docs(rust): RaidableBases built (PROTOCOL §20.12, PLAN_REDESIGNS §11.4.6, D391, MODULE_API 1.16.0)

- rust-link/PROTOCOL.md §20.12: RaidableBases — hello's raidableBases, the
  five raid.* events, the tally's raidsCompleted, map.live's raids layer (and
  its §17.3 row), raid.spawn and raid.check with their refusals, the raids
  helper, the profiles in the configuration editor, the sidecar's two
  forwards and the website's step, feed, map layer and Warlord.
- modules/rust/PLAN_REDESIGNS.md: D391 (the editor's spot check is advice
  through core), §11.4.6 (what was built, the rig tests on both rigs, the
  Oxide rig's RaidableBases fault that a restart cleared, twelve points
  settled in code, the end walk's rows), and the order of work.
- website/MODULE_API.md, EVENTS.md: 1.16.0, a dry run's detail.warnings.
- website/STEAM_SIGNIN.md: its contract moves to 1.17.0.

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

website/STEAM_SIGNIN.md

@@ -60,7 +60,7 @@ assertion is single-use, which the existing single-use tx cookie already enforce
 - Admin → Auth shows Steam with an enable switch and, per Q3, an optional Web API key stored like a client secret.
 - The account page lists Steam identities with a *Link Steam* button, and each linked Steam account is shown with its
   id (or name, Q3) and an *Unlink* button.
-- **Module contract, MODULE_API 1.16.0 (additions only; 1.15.0 was taken by a step's `retryAfterMs`, Rust
+- **Module contract, MODULE_API 1.17.0 (additions only; 1.15.0 was taken by a step's `retryAfterMs` and 1.16.0 by a dry run's advice, Rust
   PLAN_REDESIGNS §14.3.13):** a read of a user's verified identities for one provider,
   and a hook when one is linked or unlinked. Names are settled at build. Module-uo uses neither, and runs its usual
   frozen-manifest proof against the new core.