[brennanb2025]

	Files	Added	Deleted	Net
Test	5	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​444	$\color{#cf222e}{\Huge{\mathbf{−}}}$​97	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​347
Prod	8	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​389	$\color{#cf222e}{\Huge{\mathbf{−}}}$​85	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​304

Skeleton PR — plan only, no implementation yet. Stacked on #19786.

What this step does

The actual unification: main starts publishing structured rows to the renderer, and the renderer stops deriving its own.

The two filters removed

Both were added by PR 1a and are the only thing keeping main out of the renderer's lane. Each is pinned by a test, so this step starts by turning those tests red on purpose:

• main/startup/main-window-agent-status.ts — the if (structuredHost) return guard above the agentStatus:set sends. It sits above both the main window and getDashboardPopoutWindow(), so removing it is also what first gives the dashboard popout structured sessions (it has never shown them).
• main/ipc/agent-hooks.ts — the .filter((entry) => entry.structuredHost === undefined) on agentStatus:getSnapshot.

Writers retired

Per the audit table in the design doc:

Writer	Disposition
Command Code output seeds, parked-pane seeds, pty-exit removal	delete — main already emits the same facts
structured bridge status writes	delete — main now publishes the row
launch placeholder seeds	keep for now (deferral, not principle)
dismissal, acknowledgement, unmount	keep — user facts and component lifecycle
remote-runtime OSC parse	keep, fenced behind the host's published row
web-session mirror receipt clock	keep — the decay rule needs both clocks from one machine

The structured bridge's unmount cleanup becomes a tab-close signal to the host rather than a status write.

What "one writer" means after this

Not zero renderer writers. The IPC applicator becomes the single writer for observed status; four categories stay on purpose. Of those, only the launch placeholder seeds are a deferral — main holds the launch config and could seed them. That is the next thing to remove after this step, not part of it.

Open decision

The Command Code done-settle window is renderer policy with no main equivalent. This PR either moves it into main's detector or leaves it — and says which.

Dependency

Stacked on #19786 (PR 2a). Removing these filters before the two derivations converge renders one session twice and shifts the chat's elapsed clock.

[brennanb2025]

Closing as superseded — the work this PR does is now a later stage of the rebuilt lane, to be written against a contract that did not exist when this was authored.

Why it cannot simply be rebased. This was written before AgentStatusSubject (#20531) froze the identity contract, and before the canonical store (#20717) and its first producer (#20718) landed. The renderer-subscribes change now depends on host-fed selectors that are only being built in the stages ahead of it, and the branch is 339 commits behind main.

Where it lands instead. Reader cutover is its own stage: all four readers — sidebar, orca worktree ps, mobile and dashboard — move onto the same host-fed selectors, the renderer bridge writer is deleted, and today's two parallel child-freshness rules collapse into one shared decay rule. That stage is explicitly gated: it cannot start until the legacy-producer allowlist is empty on native, WSL and SSH, with no local-only waiver.

Salvage. Its missing-PTY-means-idle default is deliberately not carried forward as the remote rule — loss of contact is never evidence of process death, and the vocabulary is live / unverifiable / exited. That decision is recorded so it is not reintroduced.

Branch brennanb2025/agent-status-2b-renderer-subscribes is retained.