Backend: Publish and enforce a complete OpenAPI specification

[Cedarich]

Complexity: Medium (150)

Description
test-swagger-docs.sh exists at the repo root, which implies Swagger is wired up, but there is no guarantee that every controller, DTO, and error shape is described. Frontend issue 10 depends on a trustworthy specification to generate client types, and external integrators have no reliable contract.

Acceptance Criteria

• Every controller and DTO carries the decorators needed for a complete schema, including error responses.
• The specification is emitted to a committed artifact as part of the build.
• CI fails when the committed specification is stale relative to the code.
• Authentication schemes and required headers, including the idempotency header from Issue 3, are described.
• The artifact path is documented so the webapp generation script can consume it.

_{Wave 8 · source: backend.md}

[Lanhubs]

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

I’d love to take this on! I have strong experience implementing these exact patterns and can deliver a clean, production-ready solution that hits all acceptance criteria.

My approach will focus on writing modular, well-documented code with comprehensive test coverage for both success paths and edge cases.

I'm ready to get started immediately. Could you please assign this to me?

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

[drips-wave]

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

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

[datagerl]

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

Hi maintainer can I please work on this issue

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

[Devadakene]

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

I am experienced enough to implement this issue having worked on similar issues in the past. Please assign

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

[Alimzy]

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

Hi! I'd like to work on this issue.

I'm a software engineer with hands-on experience in testing, debugging, and building reliable features across the stack. I'm confident I can take this on and deliver a solid, well-tested solution that follows the project's existing conventions.

I'll make sure to cover the core functionality as well as relevant edge cases to keep things reliable and regression-resistant.

Let me know if I can get started, and I'll provide updates as I progress.

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