Session Explorer

Sprint 3 treats sessions as first-class evidence objects even though they are not top-level navigation items.

How operators reach sessions:

• from the global object jump
• from the agent detail "Recent sessions" section
• from the per-agent session list

What the session view contains:

• ordered timeline rows
• selected-event inspector
• raw artifact block
• linked policy context when a timeline event references a policy
• governance-outcome rendering for Allowed, Alerted, Blocked, Throttled, Terminated, and Quarantined

Live data behavior:

• if store-svc is reachable, session summaries and timeline evidence are derived from live event envelopes served by GET /v1/store/events
• if the backend read path is unavailable, the dashboard falls back to the richer Sprint 2.6 fixture set

Current limitation:

• the backend store surface does not yet expose the full policy/governance commentary model expected by later dashboard revisions, so some session reasoning remains dashboard-derived