Refactor the profile resolution flow to explicitly cache and redirect
to the `/intro` route when marriage profile basics are incomplete.
This ensures users are correctly routed to the onboarding sequence
via the entry route cache.
Additionally, adds optional chaining to `router.prefetch` calls to
prevent runtime errors and updates test suites to reflect the
newly cached `/intro` path behavior.
Introduces an `onComplete` callback to `SliderPage` to allow parent
components to control navigation logic after the slider process.
Additionally, implements internationalization for button labels within
the slider components to support multi-language interfaces.
- Enhance touch swipe logic in SliderPage by tracking vertical movement to prevent accidental swipes during vertical scrolling
- Implement internationalization (i18n) in SliderSlideTwo using the `useI18n` hook
- Refactor SliderSlideTwo layout and styling for better responsiveness and content alignment
- Update aspect ratios and spacing for video thumbnail components
Refactor the question answer storage mechanism to support multiple pending
fields simultaneously and improve data isolation.
- Update `QuestionAnswersProvider` to process all dirty fields in a single
payload instead of just the first one found.
- Ensure all processed dirty keys are cleared from the tracking set.
- Update `TestQuestionsFlow` props to allow null `draftStorageKey`.
- Add comprehensive unit tests for `user-scoped-storage` to ensure
account isolation and correct key generation.
- Update `slider-page` mocks to include marriage config query keys.
Update `AdvisorActionsCard` to fetch real advisor data using `useMarriageAdvisorsQuery`.
The component now:
- Fetches live advisor data and handles loading states with a shimmer effect.
- Derives real avatars from the API response, falling back to provided props if no data is available.
- Dynamically calculates the extra advisor count based on the API results.
- Implements a fallback avatar for missing user profile images.
Refactor the focus synchronization logic to include pointer events and
ensure test stability when manipulating browser history.
- Add `pointerdown` event listener to `useQuestionInputFocusSync` to
improve input activation on touch/pointer devices
- Extract input activation logic into a dedicated `activateFocusedQuestionInput`
function for better readability
- Update `QuestionSheet` tests to reset window history state and use
asynchronous waiting for `pushState` calls to prevent race conditions
