Infra: Cloudflare Pages deployment + Supabase env + domain

[Jose-Gael-Cruz-Lopez]

Context

Ship the site/ SPA on Cloudflare Pages. Depends on #14 building.

What to build

1. Cloudflare Pages project connected to this repo:
   • Root directory: site
   • Build command: npm run build
   • Output directory: dist
2. Env vars (Production + Preview): VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY (anon key only — never the service key).
3. Auto-deploy on push to main; preview deploys on PRs.
4. SPA routing: Vite output is a single page, so default Pages behavior is fine (add _redirects with /* /index.html 200 only if client routing is added later).
5. Custom domain matching the repo name (e.g. hackhq.\*) — can be a follow-up.

Acceptance

• Cloudflare Pages builds site/ and serves dist
• Supabase URL + anon key set as Pages env vars (no service key)
• Auto-deploys on push to main
• Live URL loads the globe with real data
• (Follow-up) custom domain
  Depends on: Frontend: Scaffold Vite + React + TS + Tailwind app (site/) #14, Backend: Supabase hackathons table + RLS read policy #11, Infra: Cloudflare Pages deployment + Supabase env + domain #20-data from Backend: Sync GitHub Action (listings.json → geocode → Supabase upsert) #13

---

Part of #10 · Design spec · Repo data lives in .github/scripts/listings.json