SRV-08 — Jobs & notifications infrastructure

SummaryCopy Anchor Link

BullMQ queues and scheduler, transactional outbox, notification service (inbox, FCM push, SMS, email adapters with dev simulators), templates and the event → channel matrix.

DescriptionCopy Anchor Link

Notifications, SSE, analytics aggregates, CRM automation and scheduled rules all run in the worker process, driven by events (NOT-01…NOT-04, INT-02…INT-04, cahier §8, §11). This task builds the BullMQ queues and the repeatable scheduler, the transactional outbox (OutboxEvent written in the same transaction as the change, dispatched by the worker with retries and a dead-letter state), and the notification service: in-app inbox (Notification), per-channel deliveries (NotificationDelivery), localised templates (NotificationTemplate per event × channel × locale), the event → channel → recipient matrix (NotificationRule), user preferences (NotificationPreference, marketing opt-out) and adapters for FCM push with deep links, SMS (provider closed in PRJ-03) and email, each with a dev simulator. It implements the reseller/delegate inbox endpoints. Out of scope: the SSE streams themselves (SRV-26) and template content for every event (filled by each module).

SubtasksCopy Anchor Link

DeliverablesCopy Anchor Link

• apps/server/src/platform/{queues.ts,scheduler.ts,outbox/}
• apps/server/src/modules/notifications/{service.ts,rules.ts,templates/,adapters/{fcm,sms,email}.ts,router.ts}
• Notifications matrix page /docs/srs/notifications-matrix aligned with the seeded rules

Acceptance criteriaCopy Anchor Link

• An event written in a rolled-back transaction is never dispatched; a committed event is dispatched at least once and consumers are idempotent by event id
• A failing consumer is retried with backoff and lands in DEAD after the last attempt, visible in Bull Board
• A reseller who opted out of PROMOTIONAL receives no promotional push but still receives TRANSACTIONAL ones (NOT-06)
• An order status event produces an inbox entry and a push with a deep link to the order (NOT-01, NOT-02)
• OTP SMS uses the SMS adapter; in dev the code is printed instead of sent (NOT-03)

Requirements coveredCopy Anchor Link

API surfaceCopy Anchor Link

Test measuresCopy Anchor Link

• Integration tests with real Redis and Postgres for outbox dispatch, retries and dead-lettering
• Unit tests for rule resolution and preference filtering
• Manual check: push received on an Android test device from staging

RisksCopy Anchor Link

• SMS provider approval and sender-id registration take weeks — start the request right after PRJ-03 and keep the simulator on staging until approved

KPICopy Anchor Link

• Delivered by Mon 19 Oct 2026 within 1.25 person-day(s).
• Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
• Zero open critical defects, permission gaps or data-integrity regressions at sign-off.

---

Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.