Regenerate openapi.json to include /api/v2/streams and current error/auth schemas

[greatest0fallt1me]

Description

openapi.json predates the v2 contract; the README documents /api/v2/streams/* as current with breaking field changes (allowed_actions, created_at, settlement), but the spec does not fully reflect v2, the wallet-auth flow, or the unified error envelope. Bring the OpenAPI 3.1 document in sync with the real route handlers. This is a backend documentation task.

Requirements and Context

• Document /api/v2/streams (GET/POST) using the toV2Stream shape from app/lib/api-version.ts, including settlement: null semantics.
• Document the wallet challenge/verify flow (GET/POST /api/auth/wallet) and the bearer-token security scheme.
• Document the shared error envelope and Deprecation/Sunset headers on v1 paths.
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b task/openapi-v2-sync

2. Implement changes
   • openapi.json
   • Add a CI/spec-lint or schema test that validates examples against route responses
3. Test and commit
   • npm test -- app/lib/api-version.test.ts
   • Cover edge cases: v1 vs v2 field diffs, error envelope schema, auth scheme
   • Include test output and notes in the PR

Example commit message

task: sync OpenAPI 3.1 spec with v2 and auth routes

Acceptance Criteria

• /api/v2/streams documented with v2 field shape and examples
• Wallet auth flow and bearer scheme documented
• Error envelope and Sunset headers documented
• Spec examples validated against actual responses in a test

Guidelines

• Minimum 90% coverage for any spec-validation code added
• Clear documentation and inline comments
• Timeframe: 96 hours

[oche2920]

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

Can i work on this issue?

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

[drips-wave]

Congratulations, @oche2920! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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