feat(rust): Teams from first-party clans (phase 9, protocol 6)

A first-party Rust clan is a Team (R5). This module becomes the site's
Team provider and answers core from the plugin's `clans` board. Design
of record: docs/modules/rust/PLAN.md §24, D47-D58.

- The store: rust_clans, rust_clan_members and rust_clan_boards. A clan's
  identity is <serverId>:<clanId>:<createdMs> (D52), because the game
  restarts clan ids whenever its clan database version changes.
- The provider (D53): getTeams is complete only when every server's
  board is fresh, supported and untruncated. It is partial when some
  are, and refuses when none are. Freshness is judged by the website's
  clock, from when the board's `t` last advanced.
- Only a complete board may mark a clan gone. A board at the game's
  100-clan ceiling (D55), or one with an unreadable row, proves nothing
  about what it leaves out.
- Leadership is diffed board to board and published (D54). The five clan
  events are published as team.* kinds, and written to the Team feed as
  members-only lines (D49).
- Core only writes feed items for a Team it already holds. So the last 10
  minutes of clan events are re-offered on each board refresh, deduped by
  a sha1 key: core clamps a dedupeKey to 40 characters, and a readable key
  would be truncated into collisions.
- projectRoster and the clan page share one audience rule (D48): the
  clan's linked members and staff by default, re-read from the users row.
  The setting lives on Admin > Rust visibility, which also warns about
  uMod Clans (D47) and the ceiling.
- Public: GET servers/:id/clans (the list is public, D58) and
  GET clans/:externalId. The client adds a Clans tab and
  /rust/clans/:externalId, with three module slots for core's notify,
  activity and forum contributions (D56).
- Linking and unlinking an account ask core to reconcile Teams (D57).
- The clan kinds are staff-class in the public feed allowlist.
- PROTOCOL_VERSION is now 6.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

server/index.js

@@ -51,6 +51,7 @@ module.exports = function register(ctx, api) {
   const playerRust = require('./router/player/rust.router')
   const adminRust = require('./router/admin/rust.router')
   const usersRust = require('./router/admin/usersRust.router')
+  const teamProvider = require('./model/clans/teamProvider')
   const boot = require('./boot')
   /* eslint-enable global-require */
 
@@ -93,6 +94,17 @@ module.exports = function register(ctx, api) {
   // slot and fails the load outright when named there.
   api.registerExtension('admin.users.detail', usersRust)
 
+  // Teams (R5, PLAN.md §24). A first-party Rust clan is a Team, and this module
+  // becomes the deployment's one authoritative source of them. Core asks; the
+  // provider answers from the clan boards (`model/clans`), and refuses rather
+  // than guessing whenever no board is current.
+  //
+  // **One provider per deployment**, so a site running module-uo as well cannot
+  // have both — the second registration is a collision core reports against the
+  // module that made it. That is core's rule and a real constraint on a mixed
+  // UO + Rust site; it is recorded in §24 rather than worked around here.
+  api.registerTeamProvider(teamProvider)
+
   // The lifecycle hooks (§2.5). `onBoot` runs after core's schema, after this
   // module's schema fragment, and BEFORE the HTTP listener binds — so a module
   // that must not serve traffic until it has warmed a cache gets that for free.
@@ -105,8 +117,8 @@ module.exports = function register(ctx, api) {
   api.onBoot(boot.onBoot)
   api.onShutdown(boot.onShutdown)
 
-  // Everything else this module will register — the Team provider, the event
-  // triggers and audiences, the engagement seeds, the four event catalogues, the
+  // Everything else this module will register — the event triggers and
+  // audiences, the engagement seeds, the four event catalogues, the
   // notification streams and the slash commands — is deliberately absent. Each
   // arrives with the phase that has something real to put in it. A registration
   // with nothing behind it is worse than a missing one: a declared trigger
@@ -117,5 +129,6 @@ module.exports = function register(ctx, api) {
     version: require('../module.json').version,
     routes: 'public:/rust player:/rust admin:/rust',
     extensions: 'admin.users.detail',
+    teams: 'first-party clans',
   })
 }