feat!: RunicNPC 1.0.0, the release module-rust requires (runicnpc 9e) #18

wtclaude · 2026-10-09T07:14:33Z

wtclaude commented

2026-10-09 07:14:33 +00:00

What & why

Stage 9e step 3 opens here. The release engine reads non-merge commit subjects since v0.1.0, and every stage landed as feat:, so the cutover would have cut v0.2.0. This commit's ! (and its BREAKING CHANGE: footer) makes it v1.0.0, as docs/runicnpc/PLAN.md and the README say — your choice of 2026-10-09.

README: the status line says v1.0.0; the Releases section says how the number was reached.
No code change. The API stays 6; plugin.toml is untouched.

Merge this before the cutover PR (edge → main), which is open beside it and picks this commit up when it lands.

How it was tested

node scripts/checkPlugin.js → plugin ok — API 6, 24 API call(s), 12 hook(s) declared, requires Kits.
The commit subject matches the engine's major rule, ^[a-z]+(\([^)]+\))?!: (checked with that grep).

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 Stage 9e step 3 opens here. The release engine reads **non-merge** commit subjects since `v0.1.0`, and every stage landed as `feat:`, so the cutover would have cut **v0.2.0**. This commit's `!` (and its `BREAKING CHANGE:` footer) makes it **v1.0.0**, as `docs/runicnpc/PLAN.md` and the README say — your choice of 2026-10-09. - README: the status line says v1.0.0; the Releases section says how the number was reached. - No code change. The API stays **6**; `plugin.toml` is untouched. **Merge this before the cutover PR (`edge` → `main`)**, which is open beside it and picks this commit up when it lands. ## How it was tested - `node scripts/checkPlugin.js` → `plugin ok — API 6, 24 API call(s), 12 hook(s) declared, requires Kits`. - The commit subject matches the engine's major rule, `^[a-z]+(\([^)]+\))?!:` (checked with that grep). ## 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:14:35 +00:00

feat!: RunicNPC 1.0.0, the release module-rust requires (runicnpc 9e)

PR Checks / plugin-checks (pull_request) Successful in -2m1s

Details

89df052d7d

Stage 9's release (D311, D313). Every stage before it landed as `feat:`,
so the release engine, which reads non-merge subjects since v0.1.0, would
cut v0.2.0 at the cutover. This commit's `!` makes it v1.0.0, as the plan
and the README say (the org lead's choice, 2026-10-09).

The README's status line now says v1.0.0, and its Releases section says
how the number was reached. No code changes.

BREAKING CHANGE: 1.0.0 is the release a Runic Gateway server requires.
module-rust refuses every Place NPCs step on a server without RunicNPC
(D310), and the bridge declares API 6 as its floor. Nothing in the API
itself changes shape here: it stays version 6.

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

whitlocktech merged commit 2d36028125 into edge

2026-10-09 07:19:34 +00:00

whitlocktech deleted branch chore/v1.0.0

2026-10-09 07:19:35 +00:00

whitlocktech referenced this issue from a commit

2026-10-09 07:19:36 +00:00

Merge pull request 'feat!: RunicNPC 1.0.0, the release module-rust requires (runicnpc 9e)' (#18) from chore/v1.0.0 into edge

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/runicnpc-rust#18