Integrate Declaration Send Screen with BLoC
epic-driver-and-confidentiality-management-ui-task-005 — Implement the BLoC/Cubit state management layer for the DeclarationSendScreen. States must cover loading, templateLoaded, sending, sent, resending, and error. Connect the screen to the DeclarationManagementService for send and re-send operations, populate the template preview section from the loaded declaration template, and display the DeclarationStatusBadge reflecting the current driver declaration state.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 2 - 518 tasks
Can start after Tier 1 completes
Implementation Notes
Use flutter_bloc Cubit (not full BLoC with events) since the state transitions are linear and do not require complex event streams. Define the state hierarchy using sealed classes for exhaustive pattern matching in the UI. The cubit's loadTemplate() method should call DeclarationManagementService.getDeclarationTemplate(assignmentId) and DeclarationManagementService.getDeclarationStatus(assignmentId) in parallel using Future.wait(). For the template preview, if the template is HTML, use a Flutter WebView or a simple HTML-to-widget parser — confirm with the team which format templates use before implementing.
The DeclarationStatusBadge should be a separate stateless widget accepting a DeclarationStatus enum, not coupled to the cubit. Ensure the cubit is provided via BlocProvider at the screen level (not globally) so it is disposed when the screen is popped.
Testing Requirements
Unit tests for DeclarationSendCubit using bloc_test package. Test all state transitions: initial → loading → templateLoaded, templateLoaded → sending → sent, templateLoaded → sending → error, sent → resending → sent, error → loading (retry). Mock DeclarationManagementService using Mockito or Mocktail. Widget tests for DeclarationSendScreen verifying each BLoC state produces the correct UI (loading spinner, template content visible, success message, error message).
Minimum 90% branch coverage on the cubit. Integration test verifying the full send flow against a mocked Supabase Edge Function is recommended but not required for this task.
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.