Refused a stream publish from a query handler at the call.

[moetemp]

This PR makes StreamWriter.publish raise ReadOnlyContextError when it's called from a query handler or an update validator.

What changed?

• StreamWriter.publish checks workflow_is_read_only() before handing the record to the provider, and raises the same error other read-only violations raise.
• A workflow case shows that a query that publishes gets the error, and that the stream stays empty.

Part of AI-198 (epic AI-37).

Why?

A query task commits only its answer. A record published there could only be dropped later, without a word. It's better to fail at the call, where the mistake is. It lands in the interface, so every provider above it, Max's External Workflow Streams (Option 7) and native alike, refuses the same way.

How did you test it?

Link to a test plan if any -

• Unit Tests
• Staging
• End to End Tests

poe lint is clean. The workflow stream cases pass on the memory provider against the dev server the fixtures start, the new query case included.

[moetemp]

Replaced by #99 in the v5 series (phase 1, Signal wake only). The branch stays as a pin.