reattach a refreshed browser to a running turn

Refreshing mid-turn appeared to kill the agent's output. It never did: the
session survives a dropped socket, the agent keeps generating into it and keeps
committing durable events, and `close` only detaches the socket and arms an
hour-long idle timer. What broke was purely delivery — and the reconnect path
that would have fixed it could not fire, because the browser came back having
forgotten officer's session key. It lived in page state. The only id left was
Claude's transcript uuid in the URL, and nothing accepted that.

So accept it. `attach` carries the uuid, and the agent's on-disk session map —
the single record relating the two — turns it back into the key everything else
is written in terms of. The uuid now also goes out at `system.init` rather than
only at `result`, which is what makes the first turn recoverable at all: until
now a chat had no address until it had finished, and a long first turn is
exactly the one worth reconnecting to.

`sync:live` deliberately carries no messages. The harness writes its transcript
as it goes, so the HTTP load on landing already supplies the past; sending the
server's record of the same messages on top of it would duplicate them, and
there is no shared id to reconcile the two by. Attach hands over the rest of the
turn, the half-written paragraph the transcript cannot hold, and the session's
cursor head — that last one so a *later* drop replays from the head instead of
re-delivering the whole conversation from zero.

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

src/servers/sidecar/claude/state.ts

@@ -105,6 +105,28 @@ export function getClaudeSession(sessionKey: string): string | undefined {
   return currentState.claudeSessions[sessionKey];
 }
 
+/**
+ * The same map read backwards: Claude's transcript uuid → the key officer made up for the session.
+ *
+ * A browser that has refreshed holds only the uuid, because that is what is in the URL; officer's own
+ * key lived in page state and is gone. This is the only record anywhere that relates the two, which is
+ * why re-binding a socket to a running turn has to come through the sidecar rather than being answerable
+ * on the platform side.
+ *
+ * A linear scan over a handful of live sessions. If that ever stops being true, add the inverse map —
+ * but a second copy of a mapping is a second thing to keep honest, and this one is written on every turn.
+ * Newest wins: a transcript resumed under a fresh key leaves the old entry in place, and the caller wants
+ * the session generating now, not the one that produced the same file yesterday.
+ */
+export function findSessionKeyByClaudeSession(claudeSessionId: string): string | undefined {
+  const keys = Object.keys(currentState.claudeSessions);
+  for (let i = keys.length - 1; i >= 0; i--) {
+    const key = keys[i]!;
+    if (currentState.claudeSessions[key] === claudeSessionId) return key;
+  }
+  return undefined;
+}
+
 function scheduleSave() {
   if (saveTimer) return;
   saveTimer = setTimeout(async () => {