Integrate ExportScopeSelector and ExportPeriodPicker into export screen
epic-bufdir-report-export-user-interface-task-008 — Embed the ExportScopeSelector and ExportPeriodPicker widgets into BufdirExportScreen's Configuration phase. Wire their output values to ExportScreenCubit so that scope and period changes trigger a fresh preview fetch. Disable the 'Preview' action button until both scope and period are valid selections. Use Riverpod providers to pass scope and period state down to the ExportPreviewPanel without prop drilling.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 1 - 540 tasks
Can start after Tier 0 completes
Implementation Notes
Prefer StateNotifierProvider (Riverpod) for exportScopeProvider and exportPeriodProvider rather than reading directly from the BLoC, so the preview panel remains decoupled from the cubit. The cubit still owns the canonical state; providers simply mirror the relevant slice. Guard against race conditions: if the user rapidly changes scope/period, debounce the preview-invalidation event by 300ms to avoid firing multiple resets. Keep ExportScopeSelector and ExportPeriodPicker as purely presentational widgets — they call a callback; callers write to state.
Testing Requirements
Widget tests: (1) 'Preview' button is disabled when scope is null, (2) 'Preview' button is disabled when period is null, (3) 'Preview' button enables after both are set, (4) changing scope after preview was loaded resets ExportPreviewCubit to idle state (mock the cubit), (5) Riverpod exportScopeProvider and exportPeriodProvider return correct values after selection, (6) Semantics test that selector change announcements are present. Use mockito or mocktail for cubit mocks.
The preview panel requires a round-trip to the edge function to compute aggregated counts. If this call takes 5–15 seconds for large scopes, users may assume the app has frozen and navigate away, potentially triggering duplicate preview requests or leaving the export in an undefined state.
Mitigation & Contingency
Mitigation: Show an immediate skeleton loading state on the preview panel as soon as the period and scope are confirmed, with named stage labels (e.g. 'Querying activities…', 'Computing totals…') streamed from the edge function's progress events. Set a clear user-visible timeout with a retry option. Pre-warm the edge function with a lightweight ping when the scope selector is opened.
Contingency: If preview latency consistently exceeds 10 seconds for large scopes, cache the preview payload in local BLoC state and allow the coordinator to proceed to confirmation without re-fetching if scope and period have not changed since the last preview.
The export preview panel contains dynamic content (warning badges, loading skeletons, aggregated counts) that must be announced correctly by VoiceOver and TalkBack. Incorrect semantics annotations could make the preview unreadable for blind coordinators, violating the project's WCAG 2.2 AA accessibility mandate.
Mitigation & Contingency
Mitigation: Implement semantic annotations using Flutter's Semantics widget with explicit labels for all dynamic content. Use live region announcements for loading state transitions. Schedule a dedicated accessibility review session with a screen reader user (Blindeforbundet has relevant expertise) before marking the epic complete.
Contingency: If the preview panel cannot be made fully screen-reader-accessible in time for launch, ship a simplified text-only summary mode activated by a toggle at the top of the preview panel, which renders all data as a single readable paragraph with no interactive badges.