release: cut edge over to main — RunicNPC v0.1.0 (stage 0) #2

wtclaude · 2026-09-30T02:05:24Z

wtclaude commented

2026-09-30 02:05:24 +00:00

What & why

This is the edge→main cutover (D226). It carries the stage-0 scaffold merged in #1. The only commit on main is the seed (D229), so the release engine finds no tag and releases v0.1.0. That includes:

tag v0.1.0;
runicnpc-0.1.0.tar.gz, holding runicnpc/RunicNPC.cs, stamped 0.1.0, and runicnpc/manifest.json;
SHA256SUMS.

After merge

Stage 0 closes when this release is loaded on both rigs (PLAN.md §9). I will:

check the release run and the assets;
verify the tarball against SHA256SUMS;
replace the 0.0.0 working-tree copies on the Oxide and Carbon rigs with the released RunicNPC.cs;
confirm rnpc.status answers RunicNPC 0.1.0 on both rigs.

If the run stops at the credential preflight, the repository or organisation needs the REGISTRY_USER and REGISTRY_TOKEN secrets.

Checklist

PR Checks passed on #1; the cutover merge is re-checked by the release's own gate.
AI-assisted: Claude Code (Claude Opus 5.5).

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

## What & why This is the `edge`→`main` cutover (D226). It carries the stage-0 scaffold merged in #1. The only commit on `main` is the seed (D229), so the release engine finds no tag and releases **v0.1.0**. That includes: - tag `v0.1.0`; - `runicnpc-0.1.0.tar.gz`, holding `runicnpc/RunicNPC.cs`, stamped `0.1.0`, and `runicnpc/manifest.json`; - `SHA256SUMS`. ## After merge Stage 0 closes when this release is loaded on both rigs (PLAN.md §9). I will: 1. check the release run and the assets; 2. verify the tarball against `SHA256SUMS`; 3. replace the `0.0.0` working-tree copies on the Oxide and Carbon rigs with the released `RunicNPC.cs`; 4. confirm `rnpc.status` answers `RunicNPC 0.1.0` on both rigs. If the run stops at the credential preflight, the repository or organisation needs the `REGISTRY_USER` and `REGISTRY_TOKEN` secrets. ## Checklist - [x] PR Checks passed on #1; the cutover merge is re-checked by the release's own gate. - [x] AI-assisted: Claude Code (Claude Opus 5.5). 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

wtclaude added 2 commits 2026-09-30 02:05:25 +00:00

feat: stage 0, an empty RunicNPC that releases through CI

PR Checks / plugin-checks (pull_request) Successful in -1m44s

Details

249f2e513f

The repository RunicNPC is built in (docs/runicnpc/PLAN.md §9, stage 0):

- plugin/RunicNPC.cs: `// Requires: Kits` (D217), `[Info]` with the 0.0.0
  placeholder the release stamps, `RunicNpc_ApiVersion()` (API 1), and
  `rnpc.status`, which reports the version and which hooks have fired. It
  spawns nothing.
- plugin.toml: the API version, the framework floors it was loaded on
  (Oxide 2.0.7726, Carbon 2.0.259) and requires_plugins = ["Kits"].
- scripts/checkPlugin.js, adapted from Rust-Plugins': every hook listed and
  void unless written down; chat-command signatures; every RunicNpc_ call
  reachable by Call (the HumanNPC trap, PLAN.md §1.2); ApiVersion,
  `// Requires:` and [Info] agreeing with plugin.toml. 23 self-tests, including
  the real plugin and a CRLF checkout.
- PR Checks on PRs into main and edge; the release workflow on main, with
  Rust-Plugins' release engine unchanged and an adapter that ships
  runicnpc-<ver>.tar.gz (runicnpc/RunicNPC.cs + manifest.json) and SHA256SUMS.
  No bundle dispatch until stage 4.
- tools/: the rig panel scripts, with the panel and server ids moved into a
  git-ignored tools/rigs.json. `con.js` became `console.js`: CON is a reserved
  device name on Windows, and git there cannot open the file.
- README, CONTRIBUTING (edge-based flow, AI disclosure, borrow-not-copy),
  SECURITY, the code of conduct, issue and PR templates.

`feat:` so the cutover to main cuts the first release, 0.1.0.

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

Merge pull request 'feat: stage 0, an empty RunicNPC that releases through CI' (#1 ) from chore/stage-0-scaffold into edge

PR Checks / plugin-checks (pull_request) Successful in 8s

Details

bb08158c50

Reviewed-on: #1

whitlocktech merged commit da8b013a09 into main

2026-09-30 02:05:54 +00:00

whitlocktech deleted branch edge

2026-09-30 02:05:54 +00:00

whitlocktech referenced this issue from a commit

2026-09-30 02:05:54 +00:00

Merge pull request 'release: cut edge over to main — RunicNPC v0.1.0 (stage 0)' (#2) from edge into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/runicnpc-rust#2