Add Declaration Status Badge to Sidebar Navigation
epic-driver-and-confidentiality-management-ui-task-012 — Integrate the DeclarationStatusBadge into the sidebar navigation entry for the driver assignment list so coordinators can see at a glance how many drivers have pending declarations without navigating to the list. The badge count must be driven by a Riverpod provider that queries pending declaration count and updates in real time.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 2 - 518 tasks
Can start after Tier 1 completes
Implementation Notes
Implement the count provider as a StreamProvider.autoDispose that listens to DeclarationStatusService.watchPendingCount() — autoDispose ensures the subscription is cancelled when the sidebar is off-screen on platforms that unload it. Wrap the badge overlay using a Stack widget on the nav icon, not by modifying the DeclarationStatusBadge widget itself, to preserve the badge widget's single responsibility. For the '99+' cap, apply it at the provider layer (map count > 99 to a displayString '99+') rather than inside the badge widget so the badge remains a pure display component. For accessibility, use Semantics(label: 'Driver assignments, $count pending declarations', child: ...) on the nav item wrapper.
Testing Requirements
Write widget tests for: (1) badge renders with correct count when provider emits count > 0; (2) badge is absent when provider emits count == 0; (3) badge displays '99+' when count exceeds 99; (4) nav item is hidden when feature flag is disabled; (5) screen reader semantics label includes the count. Write unit tests for the Riverpod provider ensuring it maps service stream emissions to the correct count value and handles stream errors gracefully. Use ProviderContainer with overrides to inject mock service in all tests.
The declaration acknowledgement screen has the most complex accessibility requirements of any screen in this feature: scrollable long-form legal text, a conditional checkbox that is only enabled after reading, and a timestamp capture. Incorrect focus management or missing semantics annotations could fail VoiceOver navigation or cause the screen reader to announce the checkbox as available before the driver has scrolled, undermining the legal validity of the acknowledgement.
Mitigation & Contingency
Mitigation: Build the acknowledgement screen against the WCAG 2.2 AA checklist from the start, not as a post-hoc audit. Use semantics-wrapper-widget and live-region-announcer from the platform's accessibility toolkit. Include a VoiceOver test session in the acceptance criteria with a tester using the screen reader.
Contingency: If WCAG compliance cannot be fully achieved within the sprint, ship the screen with a documented list of accessibility gaps and a follow-up sprint commitment. Do not block the declaration workflow launch if the core interaction works but a non-critical semantics annotation is missing.
Drivers receive a push notification with a deep link to the declaration acknowledgement screen for a specific assignment. If the deep link handler does not correctly route to the right screen and assignment context — particularly when the app is launched cold from the notification — the driver may see a blank screen or the wrong declaration.
Mitigation & Contingency
Mitigation: Implement and test all three notification scenarios: app foregrounded, app backgrounded, and cold start. Use the platform's existing deep-link-handler infrastructure. Add integration tests that simulate notification tap events and assert correct screen and data loading.
Contingency: If cold-start deep link routing proves unreliable, implement a notification-centre fallback where the driver can find the pending declaration from the notification centre screen, ensuring the workflow can always complete even if the direct deep link fails.
If the driver-feature-flag-guard has any rendering edge case — such as a brief flash of driver UI before the flag value is loaded, or a guard that fails open on a flag service error — driver-specific UI elements could be momentarily visible to coordinators in organizations that have not opted in, causing confusion and potentially a support escalation.
Mitigation & Contingency
Mitigation: Default the guard to rendering nothing (not a loading indicator) until the flag value is definitively resolved. Treat flag service errors as flag-disabled to fail closed. Write widget tests covering the loading, disabled, and enabled states including the error case.
Contingency: If fail-closed cannot be guaranteed within the sprint, add a server-side RLS check on the driver assignment endpoints so that even if the UI guard leaks, the data layer refuses to return driver data for organizations without the flag enabled.