Session rename — the title race, fixed four ways

Three writers fight over the CC session title: the version-banner hook (every prompt), cmux (stamps the git branch on focus), and your /rename (once). This session's real tally: hook 150 · cmux 19 · rename 10 — the hook buries your rename every prompt. Pick a fix, watch the same event timeline resolve.

Resolved — and there was a FOURTH writer this doc missed. Measured across 1000 sessions (7 days), a manual rename was clobbered in 7 of 25 sessions. The dominant clobber source was not the hook (3 events) or cmux (1) but Claude Code's native AI auto-titler (ai-title, 502 events) — which the design above never modeled. Key fact: CC's ai-title only generates for unnamed sessions. ork's banner hook kept un-naming the session by overwriting /rename (option B re-checked the transcript tail every turn and could miss the rename), which re-woke CC's auto-titler. Fix shipped: option B is now a sticky per-session latch — once a rename is detected, ork writes user-renamed.flag and never emits again. The name persists, so CC keeps the session named and its auto-titler stays off. One flag closes all four sources. See docs/fix--session-rename-sticky-guard/rename-latch.html.