The current route is loading its editorial surface, data, and workspace context.
Scan current workspace health, act on alerts and reconciliation, verify queue and automation state, and review operational evidence without leaving the selected ops scope.
Public runtime health remains visible here, but queue depth, alert controls, reconciliation, and retry actions only load after an authenticated studio session selects an accessible workspace.
Web control plane · Reported Apr 27, 2026, 1:57 PM
fetch failed · Checked Apr 27, 2026, 1:57 PM
No checkpoint reported · No workflow source reported
Operator scope not loaded · 0 accessible workspaces
Public runtime health is still visible above, but live queue state, alert controls, reconciliation, and generation recovery stay behind the authenticated operator boundary.
Use a studio session to move from passive runtime checks into queue triage, alert handling, reconciliation repair, and retry control.
Workspace-aware commands stay protected so alert policy and remediation actions remain scoped to a real owner or operator session.
Accessible workspace summaries remain available as supporting context below the live command surface so operators can confirm where they can move next without crowding the active attention zones.
Workspace summaries will appear here after ownership or operator access is provisioned.