0 stale/missing signals
Public dashboard
Dispatch
Refine docs-view compactness and readiness-card evidence behavior, especially Deck's Docs / freshness hover/focus behavior, before tuning readiness heuristics. Keep an eye on the weekday refresh/deploy automation after the new central overview deploy step.
Readiness: Architecture: strong, Docs / freshness: strong; 5 decision signals.
Open dashboard
2 stale/missing signals
Local/private dashboard
Deck
Keep Controlled Runner v1 terminal-only and fixed-command-id only while keeping refusal regression coverage current.
Readiness: Automation: strong, Frontend: solid; 1 decision signals.
Local/private only
3 stale/missing signals
Public dashboard
Sleeping Bunnies
Start the next substantive work on a feature branch from updated main.
Readiness: Frontend: solid, Architecture: solid; 3 decision signals.
Open dashboard
0 stale/missing signals
Public dashboard
S2S CRM
Run the launch-host readiness pass: verify the deploy target and secrets, prove backup/restore, run read-only readiness checks, confirm session behavior, create approved staff access only after those gates, then complete the final real-browser smoke with representative Whistler data.
Readiness: Validation: strong, Docs / freshness: strong; 2 decision signals.
Open dashboard