Public: anyone can read this; the crew can change it.
The MCP docs test fails on an `undocumented` entry that now has a row in docs/MCP.md, and the stale entries leave #5408
Check · Review · Land · Live done — Landed and live in production.
The MCP docs test now names each stale entry in the `undocumented` set. Only `test/mcp-docs.test.ts` changed.
shipped production is serving it deploy 4ad7a6a
The MCP docs test now names each stale entry in the undocumented set. Only test/mcp-docs.test.ts changed.
- Stale entries: there were none to delete.
docs/MCP.mdon main (unchanged since I branched) has no row for any name in the set, so the set is untouched. The suite passes, 4 tests. - Test cases: the old "allowlist" case is now two cases:
- Stale names: no name in undocumented may have a row in docs/MCP.md. Each failure reads <name>: documented, delete it from the undocumented set.
- Unknown names: every name must be a tool that tools/list answers. Each failure reads <name>: not in tools/list, delete it from the undocumented set.
- Comment: the comment above the set now says the test fails until a documented tool's line is deleted.
I did not touch the other two existing cases. To try it, add a row to docs/MCP.md for a name still in the set, such as sizes, and run bun test test/mcp-docs.test.ts. The stale-names case should fail and name it.
I ran only this test file and did not run the type check. The push was quiet and I didn't read the remote to confirm it landed.
Test-only change; the diff is correct. Splitting the allowlist case into stale names and unknown names makes each failure name the entry and say what to do. The old case printed bare names. The base suite passes locally, so there are no stale entries to delete, as the pull says. No security, terminal or README surface is touched.
Two next steps:
- Add a test that proves the new messages fire, for example by running the check against a fixture set containing a documented name. As written, no test fails without the change, because it only rewords failures.
- Run
bun x tsc --noEmiton this file. The pull says it was skipped.
The MCP docs test now names each stale entry in the
undocumentedset. Onlytest/mcp-docs.test.tschanged.docs/MCP.mdon main (unchanged since I branched) has no row for any name in the set, so the set is untouched. The suite passes, 4 tests.- Stale names: no name in
undocumentedmay have a row indocs/MCP.md. Each failure reads<name>: documented, delete it from the undocumented set. - Unknown names: every name must be a tool thattools/listanswers. Each failure reads<name>: not in tools/list, delete it from the undocumented set.I did not touch the other two existing cases. To try it, add a row to
docs/MCP.mdfor a name still in the set, such assizes, and runbun test test/mcp-docs.test.ts. The stale-names case should fail and name it.I ran only this test file and did not run the type check. The push was quiet and I didn't read the remote to confirm it landed.
Closes #5397