docs(runicnpc): 9e step 3 — the cutover, RunicNPC v1.0.0 and bundle 2026.10.09 (D330)

runicnpc/PLAN.md records step 3 as built: D330 (v1.0.0 by a `feat!:`
commit), the six PRs, the five releases and what was checked in each,
the bundle moving to protocol 13 with RunicNPC 1.0.0, the order slip
(Module-Rust out eleven minutes before the bundle), edge recreated in
all five repos, and the installer and the egg's script run from the
real bundle. A panel reinstall waits for egg 25 to be re-imported.

rust-link/INSTALL.md: the "until phase 19" protocol 2/12 caveat is no
longer true; it now names the protocol 13 releases.

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

rust-link/INSTALL.md

@@ -37,9 +37,9 @@ There are three ways to set a server up. They produce the same result:
 - **The website has the Rust module**, and you are an administrator on it. Servers are added at
   **Admin → Rust → Servers** (`/admin/rust/servers`).
 
-> **Until module-rust phase 19**, the released Rust module (Module-Rust v0.3.0) speaks protocol 2
-> while the released bridge speaks 12, and a site pairing them answers `409`. This is expected and
-> closes with phase 19's release; it is not a fault in your install.
+> **The released pieces speak protocol 13 together** (2026-10-09): Module-Rust v0.4.0 on the site, and
+> the bundle 2026.10.09 on the server (Rust-Link v0.2.0, Rust-Plugins v0.2.0, RunicNPC v1.0.0). A site
+> on Module-Rust v0.3.0 or older speaks protocol 2 and answers `409`: update the module first.
 
 ---