Implement Admin Portal BLoC State Management Foundation
epic-admin-portal-dashboard-ui-task-001 — Create the AdminPortalBloc using Riverpod and flutter_bloc, defining all state classes (AdminPortalState, AdminPortalEvent) for dashboard stat loading, org hierarchy scope propagation, export job progress tracking, and pagination/filter state for user and activity lists. Wire up initial state and event handlers.
Acceptance Criteria
Technical Requirements
Implementation Notes
Use flutter_bloc's Bloc
The export job status should be a separate enum (ExportJobStatus: idle, queued, processing, completed, failed) rather than a generic string. Register a custom BlocObserver in main.dart (debug builds only) that logs state transitions to console. This BLoC is the single source of truth for all admin portal state — downstream providers should derive from it rather than maintaining parallel state.
Testing Requirements
Unit tests using bloc_test package. Cover: (1) initial state is correct, (2) LoadDashboardStats emits loading then loaded, (3) LoadDashboardStats emits loading then error on repository failure, (4) SelectOrgScope updates selectedOrgScope, (5) ClearOrgScope resets to null, (6) StartExportJob transitions exportJobStatus, (7) UpdateActivityFilter updates filter without resetting page, (8) LoadNextPage increments currentPage and sets isLoadingMore, (9) ResetFilters clears all filters and resets page to 0. Use MockAdminStatsRepository and MockOrgHierarchyRepository injected via constructor. Assert exact state sequences using bloc_test's expect().
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.