docs(runicnpc): stage 9e is three steps — the session's asks, the Carbon check, the cutover

The org lead put all three in 9e (2026-10-09): the default dome at 3 spheres and the
recommended PopupNotifications banner (docs, installer, egg) first, so the cutover
ships them; then the Carbon Kits reload checked on a real first boot; then the
coordinated v1.0.0 release.

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

runicnpc/PLAN.md

@@ -1793,21 +1793,37 @@ What the session changed or asked for:
 
 - **D323 and D324** (each example its own outfit; every item at full durability) and **D325** (`/rnpc here` stands
   the NPC a metre in front, facing you). The four kits were rewritten on both rigs by resetting `examplesWritten`.
-- **Asked for, to build next:** the default dome stacks **3** spheres, not 1 (chosen by eye at noon), and a
+- **Asked for, now 9e step 1:** the default dome stacks **3** spheres, not 1 (chosen by eye at noon), and a
   recommended PopupNotifications look: a banner across the top (left 0.15, bottom 0.87, width 0.7, height 0.07),
   no close button, Roboto Condensed Bold at 18. The docs show it, and the installer and the Pterodactyl egg write
   it where PopupNotifications' config is missing or still at the plugin's defaults.
-- **Found, not fixed:** on Carbon, the automatic Kits reload after the first load wrote the example kits did not
+- **Found, not fixed (9e step 2):** on Carbon, the automatic Kits reload after the first load wrote the example kits did not
   take: `s6bossc` stayed refused ("no kit 'rnpc_juggernaut'") until Kits was reloaded by hand. It was a hot load,
   not a boot, so a fresh server may not see it. Oxide was fine.
 - **Walk artifacts, not faults:** the harness's own players (`11400000001` and up) hold NPC kills on the rigs'
   leaderboards, which pushed the org lead out of a top-3 title rule until it was widened for the session.
   `/rnpc here` makes a placement that respawns, so a boss placed that way comes back until it is removed.
 
-**9e. The cutover and release (D311, D313).** Only after the walk passes. In order: `runicnpc-rust` `edge` → `main`
-as v1.0.0 (its Gitea release is the only download); `rust-plugins`, `rust-link` and `installer` `edge` → `main`,
-and the bundle that pins all four; `module-rust` `edge` → `main` with RunicNPC required. Each release is checked
-(checksums, the bundle composing) before the next merge.
+**9e. Before the cutover, then the cutover and release (D311, D313).** The walk passed on 2026-10-09. The org lead
+put three steps in 9e, in this order (2026-10-09), each ending in its PRs:
+
+1. **What the player session asked for.** Each lands on `edge`, so the cutover ships it without a second release:
+   - **The default dome stacks 3 spheres, not 1** (`module-rust`), chosen by eye at noon in the session; PLAN_REDESIGNS
+     §3's "until it is chosen by eye" closes.
+   - **A recommended PopupNotifications look:** a banner across the top of the screen (left 0.15, bottom 0.87,
+     width 0.7, height 0.07, spacing 0.005), no close button, Roboto Condensed Bold at 18, panel transparency 0.8.
+     It ships three ways: a block to paste in `docs/rust-link/INTEGRATION.md`; the installer writing it; and the
+     Pterodactyl egg's install writing it. Both write only where PopupNotifications' config is missing or still at
+     the plugin's own defaults, and never over one someone changed. PopupNotifications itself stays optional and is
+     installed by the operator (D141).
+2. **The Carbon Kits reload, checked on a real first boot.** In the session the automatic Kits reload after the
+   first load wrote the example kits did not take on Carbon, during a hot load. A fresh Carbon boot with
+   `examplesWritten` reset shows whether a new server meets it. If it does, the fix is proposed to the org lead
+   before it is built; if not, it is recorded as a hot-load artifact.
+3. **The cutover and release.** In order: `runicnpc-rust` `edge` → `main` as v1.0.0 (its Gitea release is the only
+   download); `rust-plugins`, `rust-link` and `installer` `edge` → `main`, and the bundle that pins all four;
+   `module-rust` `edge` → `main` with RunicNPC required. Each release is checked (checksums, the bundle composing)
+   before the next merge. The row the walk left for it: the installer's RunicNPC path from a real bundle.
 
 **Then the Rust plan resumes** at PLAN_REDESIGNS §9 item 6 (the step editor and the kit weekend) and §11.