fix(library): restore breadcrumb 'All' navigation broken by next-view-transitions

[chrox]

Summary

• Closes On Windows in Readest 0.10.4 going back from a stack into the main dashboard does not work #3782 — clicking the breadcrumb "All" button after entering a group did nothing on production builds; users had to refresh to leave the group view.
• Root cause: next-view-transitions@0.3.5 wraps router.replace() in startTransition + document.startViewTransition, and that combination is incompatible with Next.js 16.2 RSC navigation when only the search params change for the same pathname (e.g. /library?group=foo -> /library). The navigation silently never commits. Same upstream issue is tracked in Next.js 16.2 - Monkey-patch warning shuding/next-view-transitions#65.
• Fix: extract the library navigation logic into a new useLibraryNavigation hook that uses the plain useRouter from next/navigation (matching the pre-feat: add directional view transitions with scroll preservation in library view, closes #3357 #3362 behavior). The data-nav-direction attribute is still set so the existing directional CSS keeps working when view transitions fire via popstate.

Test plan

• pnpm test — 3141 passed (7 unit tests added for useLibraryNavigation covering forward, back-to-root, sibling-swap, multi-param preservation, direction attribute, and onBeforeNavigate ordering)
• pnpm lint — clean (tsgo --noEmit && biome check .)
• Bug reproduced on production build with the unmodified code: clicked "Literature" group → URL became /library?group=f1506b6 → clicked "All" → URL stayed at /library?group=f1506b6 for 5+ seconds (user perceives "nothing happens").
• Fix verified on production build with the same steps: clicked "All" → URL navigated to /library within ~1s, bookshelf re-rendered with all groups.
• Verified fresh page reload + first click works (the user-reported failure mode).
• Verified multiple round-trips (group → All → group → All) all work.
• Sanity check on Tauri desktop builds (Windows/macOS) — not blocking, the fix lives entirely in the Next.js layer and the unit tests cover the navigation contract.

Closes #3782.

🤖 Generated with Claude Code