Align `growth/alerts` Module — Event-Driven Alert Pipeline with Delivery Guarantees

[grantfox-oss]

Description
The alerts module (src/growth/alerts/) has basic CRUD for alerts and trigger logs, but lacks:

• Event-driven trigger mechanism — alerts are created via direct API calls, not by subscribing to domain events (risk breaches, portfolio thresholds, DeFi position changes).
• Delivery channel abstraction — no distinction between email, push, WebSocket, or in-app alerts.
• Delivery guarantees — no retry logic, no deduplication, no rate limiting per user.
• Integration with the risk management events from Issue Align defi Module — Protocol Adapter Registry & Strategy Discovery #9.

Direction

1. Create src/growth/alerts/listeners/ directory with event listeners:
   • RiskAlertListener — subscribes to risk.threshold.breached events.
   • PortfolioAlertListener — subscribes to portfolio rebalancing events.
2. Create src/growth/alerts/services/alert-dispatcher.service.ts:
   • Channel abstraction (EmailChannel, WebSocketChannel, InAppChannel).
   • Retry logic with exponential backoff (max 3 attempts).
   • Deduplication via alert fingerprint (hash of userId + triggerType + triggerId + timeWindow).
3. Add user preference model: AlertPreference entity storing per-user channel preferences and quiet hours.
4. Expose POST /api/v1/alerts/subscribe and DELETE /api/v1/alerts/unsubscribe endpoints for user preference management.
5. Rate limit alert delivery per user (configurable, default: 10 alerts/hour).

Definition of Done

• Alerts module reacts to domain events automatically.
• Users receive alerts through their preferred channels with delivery guarantees.

Acceptance Criteria

• RiskAlertListener creates alerts when risk.threshold.breached events are emitted
• AlertDispatcher delivers through at least 2 channels (in-app + one other)
• Duplicate alerts within a 5-minute window are deduplicated
• Failed deliveries retry up to 3 times with exponential backoff
• AlertPreference entity exists with channel and quiet-hours configuration
• Subscribe/unsubscribe endpoints exist and are documented in Swagger
• Rate limiting prevents more than 10 alerts per user per hour
• npm run build succeeds
• Alert service unit tests pass

---

[clintjeff2]

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

Pull request in 2 days.

[demilade18-git]

can this be assigned to me?

[grantfox-oss]

🦊 GrantFox — @demilade18-git has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #12)
2. Your PR will be reviewed by the SourceXXL maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@demilade18-git's PR #21 was approved and merged by @memplethee-lab.

🏆 @demilade18-git: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (188 total points). Track your full progress on GrantFox.

👏 Great work, @demilade18-git! Keep contributing to SourceXXL.