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.

supabase/ADMIN_CREATE_STOP_FIX.sql

@@ -1,92 +0,0 @@
--- ============================================================================
--- Grok Fix Prompt: admin_create_stop (copy-paste ready for Supabase SQL Editor)
--- ============================================================================
--- This is the exact "Best Practice Version" from the fix prompt, with
--- additional comments. Run this directly in the Supabase SQL Editor
--- (https://supabase.com/dashboard/project/wnzkhezyhnfzhkhiflrp/sql) if the
--- migration push cannot be used.
---
--- After running, PostgREST may need a schema reload:
---   NOTIFY pgrst, 'reload schema';
---
--- Then test "Add New Stop" again.
---
--- The calling code (JS/TS) is in:
---   src/actions/stops/create-stop.ts  (the fetch to /rest/v1/rpc/admin_create_stop)
---   src/components/admin/AddStopModal.tsx
---   src/components/admin/NewStopForm.tsx
---   (all go through the server action createStop which builds the p_* args)
--- ============================================================================
-
-CREATE OR REPLACE FUNCTION public.admin_create_stop(
-  p_active boolean,
-  p_address text,
-  p_brand_id uuid,
-  p_city text,
-  p_cutoff_time time,
-  p_date date,
-  p_location text,
-  p_state text,
-  p_time time,
-  p_zip text
-)
-RETURNS jsonb
-LANGUAGE plpgsql
-SECURITY DEFINER
-SET search_path = public
-AS $$
-DECLARE
-  new_stop_id uuid;
-BEGIN
-  INSERT INTO stops (
-    active,
-    address,
-    brand_id,
-    city,
-    cutoff_time,
-    date,
-    location,
-    state,
-    time,
-    zip
-  )
-  VALUES (
-    p_active,
-    p_address,
-    p_brand_id,
-    p_city,
-    p_cutoff_time,
-    p_date,
-    p_location,
-    p_state,
-    p_time,
-    p_zip
-  )
-  RETURNING id INTO new_stop_id;
-
-  RETURN jsonb_build_object(
-    'success', true,
-    'stop_id', new_stop_id,
-    'message', 'Stop created successfully'
-  );
-EXCEPTION WHEN OTHERS THEN
-  RETURN jsonb_build_object(
-    'success', false,
-    'error', SQLERRM
-  );
-END;
-$$;
-
--- Important: grant so PostgREST (anon key from server action) can invoke it.
-GRANT EXECUTE ON FUNCTION public.admin_create_stop(
-  boolean, text, uuid, text, time, date, text, text, time, text
-) TO anon, authenticated, service_role;
-
--- Reload cache so the function is immediately visible (avoids PGRST202).
-NOTIFY pgrst, 'reload schema';
-
--- NOTE: The above simple version may fail on INSERT because the stops table
--- requires "slug" and "status" (NOT NULL, no defaults in all cases).
--- Prefer the enhanced version in migrations/202_fix_admin_create_stop.sql
--- which includes slug generation and status='draft' while using a compatible
--- signature and the success/stop_id return shape.