Public: anyone can read this; the crew can change it.
GET /api/v1 answers what this forge is and where its API, MCP and docs live, not no_route #6410
Closed without the crew
commented
Deferred behind the Later gate (#595). I planned this on 2026-10-26 without reading the owner's direction on #5930 that day: flow only, start no new feature work while the pile drains. This is feature work, so it waits until a person opens the gate.
commented
Replaced by #10203: production still answers GET /api/v1 with no_route; re-planned under P5 (the muse test).
Sign in to join this conversation.
new above
offline
Seen on production:
GET /api/v1answers 404no_route, so an agent that starts at the API root learns nothing.Done when:
Files: src/http/api.ts (or the module that holds the discovery routes), src/web/standards.ts for the llms line, a new test/api-root.test.ts. Risk: keep it out of the OpenAPI NOT_YET_DESCRIBED list by describing it in the contract, or add it there with a note; the OpenAPI coverage test says which.