v0.36.1

A steer used to become durable and stay invisible for the length of a
provider's time-to-first-token: the queue row cleared the instant the drain
loop lifted the message, and the text appeared only when the next round's
first chunk triggered a recompose. A reader watched their message leave the
queue and land seconds later.

Appending is now announcing. Every durable write of a conversation message
routes through one journal, and the journal publishes what it writes, so
there is no path that makes a record durable without telling anyone. The two
kinds of visibility stay apart: a durable record appears immediately, an
in-flight unit grows on the throttled streaming clock.

With the number to go with it. TestSteerVisibilityGap runs the real agent
against a provider that stalls its second round by a settable amount and
times the queue row's exit against the steer reaching the wire. The gap
tracks the stall (3.001s at v0.36.0 with a 3s stall, 1.000s with a 1s stall)
and is 0ms here. The test asserts as well as measures, and fails on the old
code quoting that 3.001s.

plans/journal-emit-audit.md walks every emit site. Its finding is that
aria.Server.Update returns early when no live unit is open, so the journal's
publish is dropped in exactly the path that motivated it, and the emits after
startAssistantUnit are the fix rather than belt and braces.