sdlc-release-checklisted

# sdlc-release-check > The pre-flight checklist. Run before anything goes to prod. Run this **after** `sdlc-review` and any risk reviews the change tripped (`sdlc-migration-check`, `sdlc-contract-check`, `sdlc-security-review`). Ground yourself in the plan and the review artifacts in `.sdlc/reviews/` before judging readiness. > **Note for the autonomous loop:** LoopSmith never deploys or releases on its own — the loop parks an > irreversible action (deploy/release) for a human rather than running it (enforced by `/sdlc-loop`). This > skill produces the go/no-go artifact a human release captain reads; it does not perform the release. ## Goal Confirm a change is genuinely ready to ship, and produce the artifact a release captain reads. ## Steps 1. Run the eleven-point checklist. Each item: `pass` / `fail` / `n/a` + one line. 2. Identify the canary path: who / what / where gets it first, and the verification metric. 3. Identify the rollback path: exact steps, timing (target ≤ 5 min). 4. Confirm the right people are notified (on-call, dependent teams). 5. State the release window (now / scheduled / off-peak). ## Eleven-point checklist 1. Tests green — full suite, not just affected files. 2. Type / lint clean. 3. Plan trace clean (no orphan diff lines). 4. Review says ready (`.sdlc/reviews/` + the loop's own review verdict). 5. Feature flag set correctly (default-off for risky changes). 6. Migrations sequenced; backfills started. 7. Dashboards / alerts present for new surfac