The OpenAPI document describes itself, a migration job and its stream, and opening an app #5262

The OpenAPI document now has rows for the self-address, the migration routes and opening an app. No routes changed. The new test file and the existing openapi tests pass and tsc is clean. I did not run the whole bun test suite, which the forge's check does on push.

What changed

• GET /api/v1/openapi.json: a new row, with status 308 and no auth. It redirects to /contract/openapi.json.
• POST /api/v1/migrate: the existing row now says it answers 202 and adds the crew and branch details. It lists every refusal the handler answers by error code, including invalid_source (422) and invalid_after (400).
• GET /api/v1/migrate/{job}: the existing row now lists its unauthorized and not_found refusals.
• GET /api/v1/migrate/{job}/stream: a new row. The summary says it is a text/event-stream with one migrate.<stage> event per stage, closing after done or failed.
• GET {REPO}/app/{env}/open: a new row beside the existing app/production/open row, with refusals not_found, no_such_env, no_runtime and unauthorized.
• Test: test/openapi-selfopen.test.ts boots the app and checks that all five paths and methods are in the served /contract/openapi.json. It also checks the 308, the 202 status and the stream wording. For every row except GET /api/v1/openapi.json, it calls the route and checks the refusal code it answers is one the row lists:

- invalid_source and invalid_after on migrate. - not_found on an unknown job, for both the read and the stream. - not_found for a repository with no app on the open route.

What I left out

• Production row: I kept the app/production/open row because test/openapi.test.ts requires it, since the manifest names that literal path.
• Event-stream content type: the document builder has no way to declare a response content type, so the stream's nature is in the summary only.
• Refusals without a test: only one refusal per row is tested, as the issue asks. The origin-backed and clone-failure codes on migrate are described but not exercised, because they need a fake origin.

To try it, open /contract/openapi.json and look for the five paths, or run bun test test/openapi.

Closes #5245

The OpenAPI document now has rows for the self-address, the migration routes and opening an app. No routes changed. The new test file and the existing openapi tests pass and tsc is clean. I did not run the whole bun test suite, which the forge's check does on push.

What changed

• GET /api/v1/openapi.json: a new row, with status 308 and no auth. It redirects to /contract/openapi.json.
• POST /api/v1/migrate: the existing row now says it answers 202 and adds the crew and branch details. It lists every refusal the handler answers by error code, including invalid_source (422) and invalid_after (400).
• GET /api/v1/migrate/{job}: the existing row now lists its unauthorized and not_found refusals.
• GET /api/v1/migrate/{job}/stream: a new row. The summary says it is a text/event-stream with one migrate.<stage> event per stage, closing after done or failed.
• GET {REPO}/app/{env}/open: a new row beside the existing app/production/open row, with refusals not_found, no_such_env, no_runtime and unauthorized.
• Test: test/openapi-selfopen.test.ts boots the app and checks that all five paths and methods are in the served /contract/openapi.json. It also checks the 308, the 202 status and the stream wording. For every row except GET /api/v1/openapi.json, it calls the route and checks the refusal code it answers is one the row lists:

- invalid_source and invalid_after on migrate. - not_found on an unknown job, for both the read and the stream. - not_found for a repository with no app on the open route.

What I left out

• Production row: I kept the app/production/open row because test/openapi.test.ts requires it, since the manifest names that literal path.
• Event-stream content type: the document builder has no way to declare a response content type, so the stream's nature is in the summary only.
• Refusals without a test: only one refusal per row is tested, as the issue asks. The origin-backed and clone-failure codes on migrate are described but not exercised, because they need a fake origin.

To try it, open /contract/openapi.json and look for the five paths, or run bun test test/openapi.

The full gate on land was red; the pull is open again. Red tests:

• no method and path is described twice, so no row is dead
• no method and path is described twice, so no row is dead [0.39ms] [shard 642]

The full gate on land was red; the pull is open again. Red tests:

• no method and path is described twice, so no row is dead
• no method and path is described twice, so no row is dead [0.41ms] [shard 642]

The full gate on land was red; the pull is open again. Red tests:

• no method and path is described twice, so no row is dead
• no method and path is described twice, so no row is dead [0.41ms] [shard 642]

The red gate is fixed: the "no method and path is described twice" test failed on land because GET /api/v1/openapi.json was described twice. Main now describes that route itself, so my row from this pull became a duplicate. I merged origin/main into the branch and removed my row, which leaves the one main already has. The openapi* tests pass (43) and bun x tsc --noEmit is clean. I did not run the whole bun test or design-lint.

The other four rows are unchanged. They are the migration job, its stream, opening an app, and the document's own entry.

I haven't done juniper's two follow-ups. These are a test for no_such_env and unauthorized on app/{env}/open, and letting the document builder declare a response content type so the stream row says text/event-stream in the schema. Both are best done as a separate pull.