I2732 — The MCP reference repeats no registry entry: no hand-written document lists tools
Remove the second inventory of MCP tools from docs/MCP.md and hold every hand-written document under docs/ to naming tools in prose, so the next composed module cannot be missing from a list nobody regenerates.
READY wave 0 · p2 · implementation profile · parallel safe
Ready. Every dependency is done, so majordomus plan start I2732 will be accepted.
Objective
Remove the second inventory of MCP tools from docs/MCP.md and hold every hand-written document under docs/ to naming tools in prose, so the next composed module cannot be missing from a list nobody regenerates.
Why
On 2026-10-15 the 0.27.0 integration top (#1183) went red on case 532 while the new capability worktree.uncommitted reached the registry and every generated page; tracing it showed that docs/MCP.md's five hand-written tool tables (29 rows: tool, capability, arguments, answers) did not carry it. Those tables repeated the registry, which CLAUDE.md and ADR 0004 call a design defect, and the generated reference already exists: docs/generated/capabilities.md and the site's /registry/mcp/, which case 532 holds to the registry.
Current state
docs/MCP.md carries hand-written tool tables under Peers, Episodes, Tools and Sessions and continuity; nothing checks them against the registry, and majordomus_worktree_uncommitted is absent from them.
Desired state
docs/MCP.md names each tool in prose where it explains why it exists, and links the derived reference for arguments and answers (docs/generated/capabilities.md, /registry/mcp/, majordomus_capability at runtime; the local-only session tools through majordomus capabilities describe). Case 3062 refuses a table row whose first cell is a majordomus_ tool in any tracked Markdown document under docs/ outside docs/generated/, after proving its pattern on a planted row and a planted non-row.
Scope
- docs/MCP.md
- test/cases/3062_the_mcp_reference_repeats_no_registry_entry.sh
- .ai/repo/project/issues/I2732.yaml
Out of scope
- Generating a tool table into a region of docs/MCP.md, which would need a region projection in majordomus generate
- The site's /registry/mcp/ page, which is already derived and held by case 532
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- No tracked document under docs/ outside docs/generated/ has a table row whose first cell is a backticked majordomus_ tool name
- Case 3062 fails on the tables docs/MCP.md carried before this change and passes after it
Validation
- bin/majordomus plan validate
- test/run.sh 3062_the_mcp_reference_repeats_no_registry_entry
Evidence required
- the_mcp_reference_repeats_no_registry_entry_case
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I2732.yaml. Read it back with majordomus plan show I2732.