Release State Dashboard

This is the command path first stop before launch or live-rail review. Detailed gates still live in the Launch Readiness, RC Signoff, Stripe Test, Payment Recovery, and Notification workrooms.

This panel turns the current auth/database release evidence into the next safe page and decision. It keeps live auth, database writes, migrations, Stripe, notifications, customer records, and coordinates off until explicit approval.

This panel reads the public-safe staging rollup artifact. It explains whether the current hold is source-side, hosted-deploy, or live-provider related without exposing secrets.

This panel reads public-safe auth/database evidence packets only: dry runs, synthetic bridge, provider setup packets, evidence review, migration, restore, redaction, and smoke execution state. It does not activate Clerk, create a Render Postgres database, read database URLs, send notification email, enable live Stripe, or touch operator-held coordinates.

This panel reads the backend provider setup session companion receipt. It shows only public-safe row IDs, status counts, and next safe action. It does not expose provider secrets, database URLs, passwords, customer records, live payment values, notification credentials, or coordinate material.

This path keeps production auth and database work staged, auditable, and public-safe. It names only pages and evidence states; it does not expose provider secrets, database credentials, customer records, live payment values, notification secrets, or coordinate material.

This queue turns backend cutover gate IDs into operator-readable next actions. It cannot approve provider holds, perform restores, enable live Stripe, send notifications, or touch coordinate material.

Export captures the same high-level state shown here. It intentionally excludes provider secrets, Stripe keys, webhook secrets, raw coordinates, vault paths, card data, and private customer details.