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.

README.md

@@ -17,7 +17,7 @@ Route Commerce helps produce brands run their wholesale operations:
 ## Tech Stack
 
 - **Framework:** Next.js 16 (App Router)
-- **Database:** Supabase (Postgres + Auth + RLS)
+- **Database:** Postgres (direct via `pg` + Drizzle) with Neon Auth (Better Auth)
 - **Payments:** Stripe + Square
 - **Email/SMS:** Resend
 - **Styling:** Tailwind CSS v4
@@ -37,10 +37,8 @@ npm install
 Create a `.env.local` file with:
 
 ```bash
-# Supabase
-NEXT_PUBLIC_SUPABASE_URL=https://your-project.supabase.co
-NEXT_PUBLIC_SUPABASE_ANON_KEY=your-anon-key
-SUPABASE_SERVICE_ROLE_KEY=your-service-role-key
+# Database (Postgres)
+DATABASE_URL=postgresql://user:pass@host:5432/dbname?sslmode=require
 
 # Stripe
 STRIPE_SECRET_KEY=sk_test_...
@@ -56,10 +54,9 @@ RESEND_API_KEY=re_...
 
 ### 3. Set up the database
 
-Link your Supabase project, then push migrations:
+The migrations live in `db/migrations/` and are applied via the `pg` driver (no Supabase CLI):
 
 ```bash
-supabase link --project-ref <your-project-ref>
 npm run migrate
 ```
 
@@ -111,7 +108,7 @@ src/
 │   ├── admin/       # Admin-specific components
 │   └── storefront/  # Storefront components
 └── lib/             # Utilities, auth, feature flags, formatting
-supabase/
+db/
 └── migrations/      # SQL migrations (numbered sequentially)
 ```
 
@@ -315,8 +312,8 @@ curl -X POST https://route-commerce-platform.vercel.app/api/email-automation/wel
 
 ## Notes
 
-- All database writes go through **server actions** (`src/actions/`), not the Supabase JS client directly
-- Dev mode bypasses Supabase auth via `dev_session` cookie — never use this in production
+- All database writes go through **server actions** (`src/actions/`) over a shared `pg` `Pool` from `src/lib/db.ts` — no Supabase JS client, no REST gateway
+- Dev mode bypasses Neon Auth via `dev_session` cookie — never use this in production
 - Brand-scoped data is enforced at the application layer via `p_brand_id` parameters in SECURITY DEFINER RPCs
 - Display dates use `formatDate()` (MM/DD/YYYY) — never raw `toLocaleDateString()`
 - Migration files are numbered sequentially — never reuse numbers