- Split the Godot API snapshots in the directory tree into parts under the scanner's 256 KiB; apicheck merges them back.
- Give agentdisk only the folder variables it reads.
- Take the GitHub token for lookup from the plugin's optional, secret github_token setting (REVERSEPORT_GITHUB_TOKEN).
Without TEMP and TMP, Windows falls back to C:\Windows\temp, which a normal account may not open, so every analysis in the Qwen client verifier failed with "Access is denied". verifierHostEnvironment() now also keeps TEMP and TMP on Windows. verify:qwen-client passes on Windows 11 with Qwen Code 0.23.3.
Claude Code now defers a large MCP catalog behind ToolSearch (at most 64 tools per call) and saves a large tool result to a file with a <persisted-output> preview. The Claude client fixture now loads the missing REA tools with ToolSearch select: in batches before checking the complete catalog, and reads a persisted result only when it lies inside the verifier lab. The client verifier passes again against Claude Code 2.1.317.
On Windows with core.autocrlf=true, Git checks out patches/release-please+17.3.0.patch with CRLF line endings, so `git apply` in prepare no longer matches the LF dependency sources and `npm ci` fails. The repository cannot pin line endings with .gitattributes (the Claude plugin directory rejects one), so applyReleasePleasePatch now applies an LF copy from a temporary directory when the patch has CRLF line endings. The regression test runs the existing fixture with a CRLF patch.
The Qwen, Gemini, Command Code and Harness client verifiers built an isolated environment with only PATH and their own home variables. On Windows a child Node process without SystemRoot aborts with `Assertion failed: ncrypto::CSPRNG(nullptr, 0)`, and npm .cmd shims also need ComSpec and PATHEXT. Keep those four host variables on Windows only, and test the selection, its use in each verifier, and a child Node start on Windows.
The Harness row keeps its `rea-mcp` id for ownership, but `serverName` must be `reverseport`; a row that still says `rea` is stale and setup rewrites it. Correct the stale-check comment and assert the migrated row connects as `reverseport` over stdio.
Setup and connect registered the server as "rea" while the Claude plugin
used "reverseport"; there is now one server name, "reverseport". The CLI
command "rea" stays as an alias. Setup and update move a REA-owned "rea"
registration to the new name with approval and a backup; foreign or
unknown "rea" entries are left untouched and reported; uninstall removes
owned entries under both names.
Also fixes the 35 confirmed review findings on the Unity reader (#89).
BREAKING CHANGE: clients now see the server as "reverseport", so tool
names change from mcp__rea__* to mcp__reverseport__*. Rerun
`reverseport setup` (or `reverseport update`) to move an existing "rea"
registration; permission rules naming mcp__rea__* need updating.
Roel