Release Command Center: check everything before you ship
ProductionUse one project-wide preflight to understand readiness, blockers, next build identity, and the safest next action without hunting across every release tab.
What it is
The Release Command Center sits near the top of every project and turns LaunchLayer release evidence into one plain-language status: Ready, Working, Needs you, or Blocked. It is the recommended starting point when you return to a project or are unsure what to do next.
Check everything
Check everything runs a server-side deterministic preflight across the project evidence LaunchLayer already records. Depending on platform and project path, checks include bundle or package identity, build configuration identity, exact store-app matching, store connections, deployment credentials, signing readiness, icon and screenshot evidence, store metadata, privacy confirmation, latest artifact identity, unresolved rejections, and active background jobs.
Launch readiness score
The percentage is a progress signal derived from the current preflight checks. It is not an Apple or Google approval score and does not predict App Review or Play policy decisions. Review-only recommendations are kept separate from deterministic blockers.
Next safe build number
LaunchLayer calculates a suggested next build number from the recorded project, configuration, build artifact, and deployment build numbers. This helps avoid accidentally reusing a recorded build number, but the target provider remains authoritative if it has newer build history that LaunchLayer has not yet observed.
Smart Fix Center
Unresolved checks are grouped into one expandable Smart Fix Center. Take me there opens the relevant LaunchLayer section; Ask AI opens the same project's scoped Project Agent. This routing does not grant the AI extra permissions or silently apply a change.
Reconcile status
Reconcile status is for stale or uncertain workflow state. It asks existing provider-aware screenshot, cloud-build, and deployment status workflows to refresh their recorded evidence, then reloads the project. It does not create a new paid build, change signing or credentials, submit a binary, answer legal/privacy questions, or declare provider approval.
How to use it
1) Open the project and read the Command Center status. 2) Choose Check everything after meaningful setup changes. 3) Follow the single Do this next action. 4) Use Smart Fix Center only for the remaining items. 5) Use Reconcile status when an external job finished but LaunchLayer still looks stale. 6) Re-run Check everything before a build, upload, or review submission.
Audit history
Manual preflight checks and status reconciliations create project timeline events with the readiness phase and issue counts so users can see that the project was checked without storing provider secrets in the timeline.
Safety boundary
The Command Center is orchestration and evidence, not an unrestricted automation engine. It never promises store approval. Identity mismatches fail closed, signing and credentials remain explicit, privacy/legal answers remain human-owned, and paid build starts, binary uploads, review submissions, and other high-impact provider mutations stay behind their existing guarded workflows.