Implement WrappedSummaryScreen full-screen scaffold
epic-annual-impact-summary-orchestration-task-008 — Build the full-screen WrappedSummaryScreen scaffold with a Hero transition entry animation. The screen must occupy the full display with no bottom navigation, render a dark branded background, host the PageView for slide-by-slide navigation, and expose a close button that pops the Hero transition on exit. Wire BlocProvider to supply WrappedSummaryBloc.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 4 - 323 tasks
Can start after Tier 3 completes
Implementation Notes
Use Scaffold with extendBodyBehindAppBar: true and set appBar: null to achieve full-bleed dark background. Apply SystemChrome.setSystemUIOverlayStyle(SystemUiOverlayStyle.light) in initState and restore the app default in dispose. The Hero tag should follow the pattern 'wrapped-summary-{userId}' — the calling screen must use the same tag on its entry widget. BlocProvider.create() is preferred over BlocProvider.value() here because this screen owns the BLoC lifecycle.
Dispatch LoadSummary inside BlocProvider.create's create callback: create: (context) => WrappedSummaryBloc(...)..add(LoadSummary()). Keep this widget thin — delegate all slide rendering and progress UI to child widgets (implemented in task-009). Ensure go_router or Navigator 2.0 route is registered so back-stack behaviour is predictable on both iOS and Android.
Testing Requirements
Widget tests using flutter_test. Test: (1) scaffold renders without overflow on 375px and 414px screen widths, (2) close button tap calls Navigator.pop (use NavigatorObserver mock), (3) BlocProvider is found in the widget tree via context lookup, (4) dark background color matches the design token value. Accessibility test: run SemanticsChecker to confirm close button has a valid semantic label. No integration tests required for this scaffold task.
If the device transitions between online and offline states while the user is mid-session in the wrapped screen, the BLoC may emit conflicting state transitions (loaded → error → offline) that cause visual flickering or an inconsistent UI state such as showing the offline banner over an already-loaded summary.
Mitigation & Contingency
Mitigation: Implement a connectivity stream listener in the BLoC that only triggers a state re-evaluation when transitioning from online to offline, not on every connectivity event. Once a summary is in the Loaded state, the BLoC should not transition to error/offline unless the user explicitly requests a refresh. Store the last-loaded data in BLoC state so it survives connectivity changes.
Contingency: If state flickering is observed in testing, add a minimum 3-second debounce on connectivity state changes before the BLoC reacts, and display a non-blocking top banner rather than replacing the entire screen state.
The push notification deep-link to the wrapped-summary-screen must work correctly whether the app is in the foreground, background, or terminated state. Handling all three app launch states on both iOS and Android is a common source of edge-case bugs, particularly when authentication state must be restored before the deep link can be resolved.
Mitigation & Contingency
Mitigation: Implement deep-link handling through the existing notification-deep-link-handler component which already manages app-state-aware routing. Define the wrapped-summary route in the navigation config early in the epic so the router is ready before notification dispatch is wired. Test all three app states (foreground, background, terminated) explicitly in the QA checklist.
Contingency: If terminated-state deep-linking fails on specific platforms, fall back to launching the app to the home screen with an in-app notification banner prompting the user to open their summary, rather than direct deep-link navigation.
The wrapped-summary-screen manages a large number of AnimationController instances (one or more per slide) via the wrapped-animation-controller. If disposal is not triggered correctly when the user exits mid-flow (e.g., via system back gesture or deep-link away), memory leaks will accumulate across session navigation.
Mitigation & Contingency
Mitigation: Implement screen disposal via Flutter's dispose() lifecycle method calling a single wrapped-animation-controller.disposeAll() method that iterates the named controller registry. Write a test that navigates to the screen, starts animations, then navigates away and verifies no active AnimationController listeners remain using Flutter's test binding.
Contingency: If disposal bugs are detected in production via memory profiling, patch by converting all AnimationControllers to use AutomaticKeepAliveClientMixin false and wrap each slide in a widget that disposes its own controller when removed from the widget tree.