feat/public self-registration + sign-in/sign-up pages

[ethnjs]

Background

Previously, registration was admin-only. This pivots to public self-registration — volunteers and TDs both create their own accounts. Everyone gets role="user" on signup; admin role is assigned separately.

Changes

Backend

• POST /auth/register/ — public self-registration; validates password (8+ chars, upper/lower/number/symbol, no control chars); role hardcoded to "user"; logs the user in immediately (httpOnly JWT cookie); returns UserResponse
• POST /admin/auth/register/ — admin-only account creation; no password field; is_active=False on creation; email activation handled in a separate issue
• Shared _create_user() helper for both routes; check_if_email_exists() for duplicate email checks
• UserUpdate schema (self-service; excludes role/is_active, but does allow changing email) and AdminUserUpdate schema (admin only — role, is_active)
• PATCH /users/me/ — self-service profile update, exclude_unset=True semantics
• PATCH /admin/users/{user_id}/ — admin-only role/active-status update
• missing_profile_fields computed field on UserResponse — returns list of specific missing field names
• normalize_phone() (renamed from format_phone_us) — now returns raw digits and raises ValueError on unparseable input, instead of formatting with a graceful fallback; also updates how sync_service.py normalizes phone numbers pulled from Google Sheets
• Two new migrations: add year_level/graduation_year to users; make first_name/last_name NOT NULL
• Tests covering both register routes, self-service PATCH, admin role update, profile completeness logic

Frontend — /sign-up

• Step 1: account creation (name, email, phone, password) with inline password validation checklist
• Step 2+: progressive profile enrichment (student/employer branch, university/major/status or employer, shirt size, dietary restriction), skippable per question and all at once
• inSignUpFlow cookie preserves step 2 on navigation away mid-flow
• Redirect guard sends already-logged-in users to /dashboard
• Hits POST /auth/register/ for step 1, PATCH /users/me/ for step 2
• New supporting modules: lib/auth.ts (email/phone/password validation), Textarea component, (auth)/layout.tsx route-group layout

Frontend — /sign-in

• Email + password form, hits POST /auth/login/
• Redirect guard
• No link to /sign-up yet

Frontend — shared components

• Input, RadioOption, Select reworked: default font switched to mono, RadioOption label click now also triggers onChange (previously only the radio input itself did)
• Two new icons (IconCheckCircleSolid, IconXCircleSolid) for the password checklist

Testing

• Full backend test suite passing against a fresh Postgres volume
• Manually walked sign-up flow end to end (student + non-student branches, skip-per-question, skip-all, back-navigation mid-flow)
• Manually verified sign-in redirect guard and error states
• Confirmed branch builds/runs in isolation off main, no dependency on later commits from the source branch

Notes / follow-ups

• Backend password validator is the source of truth — frontend checklist is UX only
• proxy.ts handles auth redirects for both /sign-in and /sign-up
• After step 1, user is immediately logged in; step 2 is enrichment, not account creation
• Admin-created accounts (is_active=False, no password) rely on an email activation flow that is a separate issue (confirmed: no partial implementation exists yet)
• normalize_phone() behavior change: now raises on invalid input instead of falling back — double-check this doesn't break sheet-sync on malformed phone data
• NOT NULL migration for first_name/last_name — no visible backfill step; confirm existing rows are clean before this runs against prod data
• UserUpdate.reject_null validator rejects explicit null for name/email/phone — this seems to contradict the "explicit null clears a field" semantics described in update_user_me's docstring; worth confirming intended behavior
• Sign-in page currently has no link to sign-up — minor UX gap

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nexus	Ready	Preview, Comment	Jul 25, 2026 6:27pm

[railway-app]

🚅 Deployed to the nexus-pr-48 environment in nexus

Service	Status	Web	Updated (UTC)
nexus	✅ Success (View Logs)	Web	Jul 25, 2026 at 5:05 pm