Ambient Wallpaper Recovery After History Navigation
Fixes a case where the desktop Home ambient wallpaper could remain static after browser history navigation or a BFCache restore. The main module could read a stale off state before ui-motion wrote full back without notifying the wallpaper controller; motion-mode, runtime-ready, and pageshow signals now resynchronize vi
# Ambient Wallpaper Recovery After History Navigation
The subtle desktop Home wallpapers now return to the correct state after browser back/forward navigation and BFCache restores. This fix only addresses page-lifecycle synchronization; it does not change the video content, resolution, or progressive-enhancement thresholds.
## Root cause
During a BFCache restore, the main module could first read the stale `off` state left while the page was hidden. `ui-motion` then wrote the site-wide motion state back to `full`, but the previous flow did not observe that write, so the wallpaper controller continued to treat the page as static and did not remount the current theme video.
## Resynchronizing on restore
- Wallpaper state is synchronized immediately when the motion mode changes.
- Runtime ready triggers another check of the current Home route, theme, and playback eligibility.
- `pageshow` coordinates wallpaper motion and the current video again without relying on a full reload.
## Fallback boundaries are unchanged
The fix does not loosen progressive enhancement. Mobile, low-performance, Save-Data, `prefers-reduced-motion`, and in-site reduced/off modes still make no video requests. Non-Home and hidden-page states still pause or release video, and the static wallpaper remains the permanent fallback.
