Implement deep-link entry point for push notification
epic-annual-impact-summary-orchestration-task-013 — Wire the push notification deep-link handler to navigate directly into WrappedSummaryScreen when a summary-ready notification is tapped. The entry point must dispatch LoadSummary on screen init so the BLoC loads the correct year. Handle cold-start (app not running) and warm-start (app backgrounded) deep-link scenarios using the existing notification deep-link handler infrastructure.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 5 - 253 tasks
Can start after Tier 4 completes
Implementation Notes
Register a new named route (e.g. /wrapped/:year) in the central go_router configuration. In the notification handler (likely a top-level onMessageOpenedApp callback and getInitialMessage for cold-start), inspect data.type == 'wrapped_summary_ready' and extract data.year before pushing the route. Use go_router's extra or pathParameters to pass the year — avoid storing it in a global singleton to prevent stale-state bugs.
For cold-start, getInitialMessage must be awaited in main() or the root widget's initState before any navigation occurs. Ensure the route guard checks the Wrapped feature flag via the feature-flag-provider Riverpod provider; if disabled, use go_router's redirect to push /home instead. Use the Navigator 2.0 / go_router initialLocation to set WrappedSummaryScreen as the current route without adding home to the back stack beneath it — use go_router's replace semantics (context.go) rather than push semantics (context.push) so that back navigation lands on home.
Testing Requirements
Write widget tests mocking the WrappedSummaryBloc to assert that LoadSummary is dispatched with the correct year when the screen is constructed via deep-link route arguments. Write integration tests (integration_test package) covering cold-start deep-link navigation using a seeded FCM payload — assert correct screen is reached and correct year is loaded. Write unit tests for the deep-link payload parser covering: valid year, missing year (fallback), non-integer year (fallback), feature-flag-disabled scenario (redirect). Achieve 90% branch coverage on the deep-link handler extension.
Verify warm-start scenario manually via TestFlight on physical iOS and Android devices.
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.