Jake Barnby aa9b45b5a1 fix(notifications): persist alerts to platform db regardless of dispatching project ...

The `alerts` collection lives in the platform database, but the Notifications
worker was injecting `dbForProject` and writing alerts there. Webhooks
dispatches with the user's project context, so alerts were being written to
the user's project DB (which has no `alerts` collection), and `/v1/account/alerts`
(which reads from `dbForPlatform`) returned nothing.

Switch the worker to inject `dbForPlatform` instead. All alert reads (dedup
lookup) and writes (persistAlert + ConsoleAdapter) now target the platform DB,
independent of which project the dispatching event belongs to.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-06 15:25:45 +12:00

..

benchmarks

Improve scopes quality

2026-04-29 13:52:13 +02:00

e2e

test(notifications): e2e tests for list, mark-read, tracking pixel, and webhook-failure fanout

2026-05-06 15:09:28 +12:00

extensions

chore: bump PHPStan to level 4 and fix all new errors

2026-04-19 17:31:20 +05:30

resources

feat(notifications): add worker entrypoint and registration alongside Mails

2026-05-01 15:56:43 +12:00

unit

fix(notifications): persist alerts to platform db regardless of dispatching project

2026-05-06 15:25:45 +12:00