next.js

ba55bd63 - Refine Cache Components and Partial Prefetching adoption skills (#95817)

Refine Cache Components and Partial Prefetching adoption skills (#95817) Refinements to the Cache Components and Partial Prefetching adoption skills from running them cold against real apps, plus the doc changes they lean on. **Skills** - PPF: URL-data sweep reworked to feature-by-feature with a resumable hand-off, and the requires section now says unfinished Cache Components adoption doesn't gate the skill. Prerender insights are non-blocking dev signals expected on a fresh branch; only a build-blocking failure stops the run. - PPF: install `next-dev-loop` without asking, and verify a real blocker before falling back. - CC: dropped the hard-coded `agent-browser` version pin; updated the PPF cross-reference to the current enable-first flow. **Docs** - `runtime-prefetching`: the per-card server cost of `allow-runtime` grids is specific to `prefetch={true}`, with hover-triggered prefetch as the mitigation. - `use-cache`: the request-API restriction follows the call stack (`next-request-in-use-cache`, can pass build and fail under `next start`), and the nested-`cacheLife` build error with its fix. - `instant` route segment config: removed a stale `version: draft` so the page publishes. <!-- NEXT_JS_LLM_PR -->