Release State Dashboard

This is the first status stop before launch or live sales review. Detailed checks still live in the Launch Readiness, RC Signoff, Stripe Test, Payment Help, and Message Setup pages.

This panel turns the current member-record evidence into the next safe page and decision. It keeps live sign-in, database writes, migrations, Stripe, member messages, private records, and coordinates off until explicit approval.

This panel reads the public-safe readiness rollup. It explains whether the current hold is source-side, hosted page, or live-service related without exposing secrets.

This panel reads public-safe member-record evidence only: dry runs, synthetic bridge, service setup packets, evidence review, migration, restore, redaction, and rehearsal state. It does not activate live sign-in, create databases, read database URLs, send email, enable live Stripe, or touch offline coordinates.

This panel reads the saved service setup receipt. It shows only public-safe row IDs, status counts, and next safe action. It does not expose service secrets, database URLs, passwords, member records, live payment values, message credentials, or coordinate material.

This path keeps member records and sign-in work staged, auditable, and public-safe. It names only pages and evidence states; it does not expose service secrets, database credentials, member records, live payment values, message secrets, or coordinate material.

This queue turns service cutover holds into founder-readable next actions. It cannot approve service holds, perform restores, enable live Stripe, send member messages, or touch coordinate material.

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