From 89df052d7daf7548e93907886eef4a6ce4be53aa Mon Sep 17 00:00:00 2001 From: wtclaude Date: Fri, 9 Oct 2026 02:14:13 -0500 Subject: [PATCH] feat!: RunicNPC 1.0.0, the release module-rust requires (runicnpc 9e) 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 Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 8c9e4e7..891a161 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ works on its own, and on a [Runic Gateway](https://gitea.whitlocktech.com/RunicG website authors its NPC profiles and events use its NPCs. The plan of record, stage by stage, is [`docs/runicnpc/PLAN.md`](https://gitea.whitlocktech.com/RunicGateway/docs/src/branch/main/runicnpc/PLAN.md). -> **Status: stage 9, hardening for v1.0.0.** The NPC, its profiles, placements and routes; factions, +> **Status: v1.0.0, stage 9's release.** The NPC, its profiles, placements and routes; factions, > fights, escorts and tethers; bosses and passive NPCs; loot. Admins use the `/rnpc` commands, other > plugins the API (version 6). On a Runic Gateway server RunicNPC is **required** (D310): the website > authors its profiles and faction table, edits its placements, and every NPC an event places is @@ -184,7 +184,8 @@ and +5.2 ms fighting to the median frame. Load `tools/RunicNpcTest.cs` on a rig Work lands on `edge` and is cut over to `main`; every releasable push to `main` tags and publishes a release (`.gitea/workflows/release.yml`). The version comes from Conventional Commits since the -last tag. `v1.0.0` is stage 9's release, the one `module-rust` then requires. +last tag. `v1.0.0` is stage 9's release, the one `module-rust` requires; it was cut by a `feat!:` +commit, because the stages before it were all `feat:` and would have made it `v0.2.0`. ## Contributing