Remote Control: SessionStart hook sessionTitle output is delivered to the bridge but never applied to the session's display title

Environment

Claude Code 2.1.207, Windows 11, claude remote-control server mode; SessionStart hook emitting the documented sessionTitle output field.

Problem

For Remote-Control-spawned sessions (including the server's pre-created session), the SessionStart hook runs normally (source: "startup") and its sessionTitle JSON output is visibly relayed to the bridge — the debug stream shows the hook_response event containing {"sessionTitle":"…"} with "outcome":"success" — but the bridge assigns the session's display title BEFORE hooks complete ([bridge:title] precedes the hook response by ~1s in three independent instrumented runs) and never updates it afterward. The hook title is therefore applied to the local session while the claude.ai / mobile display title follows only the rc chain (explicit --name → /rename/prompt-derived → auto prefix-random-word).

Users who standardize session naming via the documented sessionTitle hook field (hooks.md) get conforming titles everywhere EXCEPT the Remote Control UI, where the title is the most user-visible.

Request

Have the bridge apply (or re-apply) the SessionStart hook's sessionTitle to the Remote Control display title — hooks.md documents the field as acting like /rename, and /rename DOES propagate to the Remote Control UI, so the current behavior is an inconsistency between the two documented equivalents. Alternatively, document the precedence explicitly in remote-control.md.

🤖 Filed with Claude Code on the user's behalf