docs: add Routing-Animations.md overview page (decision matrix + 4 approaches) Single overview article instead of four peer pages. Rationale: - The 4-approaches comparison table is the central artefact — splitting it across 4 pages dilutes the decision matrix. - Implementation truth lives in 24 example READMEs (4 approaches × 6 adapters); the wiki page should route the choice and link out, not duplicate them. - View-Transitions.md already exists as a peer (it documents a first-class DOM utility shipped with each adapter). The other three approaches are recipes in example code, not library APIs — uneven peer pages would misrepresent the categorisation. Page structure: 1. Why router coordination — `useRouteExit`'s Promise-blocking semantics 2. Four-approaches comparison table 3. Per-approach (~30-50 LOC each) — view-transitions, route-animations, page-animations, motion-animations 4. "How to choose" decision flow + recommended defaults 5. Per-adapter notes — which library each adapter uses for the "library-driven" recipe (motion / solid-motionone / Vue's Transition / Svelte transitions / Angular signals) 6. Common edge cases — skip-initial, same-route, abort, reduced-motion, direction-aware UI 7. See Also Cross-references added so the page is discoverable from the related ones: - View-Transitions.md, useRouteExit.md, useRouteEnter.md → link back to Routing-Animations - _Sidebar.md → new "Patterns" subsection under "DOM Utilities"

greydragon888 committed Apr 27, 2026