docs(rust): zones and the dome as built — PROTOCOL 19.11, PLAN_REDESIGNS 3.4, D210, D211

PROTOCOL §19.11: world.zone's seven new fields, bad-option and
dome-unavailable, the bridge-said zone messages, the domes helper and
OnRgDomesReady, hello's zoneManager and integrations.zoneDomes.

PLAN_REDESIGNS: §0.6 corrected (ZoneFieldListRaw exists), §3.4 as built,
D210 (flags ticked on a presets page, the step copies a preset's line) and
D211 (the bridge reads the flag list). INSTALL names the new helper.

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

rust-link/INSTALL.md

@@ -159,7 +159,9 @@ history, and the token is unchanged.
    `oxide/plugins/` or `carbon/plugins/`, and every other `.cs` the tarball's `manifest.json` lists
    in `files` beside it — from protocol 13 that is `RunicGatewayZones.cs`, which lets ZoneManager count a
    player already standing in a zone when it opens or comes back after a restart. It is optional: leave
-   it out and events still score everybody, but ZoneManager's own flags miss that player. To name the server, create its config first —
+   it out and events still score everybody, but ZoneManager's own flags miss that player. The second is
+   `RunicGatewayDomes.cs`, which lets the bridge ask ZoneDomes for a dome over an event zone; leave it
+   out and zones open without one. To name the server, create its config first —
    `oxide/config/RunicGateway.json` or `carbon/configs/RunicGateway.json` — holding
    `{ "ServerId": "<id>", "Port": 7799 }`. Without it, the plugin calls the server `main`.
 4. **The sidecar:** put the binary somewhere stable and give it a config: