Files
orca/docs/reference
Merge Sim 24f1af645e docs(agent-status): say what 2a converged and what it left for the re-key
The key is derived from the session id; what the key is derived FROM is not. On
the replacement path the renderer's local tab id still trails the old session, so
"the tab id was the wrong input" was only half of it — the tab id is wrong because
the renderer lets it go stale, and the host does not have the problem because
`replaceConversationInSnapshot` re-keys and renames every reference.

Records what the re-key probe measured so the split PR does not re-derive it:
re-keying alone drops focus through `resolveWebSessionVisibleTabId` (which
matches by id, then by entityId, and a replacement changes both), the existing
`rekeyedTabIds` channel repairs that, `layoutByWorktree` is group-keyed so
persisted layouts are untouched, and the re-key would remove the main source of
`:history-N`.
2026-09-11 18:27:01 -07:00
..