Implement Claim Status Badge Widget
epic-expense-approval-workflow-coordinator-ui-task-007 — Build the ClaimStatusBadge Flutter widget that visually represents claim status (pending, approved, rejected, auto_approved, under_review) using the design token color system. Use accessible contrast-safe colors, include semantic labels for screen readers, and support both compact (list) and expanded (detail) display modes.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 2 - 518 tasks
Can start after Tier 1 completes
Implementation Notes
Define a ClaimStatus enum in a shared domain layer (not inside the widget file) so other widgets can import it without pulling in UI code. Map each enum value to a color token pair (background + foreground) in a static const map — this makes adding new statuses a one-line change. Use a Container + Text wrapped in Semantics; avoid RichText for the compact mode to keep the semantic tree simple. For expanded mode, consider a Row with an Icon and two Text widgets.
Use ExcludeSemantics on decorative icons so the screen reader only reads the label once. Register the widget in a WidgetBook or Storyboard-equivalent entry for designer QA. Do not use AnimatedContainer unless animation is explicitly requested — keep it simple.
Testing Requirements
Unit tests: verify correct color token and label string returned for each of the 5 status values. Widget tests: render both compact and expanded modes for each status and assert text content, background color, and Semantics label. Golden tests: snapshot each status × mode combination to prevent visual regressions. Accessibility test: verify contrast ratio programmatically using flutter_test's SemanticsController.
Text scaling test: render at scale 1.0, 1.5, 2.0 and assert no RenderFlex overflow. Target 100% line coverage for the widget file.
Maintaining multi-select state across paginated list pages is architecturally complex in Flutter with Riverpod/BLoC. If the selection state is stored in the widget tree rather than the state layer, page transitions and list redraws can silently clear selections, causing coordinators to lose their multi-select and re-enter it.
Mitigation & Contingency
Mitigation: Store the selected claim ID set in a dedicated Riverpod StateNotifier outside the paginated list widget tree. The paginated list reads selection state from this provider and does not own it. Selection persists independently of list scroll position or page loads.
Contingency: If cross-page selection proves prohibitively complex, limit bulk selection to the currently visible page (add a clear warning in the UI) and prioritise single-page bulk approval for the initial release.
If a coordinator has the queue open while another coordinator approves claims from the same queue (possible in large organisations with shared chapter coverage), the Realtime update may arrive out of order or be missed during a reconnect, leaving the first coordinator's view stale and allowing them to attempt to approve an already-actioned claim.
Mitigation & Contingency
Mitigation: The ApprovalWorkflowService's optimistic locking (from the foundation epic) will catch the concurrent edit at the database level. The CoordinatorReviewQueueScreen should handle the resulting ConcurrencyException by removing the claim from the local list and showing a brief snackbar: 'This claim was already actioned by another coordinator.'
Contingency: Add a queue staleness indicator (a subtle 'last updated X seconds ago' label) and a manual refresh button as a fallback for coordinators who notice inconsistencies.
The end-to-end test requirement that a peer mentor receives a push notification within 30 seconds of coordinator approval depends on FCM delivery latency, which is outside the application's control and can vary significantly in CI/CD environments.
Mitigation & Contingency
Mitigation: Structure end-to-end tests to verify notification intent (correct FCM payload dispatched, correct Realtime event emitted) rather than actual device delivery timing. Use test doubles for FCM delivery in automated tests and reserve real-device delivery tests for manual pre-release validation.
Contingency: If notification timing requirements must be validated in automation, instrument the ApprovalNotificationService with a test hook that records dispatch timestamps and assert against those rather than actual FCM callbacks.