Add automatic rollback trigger on post-switch error-rate threshold in deploy.ts

[mikewheeleer]

Description

After switch-green, regressions are only caught manually via deploy:status. Add an automatic rollback that watches error-rate/health metrics for a soak window after the switch and invokes rollback if a threshold is breached.

Requirements and context

• Read error-rate from the metrics registry over a configurable soak window; if breached, invoke deploy.ts rollback automatically.
• Make thresholds and window env-configurable and validated; emit structured deploy-decision logs.
• Ensure the rollback path is idempotent and reflected by deploy:status.
• Acceptance: deploy.test.ts simulates healthy soak (no rollback) and breached soak (auto rollback).

Suggested execution

• Fork the repo and create a branch:
  • git checkout -b feature/deploy-auto-rollback
• Implement changes:
  • src/deploy.ts
  • Tests: src/deploy.test.ts
  • Docs: docs/backend
  • Include TSDoc/NatSpec-style doc comments
  • Validate security assumptions (input validation, auth, signature verification, secret redaction, idempotency)

Test and commit

• Run tests: npm test (coverage: npm run test:ci)
• Cover edge cases
• Include test output and security notes in the PR

Example commit message

feat(deploy): auto-rollback on post-switch error-rate breach

Guidelines

• Minimum 95% line coverage on new/changed code
• No secrets in repo; use .env + deployment secrets only
• Clear documentation
• Timeframe: 96 hours from assignment

[Jayking40]

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

I'd like to work on this issue. I have strong experience with typescript, express, redis, jest and can deliver a clean, well-tested implementation.

My approach:

1. Analyze the existing codebase and understand the current architecture
2. Implement the solution following project conventions and patterns
3. Write comprehensive tests and ensure all existing tests pass
4. Submit a clean PR with clear documentation

ETA: within 24 hours

I'm available to start immediately and can provide regular progress updates.

GitHub: @Jayking40

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

[drips-wave]

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

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