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/core.js

@@ -149,6 +149,24 @@ module.exports = {
   // would be worse, since a module has more than one thing it could reconcile.
   reconcileEvents: () => need().events.reconcile(),
 
+  // Teams (MODULE_API.md §2.3, 1.6.0) — the push half of the provider this
+  // module registers (`model/clans/teamProvider.js`). Three calls, all
+  // fire-and-forget, and core's contract is that none of them can make this
+  // module's call site slow or turn a background failure into its error:
+  //
+  //   publish(event)       a membership or leadership change, as it happened
+  //   reconcile({reason})  "the set may have changed, come and ask" — debounced
+  //   pushActivity(items)  the per-Team feed, idempotent on each item's dedupeKey
+  //
+  // Correctness comes from reconciliation either way; `publish` only makes a
+  // change visible sooner. Wrapped as calls, like `emit`, so a file that takes
+  // `core.teams` at require time still resolves `ctx` when it is used.
+  teams: {
+    publish: (event) => need().teams.publish(event),
+    reconcile: (options) => need().teams.reconcile(options),
+    pushActivity: (items) => need().teams.activity.push(items),
+  },
+
   // Deployment facts. `moduleRoot` is the absolute path to `modules/<id>/` — the
   // only correct way to find a file you shipped, because the working directory is
   // core's and the module's location is the loader's business.