BE-111: OpenAPI Spec Completeness Gate

[Cedarich]

Labels: Backend, Stellar Wave, api, documentation, ci-cd
Complexity: Medium (150)

Description
The backend now exposes a large surface across roughly 45 modules, but nothing enforces that endpoints are documented with request/response schemas. Clients integrating against it have to read controllers. Add a CI gate that fails when endpoints lack schema annotations.

Acceptance Criteria

• An OpenAPI document is generated during CI from the running application metadata.
• CI fails when a route is missing a response schema, or a DTO field is missing a type.
• A documented allowlist covers intentional exclusions (for example internal-only routes).
• The generated spec is published as a CI artifact on every run.

[Windowlight]

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

I’d like to work on this issue. I’ve reviewed the requirements and understand the work involved. I’ll implement the changes, test them properly, and submit a clean PR. I’m ready to begin.

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

[drips-wave]

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

🧑‍💻 @Windowlight: 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 🌊