finish-setup

Finish provisioning a freshly scaffolded SaaS project. Configure what exists, link what doesn't — never create cloud resources the user did not ask for (no new databases, no new Vercel projects). Report every change made and every step that still needs a human. If an argument names a single service, run only that section. ## Preflight 1. Read `.env.example` and the project's env loading (`lib/env.ts` or equivalent) to learn which integrations are expected. 2. Read `.env` / `.env.local` (never print secret values — report only SET or UNSET per key). 3. List which MCP servers are reachable. For each unreachable MCP that a section below needs, skip that section and add it to the final report with the missing env var. 4. Detect the stack: billing plan definitions (`lib/billing/plans.ts` or similar), migration setup (`drizzle.config.ts`, `db/migrations/`), email templates (`emails/`), analytics keys (`NEXT_PUBLIC_POSTHOG_KEY` or similar). ## Database (Neon MCP) 1. Confirm `DATABASE_URL` is set and the Neon MCP can see the project's database. If unset, stop this section and tell the user to create a database and set `DATABASE_URL` — do not create one. 2. Compare applied migrations against the local migrations directory. If migrations are pending, run the project's migrate script (`db:migrate` or equivalent) locally — not via MCP — and confirm the result. 3. Verify the auth tables exist (sessions, users, organizations if multi-tenant). ## Billing (Stripe MCP) 1. Parse the pla...