Implement Certification Reminder Dispatch in BLoC
epic-admin-portal-dashboard-ui-task-013 — Add certification reminder state management to the AdminPortalBloc. Implement SendCertificationReminder event that invokes the AdminNotificationDispatcher for the specified mentor(s). Track pending/sent/failed reminder states per mentor ID in the BLoC state so the UI can show confirmation feedback without re-fetching the full certification list. Debounce repeated reminder sends.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 4 - 323 tasks
Can start after Tier 3 completes
Implementation Notes
Store reminder state as an immutable Map
Wrap each individual dispatch in try/catch so one failure does not abort others. Keep this as a pure BLoC concern — no service calls from the widget layer.
Testing Requirements
Unit test with bloc_test and a mock AdminNotificationDispatcher: (1) SendCertificationReminder sets status to pending then sent on success; (2) sets status to failed with error on service exception; (3) duplicate event within debounce window is ignored (state unchanged); (4) bulk event sets all mentorIds to pending simultaneously; (5) failed reminder for one mentor does not affect other mentors' statuses in a bulk send; (6) sent/failed status is preserved after subsequent unrelated BLoC events. Target 100% branch coverage on the reminder state machine.
If org node selection in AdminStateBLoC does not correctly propagate to all dependent data streams (statistics, activity log, user list, certification panel), some panels may show data from the previously selected org scope, creating a confusing and potentially dangerous mixed-scope view.
Mitigation & Contingency
Mitigation: Model org node selection as a single source of truth in AdminStateBLoC. All downstream providers derive their query parameters from this single stream via Riverpod's watch pattern. Write integration tests that verify every data stream emits a reload event when the selected node changes.
Contingency: If scope propagation bugs are detected in QA, add an explicit full-state reset on org node change (clear all cached data and refetch from scratch) as a safe but less efficient fallback until the targeted propagation is fixed.
The Admin Dashboard Screen must adapt its layout for Flutter Web (wider viewports, mouse interaction, larger grid) and mobile embedding. Flutter Web responsive layout support has historically required non-trivial workarounds, and the adaptive grid may introduce significant additional development time.
Mitigation & Contingency
Mitigation: Define breakpoints and grid behaviour in the design system before implementation. Use LayoutBuilder with explicit breakpoint constants rather than MediaQuery scattered across widgets. Prototype the web layout with a skeleton screen before implementing live data binding.
Contingency: If web layout proves intractable within sprint, deliver a mobile-first layout for all platforms initially and track a dedicated web-optimisation task for the next sprint.
A bug in the Role Assignment Panel's permission scope validation could allow an org_admin to assign roles beyond their authority (e.g., assigning super_admin to a user), representing a serious privilege escalation vulnerability.
Mitigation & Contingency
Mitigation: Enforce role assignment scope on both the client (disable unavailable roles in the panel UI) and the server (UserManagementService validates the target role is within the admin's permitted scope before persisting). Write security-focused tests that attempt out-of-scope role assignments and assert rejection.
Contingency: If an escalation vulnerability is discovered, immediately disable the role assignment panel via feature flag, revoke any incorrectly assigned roles, and deploy a server-side fix before re-enabling.