Add mission control to the web client

[Haz3-jolt]

Outcome

Render mission control in planned packages/web/ from the public SDK, with the authenticated gateway or control plane retaining session and placement authority.

Current repository evidence

• Planned packages/web/ is absent from the current repository.
• Local session listing exists only as a process-host helper and is not a browser mission-control contract.

Acceptance criteria

• Render repository, placement, runtime state, current operation, cost, blocker, security mode, and freshness from the shared SDK projection.
• Offer only capability-granted open, attach, interrupt, and filter intents and distinguish observer-only connections.
• Recover from disconnect, stale cursors, and unreachable placements through authoritative snapshots.
• Keep daemon launch, worker allocation, policy, and session aggregation outside browser code.
• Pass shared mission-control conformance plus browser security, accessibility, authorization, and reconnect tests.

Verification

Run planned web tests against local fake daemons and the shared SDK conformance suite. No tests were run during this source audit.

Coordination

#234 owns aggregation and actions. The web gateway and remote control plane remain separate client prerequisites.

Source

ROADMAP.md, Product vision §18.3; Technical implementation roadmap, Phase 14 Daemon and placement features.

Repository audit

Audited against Axl 88944a2. Phase 14. Source inspection, not an executed behavior test. Roadmap references: L1438, L2355.

Tracking key: axl-backlog:learning.mission-control-web.

Issue tracking

Axl issue mirror: #368 | GitHub #368

Related issues:

• #234 (Expose cross-repository mission-control state #234)