Close DEPLOY_API.md blue/green vs rolling open items

[Mimah97]

Context / Why

Close DEPLOY_API.md blue/green vs rolling open items. Doc ends with unchecked items to confirm deployment strategy and migration tooling with no recorded decision. Without this, Swyft cannot ship a production concentrated-liquidity DEX on Stellar (quotes, indexer, LP, or wallet flows will lie to users).

Current state

Relevant code/docs: docs/DEPLOY_API.md. Monorepo: NestJS apps/api (REST + WS, Prisma, BullMQ), Next.js apps/web, Soroban crates under packages/contract (and packages/contracts), packages/sdk (@swyft/sdk). Docs: README, docs/ARCHITECTURE.md, docs/ROADMAP.md, docs/RATE_LIMITING.md. The gap above is still open in the current tree.

Proposed work

1. Inspect docs/DEPLOY_API.md and confirm the failure mode with a failing test first.
2. Implement the production path (no silent mock success, no fail-open rate limits in production).
3. Add unit and at least one integration/e2e test under the matching package.
4. Update README, ARCHITECTURE, .env.example, or OpenAPI if operators or integrators are affected.
5. Never log JWT secrets, Freighter signatures, or wallet seeds.

Acceptance criteria

• Behavior is covered by automated tests that fail if the gap returns.
• Production/dev split is explicit (fail-fast vs local stubs).
• Docs (README, env, ARCHITECTURE) match the new behavior.
• CI-relevant tests are runnable via existing pnpm/cargo scripts.
• No new default secrets or fail-open auth/rate-limit paths.

Out of scope

Unrelated Vatix prediction-market work belongs in vatix-backend/vatix-contract.

[harmondconsultant-png]

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

I’ve reviewed the issue and I’m confident I can deliver a complete, maintainable solution. I value clear communication, consistent progress updates, and clean implementation. If assigned, I’ll take full ownership of the task and work to resolve it efficiently while respecting the project’s standards and timeline.

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

[mspotless]

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

i would like to work on this issue

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

[drips-wave]

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

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