feat(rust): RaidableBases — feed, raids map layer, Warlord, Spawn a raid base, profiles (PLAN_REDESIGNS §11.4)

PLAN_REDESIGNS §11.4 (D202-D208, D386-D391), protocol 14. Spec: docs
rust-link/PROTOCOL.md §20.12.

- raid.started, raid.completed, raid.purchased and raid.locked public,
  raid.ended staff's; raidableBases.js reads each row per viewer (raiders'
  and a buyer's names only for the presence audience, D376/D390; Steam ids,
  position and a run's key only for staff). Feed lines in the World filter.
- The step rust.raidbase.spawn, "Spawn a raid base" (ledgered, budget
  rust.raids): difficulty, profile and base from option sources listing each
  server's own names (D386), a spot as a world call's location with a height
  adjustment or an exact height, and PvP/NPCs/lock as on/off/blank. A base
  the raids helper made is a world resource, so eventWorld's revert and
  reconcile serve it and world.expired marks it expired; one it did not make
  records nothing and the run log says it despawns on its own timer. Refused
  at verify for a server that said it cannot; a dry run with a spot returns
  the spot check as detail.warnings (MODULE_API 1.16.0, D391). rb-not-ready
  retries in ten minutes.
- Warlord: raids_completed, title category raidscompleted, the leaderboard's
  Raid bases column (sort=raidsCompleted).
- The map's raids layer (D114), public by default with its own audience; the
  run's key is dropped before any viewer gets it.
- Server settings' line for RaidableBases; its profiles in Mod configuration
  under a virtual path (D205).
- Swagger fragment, bundle and README.

Tests: server 684/684 (raidableBases.test.js new, every name in it invented);
client 99/99, build and externals.

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

server/sidecarClient.js

@@ -452,6 +452,24 @@ const dtStart = (server, body) => request(server, '/dt/start', { method: 'POST',
  */
 const gcPlace = (server, body) => request(server, '/gc/place', { method: 'POST', body })
 
+/**
+ * Spawn one RaidableBases base for a run's step (protocol 14, §20.12): `{ key,
+ * runId }`, the plugin's own `difficulty`, `profile` and `base` names (D386), a
+ * spot (`monument` and offsets, or `x` and `z`, with `heightAdjust` or `height`)
+ * and the spawn's settings (`pvp`, `npcs`, `npcCount`, `despawnMinutes`,
+ * `lock`). `data.kind` is `raid.queued` — with `id` when the raids helper made
+ * the base the run's, so `world.revert` takes it back; `despawns` says
+ * `teardown` or `own-timer` — or `raid.error` with a reason.
+ */
+const raidSpawn = (server, body) => request(server, '/raid/spawn', { method: 'POST', body })
+
+/**
+ * A spot's checks for a raid base, spawning nothing (§20.12, D208, D388):
+ * `data.kind` is `raid.checked` with `ok`, a refusal's `reason` and `message`,
+ * and `warnings`; or `raid.error` when the spot cannot be checked (no helper).
+ */
+const raidCheck = (server, body) => request(server, '/raid/check', { method: 'POST', body })
+
 /**
  * Run console commands a step's author typed (protocol 14, §20.11): `{ key,
  * commands, teardown? }` once, or `{ key, commands, recipients }` once per
@@ -602,6 +620,8 @@ module.exports = {
   worldCall,
   dtStart,
   gcPlace,
+  raidSpawn,
+  raidCheck,
   commandsRun,
   worldRevert,
   tallyOpen,