move opencode's turn output into its own sidecar

The second copy of the same problem. The opencode sidecar reported raw
ChatEvents and officer translated them, buffered the assistant text and wrote
every durable message to chat_session_events — so an officer restart mid-turn
lost whatever the model had produced since the last write, and `connect.ts`
dropped the events that arrived while it was down without a word.

Both harnesses speak ChatEvents, so the sidecar reuses the agent's session log
verbatim: translate, commit, then deliver the finished message with its cursor
id as `opencode:message`. Officer folds it into the in-memory transcript and
relays it, exactly as it now does for claude — `createEventHandler` (166 lines,
a duplicate of turn-stream.ts) and `emitToSession` are gone, and nothing in
officer writes to chat_session_events any more.

`opencode:event` stops being a wire event; it is the runner's internal report to
the sidecar it runs in, typed as such so it cannot leak back onto the socket.

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

src/servers/sidecar/claude/turn-stream.ts

@@ -1,7 +1,8 @@
 import type { ChatEvent, TurnMessage } from '../../api/chat/types';
 
-// Translation from the parser's ChatEvent stream to the browser-facing turn messages, moved here from
-// the main server (`chat/websocket.ts:createEventHandler`). It lives with the process that produces the
+// Translation from a harness's ChatEvent stream to the browser-facing turn messages, moved here from the
+// main server (it was `createEventHandler` in `chat/websocket.ts`, once per harness). Both the agent and
+// the opencode sidecar use this one copy. It lives with the process that produces the
 // stream because it is stateful: `delta` events accumulate into a buffer that has to be flushed as one
 // `assistant:text` at the next boundary (a tool call, or the end of the turn). A consumer downstream of
 // a socket that can drop cannot hold that state correctly.