testnet: contract test proving OpenAPI matches every implemented route

[Depo-dev]

Related to #421 and #232. A spec that drifts from the implementation is worse than no spec, because SDKs and users trust it.

Scope

• A test that fails when a route exists without a spec entry, or a spec entry without a route.
• Cover status codes and error envelopes, not just paths and happy-path shapes.
• Run it in CI so drift is caught at the PR, not at release.

Done when

• CI fails on any divergence between the OpenAPI spec and the implemented API.

[Tobi-8]

@Tobi-8 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

please maintainer , assign me to this issue. I have looked through your description, and i have had experience in this type of issue.
kindly assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Tobi-8 to this issue.

[sagesan2580]

@sagesan2580 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello maintainer please can I be assigned to this issue? ETA <= 48hrs

ℹ️ Repo Maintainers: To accept this application, review their application or assign @sagesan2580 to this issue.

[Miracle656]

@Miracle656 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to claim this issue. Adding strict OpenAPI contract tests is critical to eliminate specification drift, ensuring that routes, status codes, and error envelopes stay in lockstep between the implementation and the published schema.

My implementation plan:

Bi-Directional Route & Method Parity: Introspect the runtime router stack (e.g., Express/Fastify/Hono route table) and compare it against the OpenAPI specification object, asserting zero unmapped routes in either direction (no undocumented endpoints and no orphaned spec paths).

Response Schema & Status Code Validation: Validate both successful (2xx) responses and structured error envelopes (4xx, 5xx) against the defined OpenAPI JSON schemas using an automated validator (e.g., openapi-request-validator / ajv or jest-openapi / spectral).

CI Pipeline Gate: Add the contract test suite to our CI workflow to fail fast on pull requests whenever an endpoint is modified, added, or removed without an accompanying spec update.

Please assign this to me!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Miracle656 to this issue.

[drips-wave]

Congratulations, @Miracle656! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Miracle656: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊