Two small textual-drift items, both verified on origin/develop @ b7c310b.
1. The never-existed mcp-configuration-guide.md path still ships in three files
#2888 repointed the wheels mcp instructions (cli/lucli/Module.cfc:1380 → https://guides.wheels.dev/v4-0-0/command-line-tools/mcp-integration) and the serverInfo.deprecationNotice field in vendor/wheels/public/mcp/McpServer.cfc to the live guide. But docs/command-line-tools/commands/mcp/mcp-configuration-guide.md — a path that has never existed in the repo — still appears in three runtime-visible strings (plus a comment):
vendor/wheels/public/views/mcp.cfm:27 — the one-time-per-JVM deprecation warning actually written to the wheels_mcp log:
text="The in-dev-server MCP endpoint at /wheels/mcp is deprecated. "
& "Use 'wheels mcp wheels' (LuCLI stdio MCP) instead. "
& "See docs/command-line-tools/commands/mcp/mcp-configuration-guide.md"
(and the header comment at mcp.cfm:17 repeats the same path.)
vendor/wheels/public/mcp/McpServer.cfc:1287-1290 — the error string returned to MCP clients that call a disabled CLI-backed tool:
return "Error: CLI-backed tools are disabled on the deprecated /wheels/mcp HTTP endpoint. "
& "Use the stdio MCP server instead ('wheels mcp wheels'; see "
& "docs/command-line-tools/commands/mcp/mcp-configuration-guide.md). "
& "Requested command: " & arguments.command;
cli/src/commands/wheels/mcp/setup.cfc:94 — the CommandBox CLI's wheels mcp setup output:
print.indentedLine("Full guide: docs/command-line-tools/commands/mcp/mcp-configuration-guide.md");
Worth noting: the #2888 CHANGELOG entry says the "deprecated /wheels/mcp endpoint's deprecation notice now point[s] to the live MCP integration guide" — that landed for the serverInfo field, but the mcp.cfm log-warning text and the McpServer.cfc:1289 error string were missed, so the claim is only partially true on develop.
Fix: replace all four occurrences with https://guides.wheels.dev/v4-0-0/command-line-tools/mcp-integration (the URL #2888 standardized on).
2. packages.mdx example manifest ships a "dependencies" key the package loader ignores
web/sites/guides/src/content/docs/v4-0-0/digging-deeper/packages.mdx:91 — the wheels-sentry/package.json example ends with:
But the package system reads requires / replaces / suggests (vendor/wheels/ModuleGraph.cfc:192/125/253); vendor/wheels/PackageLoader.cfc never reads a dependencies key. (dependencies is a legacy plugin manifest key, read only by vendor/wheels/Plugins.cfc.) The guide's own field reference below the example documents requires/replaces/suggests and never mentions dependencies — so the example teaches a key its own doc doesn't define and the loader silently ignores. A reader copying the example and later putting a real dependency in "dependencies" gets no error and no dependency ordering.
Fix: drop the "dependencies": {} line from the example (or replace it with a "requires": {} line to foreshadow the documented key).
Surfaced while fact-checking the Beyond findAll / stdio-MCP blog drafts (2026-06-11).
🤖 Generated with Claude Code
Two small textual-drift items, both verified on
origin/develop@b7c310b.1. The never-existed
mcp-configuration-guide.mdpath still ships in three files#2888 repointed the
wheels mcpinstructions (cli/lucli/Module.cfc:1380→https://guides.wheels.dev/v4-0-0/command-line-tools/mcp-integration) and theserverInfo.deprecationNoticefield invendor/wheels/public/mcp/McpServer.cfcto the live guide. Butdocs/command-line-tools/commands/mcp/mcp-configuration-guide.md— a path that has never existed in the repo — still appears in three runtime-visible strings (plus a comment):vendor/wheels/public/views/mcp.cfm:27— the one-time-per-JVM deprecation warning actually written to thewheels_mcplog:(and the header comment at
mcp.cfm:17repeats the same path.)vendor/wheels/public/mcp/McpServer.cfc:1287-1290— the error string returned to MCP clients that call a disabled CLI-backed tool:cli/src/commands/wheels/mcp/setup.cfc:94— the CommandBox CLI'swheels mcp setupoutput:Worth noting: the #2888 CHANGELOG entry says the "deprecated
/wheels/mcpendpoint's deprecation notice now point[s] to the live MCP integration guide" — that landed for theserverInfofield, but themcp.cfmlog-warning text and theMcpServer.cfc:1289error string were missed, so the claim is only partially true on develop.Fix: replace all four occurrences with
https://guides.wheels.dev/v4-0-0/command-line-tools/mcp-integration(the URL #2888 standardized on).2.
packages.mdxexample manifest ships a"dependencies"key the package loader ignoresweb/sites/guides/src/content/docs/v4-0-0/digging-deeper/packages.mdx:91— thewheels-sentry/package.jsonexample ends with:"dependencies": {}But the package system reads
requires/replaces/suggests(vendor/wheels/ModuleGraph.cfc:192/125/253);vendor/wheels/PackageLoader.cfcnever reads adependencieskey. (dependenciesis a legacy plugin manifest key, read only byvendor/wheels/Plugins.cfc.) The guide's own field reference below the example documentsrequires/replaces/suggestsand never mentionsdependencies— so the example teaches a key its own doc doesn't define and the loader silently ignores. A reader copying the example and later putting a real dependency in"dependencies"gets no error and no dependency ordering.Fix: drop the
"dependencies": {}line from the example (or replace it with a"requires": {}line to foreshadow the documented key).Surfaced while fact-checking the Beyond findAll / stdio-MCP blog drafts (2026-06-11).
🤖 Generated with Claude Code