v0.8: Role lane runtime snapshot model

[spytensor]

Context

The console should show roles as active work lanes, not as chat participants. Users need to know which roles are enabled, working, waiting for approval, blocked, stale, or idle without seeing every internal role message.

Acceptance Criteria

• AC-1: Define a role lane/runtime snapshot model for enabled roles.
• AC-2: Include role, engine, model, permission mode, session fresh/resumed state, priors/knowledge freshness where available, current WorkOrder/gate, last activity, and waiting-approval state.
• AC-3: Do not expose subprocess handles or secrets.
• AC-4: Distinguish enabled, idle, working, reviewing, blocked, waiting-user, waiting-approval, and stale-session states.
• AC-5: Tests or fixtures cover at least five role states.
• AC-6: Role lanes feed side-rail summary without polluting the public transcript.

Evidence Required

• Model/fixture changes.
• Tests for role lane states.
• Validation commands.
• Risk 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 multi-agent scheduling changes.
• No role auto-execution.
• No full-screen role view.