#3400 retired ork-elicit and merged clean. Then a sweep for the retired
name across every tracked file — not just the ones the change touched — found two live claims
still standing on main. One of them was written by the PR that did the retiring.
| file | claim |
|---|---|
foundations/mcp-servers.mdx :21 | server table row: ork-elicit | Structured form elicitation | 1 |
| :95 | "context7, memory, sequential-thinking, and ork-elicit work immediately — no API keys, no setup" |
| :189 | token-cost table attributing ~300 tokens to it |
docs/fix--3308-retire-ork-elicit/index.html | "docs.ts — 71 lines, never registered, dead" |
The docs page is the same shape as the keybindings page retired hours earlier in #3393: the mechanism is gone, the docs still sell it as zero-config and working. A reader follows it and reaches for a server that does not exist.
CI caught the false "docs.ts is dead" claim mid-#3400 —
Docs MCP image builds failed on COPY src/mcp-server/src: not found, because
docs.ts is registered by a second entry point serving the published Docs MCP
server. I corrected the PR body and the commit message. I did not correct the playground, so the
false statement merged into main as a durable artifact.
It now shows both entry points, states the correction, and carries the row it should have had from
the start: Every entry point enumerated first — NO.
git grep -ln "ork-elicit\|ork_elicit\|registerElicitTool\|elicitation" -- .
| hit | verdict |
|---|---|
foundations/mcp-servers.mdx | live claim → fixed |
| this PR's target playground | false claim → fixed |
fix-issue/SKILL.md "rich elicitation" | generic word, not the server |
reference/hooks/index.mdx Elicitation / ElicitationResult | Claude Code's own hook events |
CHANGELOG.md, docs/audits/**, prior playgrounds | historical record, must not change |
.claude/audit-allowlist.json | already fixed in #3400 |
Six hit classes, two actionable. A sweep that "fixed" all six would have rewritten history and broken two correct references — the classification is the work, not the grep.
The rule this earns. A retirement is not done when the code is deleted and CI is green. It is done when the retired name appears nowhere that a reader would take as a live instruction — docs pages, cost tables, allowlist justifications, and the retirement's own writeup. Three times today a deletion looked complete and left a claim behind: the keybindings docs after #3357, the eight test/CI references after the first #3400 push, and these two after it merged. The grep is cheap and it goes last, after the build is green, not before.