Spin up Discord server + channels/roles + runbook

[quinn-dougherty]

Description

Manual one-time Discord server setup. Bot + invite automation tracked separately (new Discord bot issue). Full spec in PLAYBOOK.md §5.1.

Setup checklist

• Create server: `m∀thl∃ss.lean 2026`.
• Enable Community server (required for stage channels + announcements).
• Channels:
  • Per-track text: `#track-adversarial-robustness`, `#track-aeneas`, `#track-lean-haskell-successor`, `#track-evals-rl`, `#track-cslib`.
  • General: `#lobby`, `#hallway`, `#announcements`, `#coc-reports`, `#curators` (private).
  • Voice/stage: one per concurrent session (plan ~2 parallel at peak).
• Roles: `@attendee`, `@curator`, `@speaker`, `@organizer`, `@bot`.
• Grab IDs for env: `DISCORD_GUILD_ID`, `DISCORD_LOBBY_CHANNEL_ID`, `DISCORD_ATTENDEE_ROLE_ID`.

Event-week runbook

• Pre-event: tech test on stage channels, pin schedule, curator onboarding, T-7 reminder email.
• During: moderate `#coc-reports`, start/stop recordings, post per-session reminders.
• Post: export recordings, run Whisper for captions, send survey, publish post-mortem.

Out of scope (separate issues)

• Bot, invite reconciliation, auto-role-assign (new Discord bot issue).
• Registration-to-invite pipeline (Build /register + Stripe Checkout + webhook #4).