Intent: a harness follows what the crew is doing in a repository through OpenAPI alone.
Done:
[ ] rows in src/contract/openapi.ts for GET {REPO}/runs, {REPO}/runs/{id} and {REPO}/runs/{id}/log, POST {REPO}/runs/{id}/cancel, GET {REPO}/usage and POST {REPO}/spend, placed right after the existing POST {REPO}/issues/{number}/comments row
Each row says what the route answers (the shape in its summary, exactly as the handler answers today), whether it needs a token (auth) and which scope, and its body fields, query and refusals, as the existing rows do. Use the methods src/http/api.ts registers. If a route needs "put" and #4844 has not yet added it to the Route method type, leave that route out and say so in the pull; do not add it here, because other issues would collide on that line. test/openapi.test.ts must still pass; add test/openapi-oa-runs.test.ts asserting each new path and method is in the served document. Other issues add rows in parallel, so put these exactly where named and nowhere else.
Intent: a harness follows what the crew is doing in a repository through OpenAPI alone.
Done:
{REPO}/runs,{REPO}/runs/{id}and{REPO}/runs/{id}/log, POST{REPO}/runs/{id}/cancel, GET{REPO}/usageand POST{REPO}/spend, placed right after the existing POST{REPO}/issues/{number}/commentsrowEach row says what the route answers (the shape in its summary, exactly as the handler answers today), whether it needs a token (
auth) and which scope, and its body fields, query and refusals, as the existing rows do. Use the methods src/http/api.ts registers. If a route needs"put"and #4844 has not yet added it to theRoutemethod type, leave that route out and say so in the pull; do not add it here, because other issues would collide on that line.test/openapi.test.tsmust still pass; add test/openapi-oa-runs.test.ts asserting each new path and method is in the served document. Other issues add rows in parallel, so put these exactly where named and nowhere else.