`MAZENG-FT-48` · Real-time notification inbox and preferences

Feature intent

Users need relevant project progress and completion signals without repeatedly refreshing the application.

Why it matters

Users need relevant project progress and completion signals without repeatedly refreshing the application.

Users receive reliable, user-scoped notifications and can control their notification experience.

Initial and live authenticated notifications with deterministic ordering and deduplication.
User-scoped individual and bulk dismissal.
Reconnect, multi-tab, offline recovery, failure handling, and defined do-not-disturb behavior.

Acceptance

01
Authenticated users receive initial and live notifications with deterministic ordering and deduplication.
02
Individual and bulk dismissals update only the requesting user's seen state.
03
Reconnect, multiple tabs or devices, offline recovery, and server or client failures are handled reliably.
04
Do-not-disturb scope and persistence are explicit.

None recorded.

Legacy server-sent events retain only one subscriber per user, making multi-tab behavior unsafe.
Browser-local do-not-disturb affects presentation only.
Notification history lacks a typed payload contract.

No authoritative Architecture tasks are linked.