launch-checklistlisted

Execute a comprehensive pre-launch gate check against the canonical checklist, surfacing every blocking issue that must be resolved before the product goes live. Non-autonomous: presents a full findings report; nothing is auto-fixed — the user decides how to address each item. ## Phases 1. **Load checklist template** — read `.claude/templates/launch-checklist.md` to get the canonical item list. If the template is missing, fall back to the built-in checklist defined in this skill. Check whether a previous run exists at `docs/specs/launch-checklist.md` and note any items already marked PASS. 2. **Security: secrets check** — run `git log --all --full-history -- '.env' '.env.*'` and grep the working tree for patterns matching real API keys (`sk_live_`, `sk_test_`, `eyJ`, `-----BEGIN`). Verify `.gitignore` covers `.env`, `.env.local`, and `.env.*.local`. Any real secret found in version control is an immediate BLOCK. 3. **Security: RLS verification** — read all migration files under `supabase/migrations/` and all Supabase query code under `lib/` and `app/`. Confirm that every tenant-scoped table has `ENABLE ROW LEVEL SECURITY` and at least one policy. Flag any table that is missing RLS as a BLOCK unless it is explicitly documented as public or service-role-only. 4. **Billing: Stripe live-mode check** — verify that the production environment's `STRIPE_SECRET_KEY` starts with `sk_live_` (check `.env.example` notes or ask the user to confirm). Verify that the Stripe webhook endpoint