RunicNPC is the Rust bundle's third artefact from stage 4, so its release
ends as Rust-Plugins' does: a dispatch of the installer's bundle workflow,
warned rather than failed when the token cannot reach it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
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
