Role-Aware Notification Filter Service

The Role-Aware Notification Filter Service is a medium-complexity component with a critical dependency on the notification repository for coordinator-scope resolution (fetching the list of peer mentors assigned to a coordinator). This introduces a database query path that must be tested under realistic data volumes to avoid performance regressions. The service must be delivered and stable before the Notification BLoC can be considered complete, since the BLoC delegates all filtering to it. Risk areas include the coordinator multi-peer-mentor scope: if the assignment model changes (e.g., coordinators gain or lose mentees dynamically), this service must be updated in lockstep.

Ensure the acceptance tests explicitly cover all three role scopes — peer mentor, coordinator, and org admin — with edge cases for empty mentor lists and mixed org membership.

Role-Aware Notification Filter Service exposes two complementary paths: buildQueryFilter(userId, UserRole) constructs Supabase PostgREST query predicates applied at fetch time, and filterNotifications(List, UserRole, userId) applies equivalent in-memory logic after Realtime events arrive to maintain consistency between initial loads and live updates. The coordinator scope requires an async getCoordinatorPeerMentorIds(coordinatorId) call to resolve the coordinator-to-mentee mapping, which is fetched from the notification-repository. isOrgWideAlert(NotificationType) is a pure synchronous predicate used by the org admin path. The service must be stateless (no cached role data) to avoid stale access decisions after role changes.

Both paths must produce identical visibility outcomes — divergence between query and in-memory filtering will cause phantom notifications appearing after realtime events that the initial query would have excluded.