next.js

28a9465d - docs: view transitions guide — skill section, source-audit fixes, flag-removal docs (#96097)

docs: view transitions guide — skill section, source-audit fixes, flag-removal docs (#96097) ## What Three things, reviewable per commit: 1. **Point readers at the [`react-view-transitions`](https://github.com/vercel-labs/agent-skills/tree/main/skills/react-view-transitions) skill** — same section shape as the partial-prefetching and cache-components guides. 2. **Fix inaccuracies found by a source audit** (React reconciler, Next client source, and the guide's own demo repo, which already does most of these correctly): - Warn that `default="none"` on a named pair silently kills the morph unless `share` stays explicit; ship `share="morph" default="none"` in the customization snippet - Add `default="none"` to the Suspense fallback VT; align the reveal-timing prose with its CSS (`--duration-move`) - Show the gallery-side directional wrapper (one page alone can't produce the promised slide) and note wrappers go in pages, not layouts - Correct the untyped-transition examples (back/forward, `router.refresh()`, reveals — not initial loads) and the `key={slug}` explanation - New "Keeping the page interactive" note (`::view-transition { pointer-events: none }` + named-participant hit-testing caveat); companion demo PR vercel-labs/react-view-transitions-demo#7 - State the real browser requirement (transition types / `view-transition-class`, Chromium 125+); note morphs need the destination rendered in the same commit 3. **Docs side of the `experimental.viewTransition` removal** (#96098 is the code-only counterpart): config page deleted, setup step replaced with "works with no configuration." Prose follows the internal technical-writing guidelines. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>