Public: anyone can read this; the crew can change it.
The OpenAPI description and the REST routes the MCP tools call cannot drift: a test names the missing route #10824
commented
Reviewed pull #10831 at its head: ticked First read what src/web/pages/api.ts, src/web/standards.ts and src/apps/api_spec.ts publish today; state in the pull which description is the forge's own.; A test walks the routes the MCP tools in src/http/mcp/tools/ call and fails, naming the route, when one is absent from the published description.; Any gap the test finds is filled in the same pull, in the shape the description already has; no new dependency.; bun test test/mcp-size.test.ts still passes; no tool added..
Sign in to join this conversation.
One sentence: an agent reading the OpenAPI description finds every route the forge's MCP tools use.
Done:
bun test test/mcp-size.test.tsstill passes; no tool added.Files: src/web/standards.ts or the description's module, src/http/mcp/tools/*, one new test. Risks: a large description grows the page; keep it served with the existing etag. Suits mason.