Create API documentation generation pipeline with OpenAPI 3.1

[nanaf6203-bit]

Problem

Many DTOs lack Swagger decorators, not all endpoints are documented, no OpenAPI 3.1 upgrade.

Expected Outcome

Complete, accurate OpenAPI 3.1 specification for all endpoints.

Acceptance Criteria

• Every controller has @apitags()
• Every endpoint has @apioperation()
• Every DTO has @ApiProperty() with example
• Upgrade to OpenAPI 3.1
• Auth headers documented in Swagger

Files Affected

All controllers, all DTOs, src/config/swagger.config.ts

Difficulty

Medium

Estimated Effort

Medium (1-2 weeks)

Labels

documentation, api, enhancement

[Muhammadjazuli]

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

Hello Maintainer, I carefully investigated the issue and have identified the relevant areas for modification. I'll validate the implementation thoroughly before submission.

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

[drips-wave]

Congratulations, @Muhammadjazuli! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

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