RunicGateway/docs
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(rust): stage 6 of the last fixes — protocol 14 released, the cutover landed

Browse Source 
PLAN_LAST_FIXES gains §8.1, stage 6 as built: the merge order, the five
releases (website main 6890a74, Rust-Plugins v0.3.0, Rust-Link v0.3.0,
installer v0.8.0, Module-Rust v0.5.0) and bundle 2026.10.22, the one
harmless red release run, the installer and the egg proved over scratch
roots, the rigs on the released files, and the walk site on v0.5.0. Its
status, §7 and §8's table follow. PLAN_REDESIGNS, rust-link/INSTALL.md and
STEAM_SIGNIN.md now name protocol 14 and the cutover as shipped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
This commit is contained in:
claude
2026-10-22 06:45:44 -05:00
parent 4a6a65f45a
commit 92fd85c3e3
4 changed files with 77 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
rust-link/INSTALL.md
View File

@@ -37,9 +37,10 @@ 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`).
> **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.
> **The released pieces speak protocol 14 together** (2026-10-22): Module-Rust v0.5.0 on the site, which
> needs core MODULE_API 1.17.0, and the bundle 2026.10.22 on the server (Rust-Link v0.3.0, Rust-Plugins
> v0.3.0, RunicNPC v1.0.0). A site on Module-Rust v0.4.0 speaks protocol 13 and answers `409`: update the
> module first.
---