release-readiness-auditlisted

# Release Readiness Audit <!-- anthril-output-directive --> > **Output path directive (canonical — overrides in-body references).** > All file outputs from this skill MUST be written under `.anthril/audits/`. > Run `mkdir -p .anthril/audits` before the first `Write` call. > Primary artefact: `.anthril/audits/release-readiness-audit.md`. > Do NOT write to the project root or to bare filenames at cwd. > Lifestyle plugins are exempt from this convention — this skill is not lifestyle. ## When to use Run this skill when the user mentions: - Release readiness, pre-deploy check, go/no-go - Migration safety, destructive DDL review - Rollback plan, revert safety - Canary, blue-green, rolling deploy strategy - Feature-flag coverage for a release Integrative skill — pulls signal from CI status, Postgres schema, feature-flag config, and git history. Assesses migration safety (destructive DDL vs additive-only, backfill plan, lock duration), rollback path (forward-only changes flagged, feature-flag coverage, revert safety), config and secrets drift, runbook existence for new code paths, monitoring coverage for the new surface, and deploy strategy fit. Produces a go/no-go verdict with pre-deploy checklist, post-deploy checklist, and a rollback procedure document. ## Before You Start 1. **Determine operating mode.** `--live` requires a staging environment reachable via env (`STAGING_URL`, `PROD_URL`, `DB_STAGING_URL`). `--runtime` runs a canary smoke test against a non-prod target — re