feat(api): restack machine-readable OpenAPI contract on latest main

[seonghobae]

Purpose

Publish Noema's machine-readable OpenAPI 3.1 contract on the current protected lineage without promoting historical checks or stale base evidence.

Test-first proof

Exact RED head 676d1b217caeb5fb48579aea93205de625032c0e added only test/openapi-contract.test.ts. Application ci run 31590811349, verify job 94095081585, checked out that exact head and failed in release verify. All five contract tests failed at the intended boundary with ENOENT for the absent openapi.json; exact checkout, package-manager verification, and install had already succeeded.

The regression pins the public /health, /ready, and /exchange surface; OpenAPI 3.1.0 / API 0.1.0; GitHub Actions OIDC bearer authentication; 8,192-byte exchange body bound; common no-store/trace/latency headers; readiness GET/HEAD semantics; 400/401/403/405/413/429/500/502/503 exchange responses; distributed rate-limit/replay headers only where the runtime contract guarantees them; and absence of embedded GitHub installation-token/private-key material.

Current implementation

Implementation head 59d05b56e6483677178749b8b2693790d91791da adds only openapi.json. The exact current regression blob is byte-identical to the previously reviewed contract test (5cb1887db418e4952cc2caeab4e804d4e049d054), while current protected docs/api-stability-contract.md still defines the same 400/401/403/429/500/502 taxonomy, common non-cacheable diagnostic headers, Bearer challenge, POST-only exchange behavior, and secret non-retention. The selected OpenAPI blob is 0c826068fc3e43ef5a3733c29c922cea6a85b0c8; no historical CI/review/scanner result transfers with that blob.

After #223 advanced protected main, current non-forced two-parent refresh 86147e5454b7deac2df76e46dfcbc45bb47986f2 preserves protected main f1b5a5626b4779b7a554aee76ba600e19ad53cc7 plus exactly the two PR blobs:

• openapi.json 0c826068fc3e43ef5a3733c29c922cea6a85b0c8;
• test/openapi-contract.test.ts 5cb1887db418e4952cc2caeab4e804d4e049d054.

Exact current-head state

For exact head 86147e5454b7deac2df76e46dfcbc45bb47986f2:

• application ci 31593285460: queued/non-passing;
• reviewer-ci 31593285437: queued/non-passing;
• protected-base eligible central Security Scan 31593285447: queued/non-passing;
• formal reviews: 0 at the latest fresh read;
• inline review threads: 0 at the latest fresh read.

Keep Draft until all applicable exact-head gates are terminal-success and current findings/reviews are re-read. No queued, predecessor, status-only, model-only, release, deployment, production, legal-rights, revenue, or acquisition evidence is promoted.

Authority boundary

This PR publishes a versioned API contract only. It does not fabricate deployment servers, modify runtime behavior, choose an outbound license, publish a release, deploy production, establish KPI/revenue/transfer evidence, or make Noema acquisition-ready.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 10 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f596d401-8fc6-4a41-95a4-d6c4a7af23f6

📥 Commits

Reviewing files that changed from the base of the PR and between f1b5a56 and 86147e5.

📒 Files selected for processing (2)

• openapi.json
• test/openapi-contract.test.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}