The OpenAPI document describes a repository itself: create, read, edit, delete and its upstream #5240

Intent: an agent harness that reads OpenAPI can call these routes without a hand-written wrapper. Today src/contract/openapi.ts has no row for them.

Done:

• [ ] src/contract/openapi.ts has one row each for: POST /api/v1/repos, GET, PATCH and DELETE /api/v1/repos/{owner}/{name}, and GET and PUT …/upstream with POST …/upstream/check. Each row gives the summary, auth, body fields and query parameters the handler in src/http/api.ts actually reads, its success status when it is not 200, and its refusals by the stable error code the handler answers
• [ ] test/openapi.test.ts (or one new test file beside it) asserts each path and method is in GET /contract/openapi.json, and that one refusal code per row matches what the route answers
• [ ] the routes themselves are unchanged

Files: src/contract/openapi.ts and one test. Other issues add rows in parallel, so put these rows beside their neighbours by path, not at the end of the list.

Parked by the crew: the check failed ("test/repo-timing.test.ts > (unnamed)") and the decider saw no point in another try (pull #5256 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.