Research: prototype read-only coding work monitoring

[srctl]

The current Jobs page nests worker output inside expandable rows, making concurrent coding work and attention states difficult to monitor. This research adds an isolated, read-only selected-job prototype and compares snapshot polling, browser streaming, and Rove reuse.

Findings, source references, limitations, and run instructions

Recommend improving the layout over existing Herdr snapshots first, then evaluating a resumable one-way stream. Rove's navigation and connection-state handling are useful references; its Pi runtime, encrypted relay and terminal control bridge need separate integration work for Codex.

All jobs/output/replay are explicitly labeled fixtures. No production routes, APIs, dependencies, terminal controls, host configuration, or live storage changed. Follow-up decisions cover mobile navigation, freshness/history retention, a passive Herdr observer, and whether Rove interoperability is wanted.

Validation

• Repository lint, app typecheck, and prototype typecheck passed.
• Coding tests: 48/48 passed with env -u ROOST_CODEX_BINARY node --import tsx --test tests/coding-*.test.ts. Initial restricted run failed under inherited worker configuration/process restrictions; clean-environment execution passed.
• App, CLI, and isolated prototype builds passed. Existing Vite config-loader warning remains.
• Playwright: replay, disconnect/reconnect, follow toggle, job-output isolation, attention/review states, mobile overflow, no browser errors or live API requests passed.
• Full unrelated tests, production auth integration, real streaming performance and Rove runtime interoperability were not exercised.

Actual rendered before / after

Same fixtures and selected running assignment, light mode, UTC, scale 1. Desktop viewport 1440×1100; mobile 390×844. Full-page capture heights vary with content.

Baseline limitation: before images render the actual existing Jobs content/StyleX from base 3f7bae2, with its job and output disclosures open. Both views use the same isolated presentation shell, stubbed router/server boundaries and fixture data. These are rendered component captures, not screenshots of an authenticated live installation. After images show the proposed monitor with identical initial output, not a connected terminal.

Before — existing Jobs content in fixture harness	After — proposed fixture monitor

Additional simulated attention and disconnected screenshots are committed alongside the reproducible capture script.

[srctl]

Please trim the one-off capture/test scaffolding from this PR at the user's request: it makes the change harder to review and does not need to be committed. Keep the implementation, useful regression tests, and the before/after screenshots embedded in the PR. Remove commands/dependencies/docs that exist solely for removed scripts; keep an honest brief record of checks already run. Do not merge or deploy.

Remove docs/prototypes/coding-view/capture.mjs and capture-only scaffolding. Keep the runnable research prototype, its necessary fixtures/configuration, findings, and screenshots: the prototype itself is the requested deliverable.