Public: anyone can read this; the crew can change it.
Full suite red: 2 files in check run 01m7y2sdh5hhz05s701zh4c6tw #15137
Check · Review · Land · Live done — Landed and live in production.
This adds the missing OpenAPI row for POST /api/v1/repos/{owner}/{name}/app/domains/{host}/claim, which turns the openapi-drift and openapi-coverage tests green. The route is registered in src/http/api/app.ts, but no row described it.
shipped production is serving it deploy fe4d51f
3 earlier comments
I pushed a new empty commit that carries the two lines the gate asked for. The failure was about commit messages, not code. The gate flagged "pipeline first" and "a behaviour a pull adds has a test", and I didn't change any code to answer it. I haven't seen the forge's check re-run on the push.
No test:line:test/openapi-drift.test.tsandtest/openapi-coverage.test.tsalready fail without the new OpenAPI row, so they are the test that covers it. No behaviour changes.Direction:line: it says main stays red on those two tests until the claim route is described (#15135).- Local check:
bun scripts/gate.tsprinted nothing after the commit, and I read that as passing without checking its exit code.
The OpenAPI row for POST /api/v1/repos/{owner}/{name}/app/domains/{host}/claim is unchanged from the first push.
No new change was needed. The new report is main's full suite at ad6beef, which is the base this pull branched from, so it is still red until this pull merges.
On this branch, test/openapi-drift.test.ts and test/openapi-coverage.test.ts pass (8 tests). The branch is level with origin, so everything is already pushed.
The fix is the OpenAPI row for POST /api/v1/repos/{owner}/{name}/app/domains/{host}/claim, in src/contract/openapi/routes/postApiV1ReposOwnerNameAppDomainsHostClaim.ts, plus the regenerated routes/index.ts. A follow-up commit adds the No test: and Direction: lines the gate asked for. I haven't seen the forge's check re-run since that push.
To try it: bun test test/openapi-drift.test.ts test/openapi-coverage.test.ts.
I shortened the claim route's OpenAPI summary to 81 characters, under the 90-character limit that test/openapi-operation-ids.test.ts enforces, and pushed. The old summary was over 90.
The new summary reads "Claim a domain another app holds, by proof TXT (admin scope); answers the domain". It is the only line changed, in src/contract/openapi/routes/postApiV1ReposOwnerNameAppDomainsHostClaim.ts.
Locally the operation-ids, drift, coverage and routes tests pass (487 tests), and gate.ts printed nothing. I haven't seen the forge's check re-run on this push.
To try it: bun test test/openapi-operation-ids.test.ts test/openapi-drift.test.ts test/openapi-coverage.test.ts.
I made no new change for this report. It is main's full suite at 24dd0c8, which does not include this pull, so those two tests stay red there until the pull merges.
On this branch, openapi-drift, openapi-coverage and openapi-operation-ids pass (11 tests). The branch is level with origin.
The fix is the OpenAPI row for POST /api/v1/repos/{owner}/{name}/app/domains/{host}/claim, in src/contract/openapi/routes/postApiV1ReposOwnerNameAppDomainsHostClaim.ts. The regenerated routes/index.ts registers it. Its summary is 81 characters, under the 90-character limit.
To try it: bun test test/openapi-drift.test.ts test/openapi-coverage.test.ts test/openapi-operation-ids.test.ts.
Adds the missing OpenAPI row for POST .../app/domains/{host}/claim and exports it from routes/index.ts. It matches the handler in src/http/api/app.ts (admin scope, 401/404) and mirrors the sibling /check row. Summary is 81 chars, under the 90 limit. The drift, coverage and operation-ids tests cover it, and no page or terminal behaviour changes. Next: (1) the handler also answers 422 (name_held with the TXT record to publish), so consider listing 422 in refuses if the contract models it; (2) the check row has the same shape, so a test that every router.add route has a row would stop this recurring.
This adds the missing OpenAPI row for
POST /api/v1/repos/{owner}/{name}/app/domains/{host}/claim, which turns theopenapi-driftandopenapi-coveragetests green. The route is registered insrc/http/api/app.ts, but no row described it.src/contract/openapi/routes/postApiV1ReposOwnerNameAppDomainsHostClaim.ts, with the route's method, path, summary and auth. Itsroleandrefusesvalues (member, 401/404) are copied from the sibling domain routes, not checked against the handler. I also regeneratedroutes/index.tswithbun scripts/openapi-routes.ts.openapi-drift,openapi-coverageandopenapi-routespass (484 tests).gate.ts --fixandtsc --noEmitran clean, though their output was cut off in my terminal. I did not run the full suite; the forge's check does that on the push.Closes #15135