8000 fix(deps): upgrade zod 3 to 4 to clear the remaining security advisory by Mnehmos · Pull Request #115 · Mnehmos/mnehmos.rpg.mcp · GitHub
[go: up one dir, main page]

Skip to content

fix(deps): upgrade zod 3 to 4 to clear the remaining security advisory - #115

Merged
Mnehmos merged 16 commits into
mainfrom
claude/practical-cannon-cel9je
Nov 10, 2026
Merged

Mnehmos merged 16 commits into
mainfrom
claude/practical-cannon-cel9je

Conversation

@Mnehmos
@Mnehmos Mnehmos commented Nov 10, 2026
Copy link
Copy Markdown
Owner

Last item from the engine audit. npm audit --omit=dev reported a memory-exhaustion advisory in zod that is fixed only in zod 4. After this PR it reports 0 vulnerabilities.

What changed

  • z.record() takes an explicit key schema (z.record(z.string(), …)), 27 call sites. Same behaviour.
  • Object defaults. zod 4's .default(v) returns v as is; zod 3 parsed it. Three schemas relied on that to fill inner defaults from .default({}) (currency on characters and inventory), so they now use .prefault({}), which keeps the zod 3 behaviour. Checked live: a new character still gets {"gold":10,"silver":0,"copper":0}.
  • UUID fields use z.guid(). zod 4's .uuid() enforces RFC version and variant bits and would reject ids zod 3 accepted.
  • load_tool_schema summarizer (meta-tools.ts) read zod 3 internals (_def.typeName). It now reads zod 4 definitions. schema-shape.ts likewise.
  • Small type-only fixes: ZodError.issues, ZodObject, ZodType.

Contract check for rpg-mcp-live

I captured tools/list, load_tool_schema for all 36 tools, and a search_tools call from a running server on zod 3, then again on zod 4, and compared them.

Surface Result
load_tool_schema (all 36 tools, 314 KB) Byte-identical
search_tools Identical
tools/list JSON Schema 177 differences, all in the list below

The tools/list schemas are generated by the MCP SDK, which uses zod 4's own JSON Schema output for zod 4 schemas:

  • additionalProperties: false is no longer emitted (71 places, including the top level of every tool). Runtime behaviour is unchanged: unknown keys are still stripped, not rejected. This matters only if the web service passes these schemas to a provider mode that requires additionalProperties: false.
  • .int() fields gain minimum/maximum at the safe-integer bounds (82).
  • z.array(z.any()) gains items: {} (9); records gain propertyNames: { type: "string" } (9).
  • The three guid fields gain a pattern (3).
  • agent_manage.kind is an anyOf of two enums instead of one merged enum (same allowed values).

Validation error text changes. zod 4 words its messages differently, e.g. a missing actorId now reads Invalid input: expected string, received undefined at actorId. The response is still isError: true.

Testing

  • New contract tests in tests/server/meta-tools.test.ts pin the load_tool_schema summary for each kind of schema the tools use (literal, union, array, object, record, enum, default, described optional) and check no zod 4 internal type name appears in any tool's summary.
  • Full suite locally: 2373 passed, 7 skipped, 3 failed. The 3 are tests/server/websocket.test.ts, which cannot bind :: in the sandbox this ran in; they pass in CI.
  • On one full run, spellcasting.test.ts "12.1 - fire bolt damage scales with character level" failed, then passed on 6 consecutive isolated runs and on the next full run. It depends on unseeded attack rolls hitting and already carries retry: 3 on main; it is not related to this change.

Note on history

The branch could not be force-pushed after #113 and #114 were squash-merged, so their history is recorded with an ours merge that leaves the tree unchanged. The diff against main is only this change.


Generated by Claude Code

claude added 16 commits November 9, 2026 20:42
…e server

An exploding one-sided die (1d1!) never stopped exploding, and dice counts
were unbounded, so one math_manage call could freeze or kill the process
for every campaign. Dice are now capped at 1000 dice of 1000 sides at every
parser, exploding dice need at least 2 sides, and exact distributions are
refused when too large to compute.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
subscribe_to_events left a callback pointing at the per-request HTTP
transport. The next combat event in any campaign made it reject with
'Not connected'; the unhandled rejection shut the process down, and the
shutdown path exited 0, so the host never restarted it.

- Crashes now exit 1; requested stops still exit 0.
- A subscriber whose connection is gone is dropped, not left to reject.
- Subscribers only receive events from their own campaign.
- On the stateless HTTP transport, where nothing can be pushed after the
  response, subscribe_to_events makes no subscription and points the
  caller at poll_events.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
- Moves are validated (destination, path, remaining movement) before
  opportunity attacks resolve. A refused move used to cost the mover hit
  points and the attacker its reaction, then report success. It is now an
  error, so the call rolls back.
- Negative damage is rejected; it was subtracted as healing with no cap
  at max HP (a 7 HP goblin reached 107). Dice damage with a penalty
  floors at zero, and applyDamage/heal ignore negative amounts.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
npm audit fix: clears the advisories in @modelcontextprotocol/sdk and its
transitive dependencies. The remaining zod advisory needs a breaking move
to zod 4 and is left for a separate change.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
- An attack outside the attacker's turn now resolves as its reaction, one
  per round, and no longer spends its action. It used to be a warning
  only, so a combatant could attack any number of times off turn.
- A target must be within reach: 5ft for melee, or the new optional
  `range` (feet) for ranged and reach attacks. Checked only when both
  combatants have a position.
- Caller-supplied attackBonus, dc and damage are bounded (-20..30, 1..40,
  1000 damage), so one call can no longer decide the outcome.
- Opportunity attacks use the attacker's attack bonus and the mover's AC
  when known instead of deriving both from initiative.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
…g call

Pool eviction closed the least recently used handle even when a call was
mid-transaction on it, and DELETE /campaign did the same. Eviction now
skips handles that are in use, and erasure waits for the call in flight.
The pool cap can be set with RPG_MAX_OPEN_DATABASES (default 64).

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
Cached worlds were keyed by a guessable id alone and never evicted, so one
campaign could read another's world by id and memory grew for the life of
the process. Entries are now keyed by the verified tenant too, and the
cache keeps the most recently used worlds (RPG_MAX_CACHED_WORLDS, default
32); the rest are restored from their database snapshot on demand.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
…ng it

A hosted campaign that failed its integrity check was quarantined and
swapped for an empty database, so the game looked deleted and play
continued into a second file. Campaign databases now fail to open and the
files are left untouched. Local single-user databases keep the
quarantine-and-recreate behaviour.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
audit_logs stored arguments and results for every tool call and was never
pruned. It now keeps the newest RPG_AUDIT_LOG_MAX_ROWS rows (default 5000).

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
… URLs

better-sqlite3 12 requires Node 20+, so CI no longer tests 18 and
package.json declares the engine. The HTTP transport builds a server per
request and logged tool registration every time; it now logs once.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
The tool's outer input schema dropped the new range argument before it
reached the handler, so a ranged attack could not be made over MCP.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
The earlier commits on this branch were squash-merged as #113. This merge
keeps the current tree exactly as it is; it only records that history so
the branch can be pushed without rewriting it.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
npm audit reported a memory-exhaustion advisory fixed only in zod 4.

- z.record() takes an explicit key schema.
- Object defaults that relied on inner defaults use .prefault(), which
  parses the default as zod 3 did (zod 4's .default() returns it as is).
- UUID fields use z.guid() to keep zod 3's lenient matching.
- load_tool_schema's summarizer read zod 3 internals; it now reads zod 4
  definitions and produces byte-identical output for all 36 tools.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
Tree unchanged. The earlier commits on this branch were squash-merged as
#113 and #114.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
@coderabbitai
coderabbitai Bot commented Nov 10, 2026 •
Copy link
Copy Markdown

Explain Change →

Caution

Review failed

The pull request is closed.

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@Mnehmos
Mnehmos marked this pull request as ready for review November 10, 2026 01:05
@Mnehmos
Mnehmos merged commit b6d3fcb into main Nov 10, 2026
4 checks passed
@chatgpt-codex-connector
chatgpt-codex-connector Bot commented Nov 10, 2026 •
Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-10T01:07:14.753867Z e9d9b8e Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e9d9b8e881

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread package.json
"uuid": "^13.0.0",
"ws": "^8.16.0",
"zod": "^3.25.76"
"zod": "^4.6.7"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve omitted ability scores when parsing partial updates

When batch_manage.execute_sequence invokes character_manage with an update such as stats: { str: 18 }, Zod 4 now applies the inner defaults in StatsSchema.partial(), producing all six scores with the omitted five set to 10. handleUpdate in src/server/consolidated/character-manage.ts assigns this parsed object directly to updateData.stats, and CharacterRepository.update persists it, silently overwriting existing ability scores. This batch path calls the tool handler directly, bypassing the shared registration schema; under Zod 3 the partial parser did not supply these defaults. Remove defaults from the update-specific stats schema and merge supplied scores with the existing stats before persistence.

Useful? React with 👍 / 👎.

Mnehmos pushed a commit that referenced this pull request Nov 10, 2026
Tree unchanged. The earlier commits on this branch were squash-merged as
#113, #114 and #115.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0