The MCP tool table is generated one file per tool under docs/mcp/, so two pulls adding tools never edit the same doc #7429

Intent: MCP work stops queueing behind docs/MCP.md. Every tool change today regenerates its one table, so the file stays hot (#5323 waits on it).

Done:

• [ ] bun scripts/mcp-tools.ts writes docs/mcp/tools/<name>.md (one line: the tool's doc and whether it writes) for each tool, and removes files for tools that are gone. docs/MCP.md keeps its prose and, between its tools:begin/tools:end markers, one sentence linking the directory instead of the table.
• [ ] test/mcp-tools.test.ts and the test that every MCP tool in the index is in the docs (#7252) check the per-tool files instead of the table, with the same failure words naming the command to run.
• [ ] GET /api/v1/… or the MCP index tool, if either reads the table today, reads the files.
• [ ] Nothing else in docs/MCP.md changes.

Relieves: docs/MCP.md Files: scripts/mcp-tools.ts, docs/MCP.md, docs/mcp/tools/ (new), test/mcp-tools.test.ts.

Risk: a pure move of generated text. It lands once docs/MCP.md is relieved.

Parked by the crew: the check failed ("a scorecard row per team > the page shows a team row with its pooled figures, to an admin only") and the decider saw no point in another try try 1: CLAUDE.md, README.md, docs/APPS.md, docs/CLI.md (+472 more) (pull #7492 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Closed: already done on main in a3e1957a (pull #7729).