8000 fix: report missed spell attacks, and tighten the agent runtime by Mnehmos · Pull Request #116 · Mnehmos/mnehmos.rpg.mcp · GitHub
[go: up one dir, main page]

Skip to content

fix: report missed spell attacks, and tighten the agent runtime - #116

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

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

Conversation

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

Two follow-ups from the engine audit: the flaky spellcasting test (which turned out to be a real bug) and an audit pass over the agent runtime.

Spell attacks that miss

spellcasting.test.ts "12.1 - fire bolt damage scales with character level" failed by chance and carried retry: 3. Repeating it 60 times showed why: when a spell attack missed, the response was a bare casts Fire Bolt! with no attack roll, no dice and no word that it missed. The caller could not tell a miss from a hit for zero damage.

A missed spell attack now goes through the same formatter as a hit, so it reports the roll, the dice and The spell missed!. The test no longer depends on three unseeded attacks all hitting, the retry is removed, and a new deterministic test covers the miss.

Agent runtime

  • Replay bypassed the no-pro-model rule. invoke enforces it through the competency ladder and overrides; live replay took model straight from the caller. It now refuses a pro variant before calling the provider.
  • timeoutMs had no upper limit. The provider call runs inside the campaign's unit of work, holding its lock and an open write transaction, so every other call on that campaign waits behind it. New and updated agents are capped at 120s (MAX_AGENT_TIMEOUT_MS); rows stored before the limit are clamped when used rather than rejected.
  • Timeouts during the body read were misrecorded. An abort that landed while reading the response body escaped as a bare AbortError and was stored as a generic error. Both providers now classify it as timeout.

Contract changes for rpg-mcp-live

  • agent_manage create/update with timeoutMs above 120000 returns a validation error.
  • agent_manage replay with a pro model returns error: true.
  • A missed spell attack's text now includes the attack roll and a miss line. The [SPELL: …] tag and STATE_JSON block are unchanged.

Found but not changed

  • Replay does not count tokens against the agent's budget and skips preflight. Existing tests assert this on purpose ("NEVER mutates the agent", "paused agent still replayable"), so it is a design choice, but it does mean a budget-exhausted agent can still spend through replay.
  • Token accounting is rolled back with the call. If a next_turn auto-invoke succeeds and the enclosing call then fails, the provider was paid but tokensUsed is restored.
  • The competency ladder JSON is read from disk on every invoke.

Testing

  • New: missed-spell test in tests/server/spellcasting.test.ts, tests/agent/runtime/timeout-bounds.test.ts, a replay model-policy test in tests/agent/audit/replay.test.ts, body-read timeout tests in tests/agent/provider/openai.test.ts.
  • Full suite locally: 2380 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.

Note on history

The branch could not be force-pushed after the earlier PRs 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 19 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
A missed spell attack returned a bare 'casts Fire Bolt!' with no attack
roll, no dice and no miss, so the caller could not tell a miss from a hit
for zero damage. It now uses the same formatter as a hit. The fire bolt
scaling test depended on three unseeded attacks all hitting and was
retried to hide that; it is now deterministic and the retry is gone.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013FWeViVwVRAxVuCWaf7UQS
- Live replay took its model straight from the caller, so it bypassed the
  no-pro-model rule that invoke enforces. It now refuses a pro variant
  before calling the provider.
- timeoutMs had no upper limit. The provider call runs inside the
  campaign's unit of work, holding its lock and an open transaction, so a
  huge timeout could stall a campaign. New and updated agents are capped
  at 120s; rows stored earlier are clamped when used.
- An abort that landed while reading the response body escaped as a bare
  AbortError and was recorded as a generic error; it is now a timeout.

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, #114 and #115.

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 02:49
@Mnehmos
Mnehmos merged commit b48b45d 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-10T02:50:21.620257Z 5b8b85f 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.

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 to #116.

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