feat(teams): phase 9 — one voice channel per Team, granted by a role

TEAMS.md §7.3. Each qualifying Team gets a Discord voice channel of its own
and a role that opens it, kept in step by a reconciler that rides the Team
reconcile it already depends on.

Access is a per-Team ROLE, always. §7.3 designed per-member overwrites with
escalation to a role above ~90 members; the org lead settled on roles always
(2026-08-18), which deletes `voice_overwrite_max`, the escalation and the
`mode` column — and moves the ceiling. Overwrites are capped per channel, so
the old shape's limit was "how big can one Team be"; roles are capped per
guild at 250, so the new one is "how many Teams can have voice at all". That
is a limit an operator must be told about before they hit it, so the panel
reports it and the pass refuses the create rather than letting Discord do it.

Three things §7.3 named that this codebase does not have, all settled by
asking the operator because nothing in the data model can answer:

  - "the staff role" — there is no staff-role concept anywhere. Now a list of
    role ids the admin designates; empty is a normal answer, since guild
    administrators bypass overwrites and what is really missing is a way to
    let NON-admin staff in.
  - the parent category — §7.3 said the bot creates it and gave the id nowhere
    to live (`team_integrations.team_id` is NOT NULL). The bot creates it and
    the server stores the id in settings.
  - whether the bot can act at all — nothing has ever checked. The operator
    invites the bot by hand and no invite URL with a permission integer exists
    in the tree, so a deployment can be one unticked box from every call
    failing. A preflight is now a PRECONDITION to enabling (422), not a
    per-Team error discovered afterwards.

Two more, decided rather than asked:

  - the threshold counts every active member, not linked ones. §7.3 wrote
    `voice_min_linked_members`; the operator is judging whether a Team is real,
    and link state answers a different question.
  - hidden Teams are never provisioned. A channel name is a game-sourced string
    published outside the site, which is exactly §2.8's concern —
    reservedNames.js already names "and eventually a Discord channel name" as a
    surface it protects — so the screen that suppresses a Team's page suppresses
    its channel, and a Team that becomes hidden takes the grace window.

Turning voice OFF tears nothing down: the pass suspends in both directions and
the panel offers per-row removal. A checkbox must not delete structure in
somebody's guild.

Fixes a phase 8 defect that blocks this phase's own artifact: `npm run swagger`
has been unable to run on `edge` at all. `param('teamId').custom((v) => ... ||
/^[0-9]+$/.test(v))` makes swagger-autogen's parser run away — a regex literal
followed directly by `.test(`. Hoisted to a const, as modules.router.js
already does. Underneath it, `teams.router.js` sits exactly at that parser's
per-file limit: at twenty `teamsRouter.*` statements it dies, at nineteen it
generates, and one more statement of ANY shape tips it — an unannotated route
does, and so does a bare `use`. So the voice routes are their own router file
mounted from `admin/index.js`, and teams.router.js keeps its nineteen.

Also breaks a require cycle this phase would have introduced:
teamSync -> teamVoiceSync -> teams.model -> teamSync left `teams.model` holding
the reconciler's exports object as it stood mid-load — the empty one, since
`module.exports = {…}` replaces rather than fills. The symptom is not in the
new code: it is `teamSync.intervalSeconds is not a function` thrown out of
`syncStatus()`, the freshness banner on every public Team page.

Tests: 1160 server (+40), 53 bot (+21), 284 client (+21). Swagger, routes
manifest and guards regenerated; the guard shape of the four new routes is
byte-identical to the existing admin-only ones.

Co-Authored-By: Claude <noreply@anthropic.com>

server/swagger/swagger.js

@@ -1329,6 +1329,107 @@ const doc = {
           rows: { type: 'array', items: { $ref: '#/components/schemas/TeamIntegrationRow' } },
         },
       },
+      TeamVoiceSettings: {
+        type: 'object',
+        description:
+          'The operator\'s voice controls. Access is granted with a role per Team, so Discord\'s guild-wide cap of 250 roles — not a per-channel overwrite budget — is the ceiling on how many Teams can have voice.',
+        properties: {
+          enabled: {
+            type: 'boolean',
+            description:
+              'Switching this off suspends the reconciler in both directions and leaves existing channels standing. A checkbox does not delete structure in somebody\'s guild; remove channels individually instead.',
+          },
+          minMembers: {
+            type: 'integer',
+            example: 5,
+            description: 'Every active member counts, whatever they have linked.',
+          },
+          graceDays: {
+            type: 'integer',
+            example: 7,
+            description:
+              'How long a Team keeps its channel after it stops qualifying. A Team that recovers inside the window keeps the same channel id.',
+          },
+          categoryRef: {
+            type: 'string',
+            nullable: true,
+            description: 'The parent category, created by the bot on the first pass that needs one and stored here.',
+          },
+          staffRoles: {
+            type: 'array',
+            items: { type: 'string' },
+            description:
+              'Roles allowed into every Team channel. Guild administrators already bypass overwrites, so this is for staff who are not administrators.',
+          },
+          roleCap: { type: 'integer', example: 250 },
+        },
+      },
+      TeamVoicePreflight: {
+        type: 'object',
+        description:
+          'The bot\'s own answer about whether it can do the job. Asked before voice may be switched on and again at the top of every pass — the operator invites the bot by hand, so nothing else in the system knows what permissions it was granted.',
+        properties: {
+          ready: { type: 'boolean' },
+          connected: { type: 'boolean' },
+          missingPermissions: { type: 'array', items: { type: 'string', example: 'Manage Roles' } },
+          roleCount: {
+            type: 'integer',
+            description: 'Roles in the guild, all of them — the cap is shared with every role the operator created themselves.',
+          },
+          roleCap: { type: 'integer', example: 250 },
+          botRolePosition: {
+            type: 'integer',
+            description:
+              'The bot can only grant roles below its own. A bot at the bottom of the list creates roles it cannot hand to anybody.',
+          },
+          reason: { type: 'string', nullable: true },
+        },
+      },
+      TeamVoiceRow: {
+        type: 'object',
+        description: 'One Team\'s provisioned channel and role, as core last believed them.',
+        properties: {
+          teamId: { type: 'integer' },
+          teamName: { type: 'string' },
+          teamSlug: { type: 'string' },
+          memberCount: { type: 'integer' },
+          linkedCount: { type: 'integer' },
+          channelRef: { type: 'string', nullable: true },
+          roleRef: { type: 'string', nullable: true },
+          state: { type: 'string', enum: ['none', 'active', 'pending_removal', 'error'] },
+          removeAfter: { type: 'string', format: 'date-time', nullable: true },
+          lastError: { type: 'string', nullable: true },
+          syncedAt: { type: 'string', format: 'date-time', nullable: true },
+        },
+      },
+      TeamVoiceConfig: {
+        type: 'object',
+        properties: {
+          platform: { type: 'string', example: 'discord' },
+          settings: { $ref: '#/components/schemas/TeamVoiceSettings' },
+          preflight: { $ref: '#/components/schemas/TeamVoicePreflight' },
+          rows: { type: 'array', items: { $ref: '#/components/schemas/TeamVoiceRow' } },
+          lastPass: { $ref: '#/components/schemas/TeamVoicePassResult' },
+        },
+      },
+      TeamVoicePassResult: {
+        type: 'object',
+        description:
+          'What one reconciliation pass did, or why it did nothing. `ran: false` is the ordinary answer on a deployment with voice off, with a stale Team projection, or with a bot that cannot manage channels and roles — and the three read differently in `reason` because an operator fixes them in three different places.',
+        properties: {
+          ran: { type: 'boolean' },
+          reason: { type: 'string', nullable: true },
+          synced: { type: 'integer' },
+          created: { type: 'integer' },
+          scheduled: { type: 'integer' },
+          removed: { type: 'integer' },
+          failed: { type: 'integer' },
+          pendingMemberOps: {
+            type: 'integer',
+            description: 'Role grants a bounded pass could not fit. Non-zero asks for another pass rather than waiting out the interval.',
+          },
+        },
+      },
       TeamModerationResult: {
         type: 'object',
         description: