Tests sign up, sign in, and connectivity against your Supabase project directly — separate from the full application form, so you can isolate the login error without the rest of the six-step flow in the way.
ℹ️ You're running this from a local file. That's fine — but if requests fail with a strange error, try deploying this one file to Cloudflare Pages (or any static host) as a quick alternative.
Before you start — the two most common mistakes:
Use the Project API URL from Settings → API — it looks like https://your-ref.supabase.co. Not the dashboard link (supabase.com/dashboard/...).
No trailing slash, no extra path after .supabase.co
Use the anon / public key, not the service_role key
⚪ Not signed in (no session checked yet)
1. Project Config
Nothing entered here is saved or sent anywhere except directly to your own Supabase project.
2. Connectivity
Raw checks — these tell you if the URL itself is reachable, before any login logic runs.
Not tested
Not tested
3. Create Test Account
Not tested
Calls supabase.auth.signUp() — the same call v4 makes.
4. Sign In
Not tested
Calls supabase.auth.signInWithPassword() — use the account you just created, or an existing one.
5. Session
Checks whether Supabase currently considers you signed in.
Log
Every action and its raw response, in order.
Nothing yet — try a connectivity test first.
Next step: once every check above shows ✓, copy the exact Project URL and anon key that worked into uniapply-v4.html's SUPABASE_URL_RAW and SUPABASE_ANON_KEY constants — and let me know it's working. I'll fold the confirmed fix back into v4 to produce v4.5.