v0.8: End-to-end console data plane dogfood validation

[spytensor]

Context

v0.8 must dogfood the full console data plane on CoreRoom itself before v0.9 starts building the full-screen UI.

Acceptance Criteria

• AC-1: Start from a user request to @host for the v0.8 project console.
• AC-2: Host classifies the request and binds it to a WorkOrder/tracker row.
• AC-3: Build a CoreRoomSnapshot from project identity, roles/runtime, WorkOrders, GitHub lifecycle, gates, evidence, sources, and alerts.
• AC-4: Include a public transcript fixture proving User ↔ @host remains clear while role delegation is side-rail/internal.
• AC-5: Include a negative stale-tracker or missing-evidence fixture.
• AC-6: Generate or reference the console mock image from the snapshot fixture.
• AC-7: Evidence Packet and tracker v0.8.0 - CoreRoom Console Data Plane Tracker #238 are complete before the issue claims done.
• AC-8: Document remaining v0.9 risks and readiness criteria.

Evidence Required

• Host transcript fixture.
• WorkOrder or fixture binding.
• CoreRoomSnapshot fixture.
• Rendered console image or snapshot output.
• Evidence Packet or inline evidence summary.
• PR/CI result.
• Tracker update.
• Remaining risks and rollback.

Tracker Update Required

This issue is incomplete until tracker #238 is updated.

• Tick this issue checkbox in v0.8.0 - CoreRoom Console Data Plane Tracker #238.
• Update any satisfied milestone AC in v0.8.0 - CoreRoom Console Data Plane Tracker #238.
• Update the Evidence Ledger row in v0.8.0 - CoreRoom Console Data Plane Tracker #238.
• Mention the tracker update in PR body.

If implementation is complete but tracker is stale, report implementation complete, tracker incomplete.

Out Of Scope

• No v0.9 full-screen terminal UI.
• No release unless separately requested.
• No mutating console actions.