docs(web/blog): close the MCP-drift paragraph in the stdio-MCP post#3216
Conversation
The "second piece of drift" paragraph claimed, present tense, that the deprecated /wheels/mcp endpoint "still" advertised the phantom mcp-configuration-guide.md path and that aligning it was "its own follow-up". That follow-up has since shipped (the 4.0.x audit sweep): both vendor/wheels/public/views/mcp.cfm and the hand-written McpServer.cfc point to the live guide, and McpDeprecationNoticeStaleDocPathSpec guards against the phantom path returning. Reframe the paragraph so a reader today sees the loop is closed. Exported from the publishing admin (post #1057). Signed-off-by: Peter Amiri <petera@pai.com>
![wheels-bot[bot]](https://avatars.githubusercontent.com/in/3657588?s=60&v=4){kind=small}
There was a problem hiding this comment.
Wheels Bot — Reviewer
TL;DR — This PR rewrites one paragraph of the published wheels-claude-stdio-mcp blog post so it reflects that the /wheels/mcp deprecation-notice doc drift has since been closed, rather than describing it as an open follow-up. Every factual claim in the new prose was checked against the current tree and holds. Verdict: approve.
Correctness
The rewritten paragraph asserts three things; all three are accurate against 04474907c:
- "both references now point to the live guide" — confirmed.
vendor/wheels/public/views/mcp.cfm:17and:27both citehttps://guides.wheels.dev/v4-0-0/command-line-tools/mcp-integration, andvendor/wheels/public/mcp/McpServer.cfc(lines 11, 1289) does the same. A repo-wide grep for the oldmcp-configuration-guidestring returns nothing outside the guard spec itself. - "a regression test (
McpDeprecationNoticeStaleDocPathSpec) fails the build if the phantom path ever creeps back" — confirmed.vendor/wheels/tests/specs/cli/McpDeprecationNoticeStaleDocPathSpec.cfc:24-48pins the phantom path and assertsexpect(content contains phantomPath).toBeFalse(...)over the runtime-visible files. - The CLI-first / endpoint-lagged framing matches the actual history described in the PR body (the 3016 audit sweep).
No factual or grammatical issues; the paragraph is well-formed and closes cleanly.
Conventions
updatedAt bumped to 2026-06-16T19:33:31.000Z, consistent with an edited post (today is 2026-06-16). No other front-matter touched. Nothing to flag.
Commits
Single commit docs(web/blog): close the MCP-drift paragraph in the stdio-MCP post — valid type docs, suggested scope web/blog, lowercase subject, header under 100 chars. Conforms to commitlint.config.js.
No changelog fragment or test changes are warranted — this is blog content, not a user-facing framework fix/feat or a behavior change.
wheels-bot
Bot
dismissed
their stale review
Auto-dismissed by the Reviewer guard: body is shorter than 200 characters or missing the canonical wheels-bot:review-a marker. See #2558 for context.
Wheels Bot — Reviewer guardDetected and dismissed 1 bogus Reviewer review(s) on commit |
1 participant
Corrects one now-stale paragraph in the published
wheels-claude-stdio-mcppost (#1057). It claimed the deprecated/wheels/mcpendpoint still advertised the phantommcp-configuration-guide.mdpath as an open follow-up; that follow-up shipped in the 4.0.x audit sweep (#3016) —vendor/wheels/public/views/mcp.cfmandMcpServer.cfcboth point to the live guide, withMcpDeprecationNoticeStaleDocPathSpecguarding it. Reframed so the loop reads as closed. Exported from the publishing admin; merging rebuilds blog.wheels.dev.