release-readiness-check

Run a release readiness check that verifies reproducible install, typecheck, lint, build, tests, health endpoint, secrets, and migrations from a clean checkout. Each gate produces pass/fail evidence, and the result is a Go/No-Go verdict with blockers listed separately.

A deployment preflight should verify the build artifact matches CI, required environment variables exist in the target, pending migrations are non-destructive and backward compatible, the health endpoint checks real dependencies, and a tested rollback plan exists for code, database, and config changes.

No, the check is strictly read-only verification. It runs status and info commands like migrate status and curl health checks, never applies migrations, pushes artifacts, or modifies environment variables, and redacts secrets in all evidence.

npm ci fails when package.json and the lockfile are out of sync, while npm install silently resolves drift. This means the release machine gets different dependency versions than local development, so the lockfile must be regenerated and committed.

Skip readiness gating for private experiments with no audience, tasks unrelated to release or operability work, or when a narrower review such as a CI/CD pipeline audit already covers the specific concern.

Run the README from an empty directory as a new teammate would, checking install, start, and test commands work without implicit knowledge. Also audit runbooks, bus factor via commit distribution, credential ownership, and estimate time-to-productivity for an incoming engineer.