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

Merged
whitlocktech merged 1 commits from docs/runicnpc-9e-step3 into main 2026-10-09 07:43:08 +00:00
Member

What & why

The record of stage 9e step 3, the cutover, as it ran on 2026-10-09.

  • runicnpc/PLAN.md:
    • D330: v1.0.0 by a feat!: commit (runicnpc-rust#18).
    • "9e step 3, as built": the six PRs; the five releases (RunicNPC v1.0.0, Rust-Plugins v0.2.0, Rust-Link v0.2.0, installer v0.7.0, Module-Rust v0.4.0) and what was checked in each; the bundle moving from 2026.09.26.5 (protocol 12) to 2026.10.09 (protocol 13, RunicNPC 1.0.0); and the installer and the egg's script run from that real bundle.
    • It also records that Module-Rust was out 11 minutes before the bundle could install RunicNPC, and that edge was deleted by every merge and recreated.
    • The header's status line.
  • rust-link/INSTALL.md: the "until phase 19, protocol 2 vs 12" caveat was no longer true. It now names the protocol 13 releases.

Not done, and said so in the record: a panel reinstall. The panel's egg 25 dates from 2026-09-26 and lacks both RunicNPC and the banner. There is no egg-write API, so it needs Rust-Link v0.2.0's egg-rust-runicgateway.json imported by hand first.

How it was tested

Every claim in the record was read from the releases, the bundles branch (via /contents, not /raw/), and the compose runs' own logs (178 cancelled, 179 Gate 1, 182 composed). The installer and egg runs were in ghcr.io/ptero-eggs/installers:debian against scratch Oxide and Carbon roots, with nothing bypassed.

Checklist

  • I have read CONTRIBUTING.md.
  • The change builds and existing tests/checks pass locally.
  • I have added or updated tests/docs where it makes sense.
  • My commits are reasonably scoped with clear messages.

AI-assisted contributions (required)

  • No AI tools were used to produce this contribution.
  • AI tools were used. Tool(s): Claude Code (Claude Opus 5.5). I have reviewed and understand
    every change, and take responsibility for it. AI-authored commits are
    marked with a Co-Authored-By / Assisted-By trailer.

License

  • I agree that my contribution is licensed under this project's license
    (GNU GPL v3.0 or later), and I have the right to contribute it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

## What & why The record of stage 9e step 3, the cutover, as it ran on 2026-10-09. - **`runicnpc/PLAN.md`:** - **D330**: v1.0.0 by a `feat!:` commit (runicnpc-rust#18). - **"9e step 3, as built"**: the six PRs; the five releases (RunicNPC v1.0.0, Rust-Plugins v0.2.0, Rust-Link v0.2.0, installer v0.7.0, Module-Rust v0.4.0) and what was checked in each; the bundle moving from 2026.09.26.5 (protocol 12) to **2026.10.09** (protocol 13, RunicNPC 1.0.0); and the installer and the egg's script run from that real bundle. - It also records that Module-Rust was out 11 minutes before the bundle could install RunicNPC, and that `edge` was deleted by every merge and recreated. - The header's status line. - **`rust-link/INSTALL.md`:** the "until phase 19, protocol 2 vs 12" caveat was no longer true. It now names the protocol 13 releases. **Not done, and said so in the record:** a panel reinstall. The panel's egg 25 dates from 2026-09-26 and lacks both RunicNPC and the banner. There is no egg-write API, so it needs Rust-Link v0.2.0's `egg-rust-runicgateway.json` imported by hand first. ## How it was tested Every claim in the record was read from the releases, the `bundles` branch (via `/contents`, not `/raw/`), and the compose runs' own logs (178 cancelled, 179 Gate 1, 182 composed). The installer and egg runs were in `ghcr.io/ptero-eggs/installers:debian` against scratch Oxide and Carbon roots, with nothing bypassed. ## Checklist - [x] I have read [CONTRIBUTING.md](CONTRIBUTING.md). - [x] The change builds and existing tests/checks pass locally. - [x] I have added or updated tests/docs where it makes sense. - [x] My commits are reasonably scoped with clear messages. ## AI-assisted contributions (required) - [ ] No AI tools were used to produce this contribution. - [x] AI tools were used. Tool(s): `Claude Code (Claude Opus 5.5)`. I have reviewed and understand every change, and take responsibility for it. AI-authored commits are marked with a `Co-Authored-By` / `Assisted-By` trailer. ## License - [x] I agree that my contribution is licensed under this project's license (**GNU GPL v3.0 or later**), and I have the right to contribute it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 1 commit 2026-10-09 07:40:07 +00:00
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
whitlocktech merged commit 9b1062dda8 into main 2026-10-09 07:43:08 +00:00
whitlocktech deleted branch docs/runicnpc-9e-step3 2026-10-09 07:43:09 +00:00
Sign in to join this conversation.
No description provided.