v0.9.x: implement true full-screen runtime parity before making live room default

[spytensor]

Context

The intended product shape is one full-screen CoreRoom room that owns the same execution guarantees as cr start: configured role runtime, real dispatch, streaming output, permission prompts, durable turn state, and dogfood evidence.

This tracker captured the parity work required after the staged live-room bridge proved misleading in v0.9.5/v0.9.6. The parity line is complete as of #338.

Acceptance Criteria

• AC-1: Full-screen live room spawns configured role engines or reuses the same runtime session manager as cr start. Implemented by [codex] implement live room TUI runtime #337 via run_with_options_and_sink_input hosted in console_room_runtime.
• AC-2: Bare text and explicit @role dispatch produce real role turns and durable CREP/message events. Implemented by [codex] implement live room TUI runtime #337 by feeding composer lines into the existing parse_line path.
• AC-3: Streaming role output, thinking/working status, tool counts, and work cards render in-room while turns are active. Implemented by v0.9.x: port REPL output::*/splash::* through RoomSink #327, v0.9.x: port REPL work::render_card and StatusRegion through RoomSink #328, and [codex] implement live room TUI runtime #337 through RoomEvent + TuiSink.
• AC-4: Permission prompts use the mature permission IPC/socket path inside the full-screen surface. Implemented by v0.9.x: port permission prompt rendering through RoomSink #329 and [codex] implement live room TUI runtime #337 through event-driven permission responses returned to the bridge responder.
• AC-5: /halt, Ctrl-C handling, /fresh, /refresh, /resume, /transcript, /journal, and /patch are either implemented in-room or explicitly blocked with parity tracking. Implemented by [codex] implement live room TUI runtime #337 through the existing slash-command parser; active TUI interruption maps to the legacy interrupt signal path.
• AC-6: PTY dogfood covers a deterministic local fake engine that proves the same runtime contract. Implemented by Ship fake-engine dogfood and TUI default #338 through Engine::Fake and scripts/dogfood-v09-user-cases.py.
• AC-7: Plain cr defaults to the full-screen live room after AC-1 through AC-6 passed. Implemented by Ship fake-engine dogfood and TUI default #338 in run_console_first_default.

Required Evidence

• Runtime integration and unit tests: [codex] implement live room TUI runtime #337 and Ship fake-engine dogfood and TUI default #338 local/CI validation.
• Deterministic fake-engine dogfood harness: Ship fake-engine dogfood and TUI default #338 adds gated engine = "fake" and drives the TUI over a real PTY.
• Real PTY evidence for active turn status, permission prompt, completion, and durable transcript state: Ship fake-engine dogfood and TUI default #338 dogfood observed idle/working/idle status, streamed fake-stream-* chunks, FakeTool permission overlay denial, and durable turn_dispatched, role_spoke, and permission_denied events in .coreroom/messages.jsonl.
• Updated release/docs/assets: Ship fake-engine dogfood and TUI default #338 updates README, CHANGELOG, splash content, v0.9 dogfood docs, generated README image, and version metadata to v0.9.8.

Progress Ledger

• [codex] implement live room TUI runtime #337 merged: implements TuiSink, console_room_runtime, external REPL input channel, TUI permission response path, and cr console --live-room wiring.
• [codex] implement live room TUI runtime #337 CI: rustfmt, shellcheck, clippy, test (ubuntu-latest), test (macos-latest) all passed.
• Ship fake-engine dogfood and TUI default #338 merged: adds gated fake engine dogfood, flips interactive plain cr to the executable TUI room, keeps cr start as stdout runtime, and keeps cr console as read-only dashboard.
• Ship fake-engine dogfood and TUI default #338 local validation: cargo fmt --all -- --check, git diff --check, cargo clippy --all-targets --all-features --locked -- -D warnings, cargo test --all-features --locked, and python3 scripts/dogfood-v09-user-cases.py all passed.
• Ship fake-engine dogfood and TUI default #338 CI: rustfmt, shellcheck, clippy, test (ubuntu-latest), test (macos-latest) all passed.
• Remaining risk: dogfood proves CoreRoom runtime/TUI/permission/durable-event plumbing via fake engine; authenticated Claude Code, Codex, and Gemini turns remain manual because they require logged-in CLIs and can burn quota.

Non-goals

• Treating dashboard/rendered prose as completion evidence.
• Burning authenticated vendor-engine quota in release dogfood.

Tracker Update Required

Tracker complete. #338 supplies deterministic dogfood evidence and flips the plain cr default to the executable full-screen TUI room.

[spytensor]

User report after v0.9.7: plain cr is truthfully executable but visually/product-wise still feels like the old pre-full-screen runtime. Treat this as active blocking work: the next fix must make the default path a real full-screen Control Room runtime, not a staged preview and not the classic REPL splash. v0.9.7 is an emergency truthfulness rollback, not the desired endpoint.