preflightlisted

# Preflight — the last pass before a repo goes public One run per repo. The pass is **read-only on infra**: it reports platform problems; fixing them (set env var, Stripe config, DNS, deploy) is a CLAUDE.md Hard Stop. Collect every needed infra fix into ONE batched go-ahead list at the end — never apply them mid-pass, never ask one at a time. Two rules that override everything below: - **Env vars are checked by NAME only.** Never pull, print, or diff env VALUES — not in chat, not in a file. Never run `vercel env pull` (it has blanked `.env.local` on this machine twice). - **Invoke the skills; don't reimplement them.** impeccable, polish, and frontend-verify each carry their own protocol. ## 0. Aim at the right project - `git status` first. Note uncommitted work. - offlocal is project-scoped and keeps a "selected" project between sessions. Always: `list_projects` → `select_project` for THIS repo → `get_project_context`. Skipping this audits whatever repo was selected last. - No matching offlocal project? Say so in the report and run local-only checks. - If a launch plan (`launch_*`) exists for this project, also run `preflight_launch` and `verify_launch` and fold their results into the report. ## 1. Wiring audit (read-only) - Required var names come from `.env.example`. If it is missing or stale, grep `process.env.` / `import.meta.env.` and report the drift — that is itself a finding. - Check presence of each name on the deploy platform via offlocal (`get_project_contex