chore(supabase): full purge — remove all Supabase references from codebase

- Delete supabase/ directory (config.toml, push-migrations.js,
  ADMIN_CREATE_STOP_FIX.sql, 137 archived migration files)
- Remove @supabase/ssr and @supabase/supabase-js from package.json
- Strip *.supabase.co from next.config.ts image hostnames
- Strip https://*.supabase.co from vercel.json CSP connect-src
- Remove 'supabase/**' ignore from eslint.config.mjs
- Clean supabase references from src/lib/db.ts, vitest.config.ts,
  db/seeds/2026-tuxedo-tour-stops.sql, src/actions/storefront.ts,
  scripts/import-tuxedo-stops.ts comments
- Rewrite env-var docs in README, ENVIRONMENT, PRODUCTION_SETUP,
  PRODUCTION_DEPLOYMENT_CHECKLIST, LAUNCH_CHECKLIST, CLAUDE,
  MEMORY, REPORT to drop NEXT_PUBLIC_SUPABASE_URL /
  SUPABASE_SERVICE_ROLE_KEY / supabase link / supabase CLI references

The canonical migration runner is now scripts/migrate.js (uses pg
directly via DATABASE_URL). Migrations live in db/migrations/. The
Supabase CLI is no longer in the codebase. The only remaining
'@supabase/*' in the dep tree is @supabase/auth-js as a transitive
of @neondatabase/auth (Neon Auth / Better Auth).

Final source scan: grep -rln '@supabase\|rest/v1\|supabase\.co'
src/ tests/ db/ scripts/ next.config.ts vercel.json eslint.config.mjs
package.json returns zero. Verification: npm install clean
(11 added, 21 removed, 12 changed), tsc shows same 17 pre-existing
errors (Stripe dahlia API version + fetch preconnect mocks),
vitest 172/175 (3 pre-existing failures in getAdminUser.test.ts),
lint shows same 14 pre-existing errors. Live-tested: dev server
boots in 248ms, public storefronts (/) (/login) (/pricing) (/tuxedo)
(/indian-river-direct) all return 200; /admin/v2?demo=1 reaches 200
after dev_session redirect; storefront renders real brand content.

REPORT.md

@@ -4,6 +4,8 @@
 **Mission:** Stand up a working Auth.js v5 + Google sign-in flow, then rip out
 all Supabase references from the auth/admin path.
 
+> **Note (2026-06-25):** Auth has since moved from Auth.js (NextAuth v5) to **Neon Auth (Better Auth)** — see `CLAUDE.md` for the current architecture. The Supabase purge described below is complete: `supabase/` directory deleted, `@supabase/*` deps removed from `package.json`, `next.config.ts` / `vercel.json` / `eslint.config.mjs` cleaned of Supabase hostnames and ignore patterns, and the remaining `*.supabase.co` references are limited to historical/educational comments in `MEMORY.md` and `docs/`.
+
 ---
 
 ## What was built
@@ -171,7 +173,7 @@ src/actions/ai/preferences.ts
 
 1. **Provision a `pg` pool in production.** `DATABASE_URL` must be
    set in the hosting dashboard (same env var as
-   `supabase/push-migrations.js` uses).
+   `scripts/migrate.js` uses).
 2. **Apply migration 204** if not already applied — adds
    `email`, `auth_provider`, `auth_subject` columns to `admin_users`
    and the `get_admin_user_for_session` RPC.
@@ -192,6 +194,15 @@ src/actions/ai/preferences.ts
 7. **Delete `@supabase/ssr` and `@supabase/supabase-js` from
    `package.json`** (last step once no file imports them).
 
+### Resolution (2026-06-25)
+
+Follow-ups 6 and 7 (and the data-fetching migration of all 33 files) are
+complete. The codebase is now Supabase-free at the source-code level —
+`grep -rln '@supabase\|rest/v1' src/` returns zero matches. The only
+remaining mentions of "Supabase" are in this report, `MEMORY.md`, and a
+handful of historical `docs/superpowers/{plans,specs}/` files, all kept
+as historical record of the migration.
+
 ---
 
 ## Commands