fix(swagger): regenerate the fragment for stage 9's runicNpc status field #35

wtclaude · 2026-10-07T02:47:13Z

wtclaude commented

2026-10-07 02:47:13 +00:00

What & why

edge is red. On run 38 (#34, RunicNPC stage 9), server-tests passed all 474 tests (# fail 0) and then failed at npm run check:swagger, with "swagger-fragment.json is STALE".

Stage 9 (d140d5c) added a runicNpc object (ready, absence, version, api) to the server-status schema in server/swagger/doc.js but never regenerated swagger-fragment.json. This PR is the output of npm run swagger and nothing else: 74 added lines, all of them the runicNpc block.

The new block renders type/description as nested properties. The existing zoneHelper entry beside it renders the same way, so that's how swagger-autogen has always handled doc.js here, not something this PR introduced.

How it was tested

npm run swagger → wrote swagger-fragment.json — 75 paths
npm run check:swagger → swagger-fragment.json is current — 75 paths
I didn't run the test suite locally. Run 38's log already shows it passing, and this PR changes no code. CI will run it again here.

Checklist

I have read CONTRIBUTING.md.
The change builds and existing tests/checks pass locally. (Locally I ran only check:swagger, which passes; see above.)
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 `edge` is red. On run 38 (#34, RunicNPC stage 9), `server-tests` passed all 474 tests (`# fail 0`) and then failed at `npm run check:swagger`, with *"swagger-fragment.json is STALE"*. Stage 9 (`d140d5c`) added a `runicNpc` object (`ready`, `absence`, `version`, `api`) to the server-status schema in `server/swagger/doc.js` but never regenerated `swagger-fragment.json`. This PR is the output of `npm run swagger` and nothing else: 74 added lines, all of them the `runicNpc` block. The new block renders `type`/`description` as nested `properties`. The existing `zoneHelper` entry beside it renders the same way, so that's how swagger-autogen has always handled `doc.js` here, not something this PR introduced. ## How it was tested - `npm run swagger` → `wrote swagger-fragment.json — 75 paths` - `npm run check:swagger` → `swagger-fragment.json is current — 75 paths` - I didn't run the test suite locally. Run 38's log already shows it passing, and this PR changes no code. CI will run it again here. ## Checklist - [x] I have read [CONTRIBUTING.md](CONTRIBUTING.md). - [ ] The change builds and existing tests/checks pass locally. *(Locally I ran only `check:swagger`, which passes; see above.)* - [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-07 02:47:14 +00:00

fix(swagger): regenerate the fragment for stage 9's runicNpc status field

PR Checks / client-build (pull_request) Successful in 17s

Details

PR Checks / frozen-manifest (pull_request) Failing after 32s

Details

PR Checks / server-tests (pull_request) Successful in 7m32s

Details

8b6e96086f

RunicNPC stage 9 (#34, D310) added a runicNpc object to the server status
schema in server/swagger/doc.js but did not regenerate swagger-fragment.json,
so check:swagger turned server-tests red on run 38 and edge has been red
since the merge. This is the output of `npm run swagger`, nothing else.

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

whitlocktech merged commit 4ad38d443b into edge

2026-10-07 02:47:38 +00:00

whitlocktech deleted branch fix/swagger-fragment-stage9

2026-10-07 02:47:39 +00:00

whitlocktech referenced this issue from a commit

2026-10-07 02:47:39 +00:00

Merge pull request 'fix(swagger): regenerate the fragment for stage 9's runicNpc status field' (#35) from fix/swagger-fragment-stage9 into edge

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/Module-Rust#35