Chapter onboarding

Step 1 — The chapters table exists, but there is no createChapter service, route, or admin UI. Chapters are seed-only today; a system admin cannot stand up a new organization from the app.

Step 2 — There's no discipline concept anywhere in the schema yet. Today the platform implicitly supports only one discipline (full-length competition theater) — a chapter can't yet pick theater vs. choir vs. public speaking, each with its own default rubric set.

Step 3 — There's no invitation system in this app yet (no invitations table, no email send, no accept flow). Every chapter-admin membership in the seed data is inserted directly by seed.ts, not through an invite.

Step 4 — Better Auth's plain email/password sign-in works (the login screen you've seen throughout these walkthroughs), but there is no invite-acceptance flow that binds a brand-new account to a specific chapter and role — signing in only works for accounts the seed already created and pre-assigned.

Step 6 — The settings table supports a chapter scope, and settings.setPolicy / the admin policies API exist, but they're only wired up for season-level policies (voting thresholds, nomination windows, etc.) — there's no chapter-scoped settings UI for things like auto-reminders or email notifications.

Step 7 — There's no terms/acknowledgment model in the schema at all — no field recording that a chapter admin accepted responsibility for handling sensitive student data.

Step 8 — Chapter-admin RLS gating already exists (assertChapterAdmin), but season *creation* itself is missing — see the season-setup presentation for what season management is actually built today (authoring award categories/rubrics, the calendar, and role assignment all work; creating the season/schools/performances themselves does not yet).