write: always end with an outcome; empty replies and the meterHEADmaster

From review. A write ended by anything other than its own stop (an ask,
a new conversation, another client's stop) sent only state idle, so the
canvas waited for written or an error forever; interrupt() now sends
error stopped with turn. A refused write carries turn too. An empty reply
is refused instead of saved, a document made of several code blocks is
no longer stripped as one fence, the write sizes its budget on the whole
context since no history goes with it, and its usage no longer moves the
chat's context meter. The file is written as UTF-8 whatever the locale.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

0 files changed, 0 insertions, 0 deletions