War Room: `conduit watch` as a TUI first (OpenTUI), web GUI second

[queso]

Context

prd/drafts/war-room.md specifies the War Room as a read-only view of the journal: a trace waterfall, one row per card, time on the x-axis. Four Claude Design rounds on 2026-09-28 settled the layout. The screen has a single-line header with meters for wall-clock, tokens, 5-hour plan quota, and the watchdog, plus tallies. It has a station color legend, half-height rows for done cards, a state column with one short token per row, a drawer showing the card's journal, and a strip of tool-call ticks for the current harness attempt. The TUI visual spec (frames, 160x45 golden text and ANSI frames, color tokens, and a cell-grid reference renderer) is in design/war-room/, added by #90.

Decision: TUI first

The PRD resolved "web over TUI" in June. This reverses the order but not the goal: the web GUI still follows.

• Flows run on a remote box. A TUI works over SSH or docker exec -it with no port forwarding, and it doesn't need an auth decision.
• There's no server layer: no Bun.serve endpoints, no SSE, and no reactiveSWR for the first version.
• Tests assert on rendered text and colors in bun test, with no browser.
• A vhs recording of a fixture run can serve as the launch demo.

Shared core (built once, reused by the web GUI)

• A read-only journal and state DB reader that loads the current state and follows new rows by sequence number.
• One pure projection function that folds journal events into view state. The June v0 prototype's projection sketch at design/warroom-prototype/lib/warroom-data.ts is the starting point. Reconcile its types with src/types/kernel.ts.
• Replay: events up to a chosen point, re-folded through the same function.
• "Not recorded" rendering, with each gap logged to a list of journal schema gaps (PRD FR-13).

TUI

• conduit watch renders with @opentui/react, pinned to 0.5.12 because it's pre-1.0. It's Bun-native.
• Minimum width is 160 columns. Bars use full and partial block characters. Borders use box-drawing characters.
• There's no hover. The selected row's details go in a status line. Keys: j/k to select, enter to open the drawer, t for tool ticks, r for replay, esc to close. Mouse clicks work on rows and ticks.
• The drawer is 60 columns wide and scrolls.

Testing

• Unit and component tests use testRender from @opentui/react/test-utils: captureCharFrame() for text snapshots, captureSpans() for color assertions (green only on working elements, OVERDUE the loudest color on screen), mockInput and mockMouse for interactions, ManualClock for countdowns and watchdog timing, and resize() for the minimum width.
• Core tests cover two things: replay gives the same view as live, and a burst of journal rows written in one tick folds without losing any.
• The black-box suite runs the shipped binary in a tmux pane and captures the screen with tmux capture-pane -p -e.

Out of scope

• Any write path, per PRD §7. Right-click menus are allowed but may only offer read-only actions.
• The web GUI, which gets its own issue and reuses the core.
• A multi-run view.

Open questions

• A run-level kernel heartbeat in the journal. Without one, "kernel not observed" can't tell a crashed kernel from a slow one (PRD §10).
• A run picker. Several flows will run at once, and the PRD limits v1 to a single run.

[queso]

Slice 1: shared core and a minimal conduit watch

This issue is too large for one PR, so the first PR covers the shared core plus a minimal TUI. The rest follows in later slices. Work is on branch worktree-feat-89-war-room-tui, based on main at 9b4db2d.

In slice 1

1. Read-only reader. Opens the state DB and the journal DB read-only, loads current state, and follows new rows by sequence number.
2. Pure projection function. Folds journal events into view state. It starts from design/warroom-prototype/lib/warroom-data.ts, with its types reconciled against src/types/kernel.ts. First step is checking the prototype types against the real journal schema.
3. Replay. Folds events up to a chosen point through the same function.
4. "Not recorded" rendering. Missing data renders as "not recorded", and each gap is logged to a journal schema gap list (PRD FR-13).
5. Core tests. Replay gives the same view as live. A burst of rows written in one tick folds without losing any. Missing fields do not crash a replay.
6. Minimal conduit watch using @opentui/react pinned to 0.5.12: header meters, one row per card with a state token, station colors from design/war-room/tokens.json, and j/k selection with a status line. Component tests use testRender (captureCharFrame, captureSpans, resize for the 160-column minimum).

Deferred to later slices

• The drawer, tool-call ticks, the replay key, and mouse support.
• The tmux black-box suite and the vhs demo.
• The kernel heartbeat and the run picker, which are open questions above and need a decision first.
• Exact match of the 160x45 golden frames. Slice 1 aims at the header and rows.
• The web GUI, which has its own issue.

Any write path stays out of scope, per PRD §7.