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

Merged
whitlocktech merged 1 commits from docs/runicnpc-9e-scope into main 2026-10-09 06:13:30 +00:00
Member

What & why

The org lead asked (2026-10-09) to "wire those 3 to the runicnpc plan as all part of stage 9e". runicnpc/PLAN.md §9e now has three ordered steps, each ending in its PRs:

  1. What the player session asked for, on edge so the cutover ships it: the default dome at 3 spheres (module-rust), and the recommended PopupNotifications banner (exact values listed) delivered by a docs block, the installer and the Pterodactyl egg — each writing only where the config is missing or at the plugin's defaults.
  2. The Carbon Kits reload, checked on a real first boot; a fix is proposed before it is built if a fresh server meets it.
  3. The cutover and release, unchanged (D311, D313), plus the installer row the walk left for it.

The session section's two pointers now name these steps.

How it was tested

Docs only.

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 org lead asked (2026-10-09) to "wire those 3 to the runicnpc plan as all part of stage 9e". `runicnpc/PLAN.md` §9e now has three ordered steps, each ending in its PRs: 1. **What the player session asked for**, on `edge` so the cutover ships it: the default dome at **3** spheres (`module-rust`), and the recommended **PopupNotifications banner** (exact values listed) delivered by a docs block, the installer and the Pterodactyl egg — each writing only where the config is missing or at the plugin's defaults. 2. **The Carbon Kits reload, checked on a real first boot**; a fix is proposed before it is built if a fresh server meets it. 3. **The cutover and release**, unchanged (D311, D313), plus the installer row the walk left for it. The session section's two pointers now name these steps. ## How it was tested Docs only. ## 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 06:13:07 +00:00
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
whitlocktech merged commit f4b7b9f3eb into main 2026-10-09 06:13:30 +00:00
whitlocktech deleted branch docs/runicnpc-9e-scope 2026-10-09 06:13:30 +00:00
Sign in to join this conversation.
No description provided.