v0.9.4: add live room PTY dogfood

[spytensor]

Summary

Closes #306.

Adds the real v0.9.4 PTY dogfood gate for the non-default unified live room path. The existing release dogfood script now opens cr console --live-room from a freshly initialized project, types real composer input, routes bare user text to @host, routes explicit @reviewer text, exercises the unsupported runtime-only /journal path, and exits in-room without falling through to the old REPL.

Acceptance Criteria

• AC-1: Add a real PTY dogfood scenario for the non-default unified room entrypoint.
• AC-2: Scenario opens an initialized project, types a user message, dispatches it, and observes public conversation output/status without exiting to the old REPL.
• AC-3: Scenario covers explicit @role routing.
• AC-4: Permission prompt path is documented as deferred because the v0.9.4: integrate live room bridge behind non-default entrypoint #305 bridge does not yet spawn role engines or replace the mature REPL permission socket.
• AC-5: Scenario verifies dashboard panels remain structured facts and do not become the authority for completion.
• AC-6: Unified room remains non-default; this PR does not make bare cr use it.

Changed Files

• scripts/dogfood-v09-user-cases.py adds dogfood_live_room_composer_pty() and PTY scripted input helpers.
• docs/v0.9.4-live-room-dogfood.md records the v0.9.4: add real PTY dogfood for unified full-screen room #306 acceptance mapping, permission prompt gap, and rollback.
• docs/v0.9-real-user-dogfood.md extends the release dogfood matrix and recorded run with the v0.9.4 live-room scenario.
• docs/DEVELOPMENT.md updates release-gate guidance so console changes must include the live-room PTY scenario.

Validation

• python3 scripts/dogfood-v09-user-cases.py PASS. This built the local binary, initialized a temp user project, ran default/live/snapshot console PTY scenarios, exercised cr console --live-room typed input and @reviewer routing, validated Nerd Font avatar PTY output, and regenerated README images.
• cargo fmt --all -- --check PASS
• python3 -m py_compile scripts/dogfood-v09-user-cases.py PASS
• cargo test --test console_room_test --locked --quiet PASS, 5 tests
• cargo test --test console_tui_test --locked --quiet PASS, 7 tests
• cargo clippy --all-targets --all-features --locked -- -D warnings PASS
• cargo test --all-features --locked --quiet PASS
• git diff --check PASS

Evidence Packet

• WorkOrder / Issue: v0.9.4: add real PTY dogfood for unified full-screen room #306
• Tracker: v0.9.4: unify full-screen dashboard with live conversation composer #301
• Branch: codex/v0.9.4-306-live-room-pty-dogfood
• Commit: 6935a71
• Dogfood doc: docs/v0.9.4-live-room-dogfood.md
• Real user cases covered:
  • initialized project
  • cr console --live-room inside PTY
  • typed bare user text routed to @host
  • typed @reviewer routed as explicit role task
  • /journal reviewer displays clear fallback to cr start
  • /exit leaves the room without CoreRoom console closed; starting REPL
• Remaining gap: real role-engine execution and permission prompts are intentionally deferred until runtime parity is implemented.

Tracker Update

• Tracker issue: v0.9.4: unify full-screen dashboard with live conversation composer #301
• Required after merge:
  • tick v0.9.4: add real PTY dogfood for unified full-screen room #306
  • tick M-AC-6 and M-AC-7 if accepted
  • update v0.9.4: add real PTY dogfood for unified full-screen room #306 Evidence Ledger row with this PR, merged commit, and dogfood evidence

Risk / Rollback

Risk is low: this adds release-gate evidence and docs only. It does not change runtime defaults, persisted user state, package metadata, or the default cr entrypoint.

Rollback: revert this PR. The previous dogfood script and documentation will remain in place without the v0.9.4 live-room PTY scenario.