Published August 6: the Next.js team retraced how v0's own navigations were made instant, months before the October writeup on partial prefetching in 16.4. Between the two posts sits the full arc of the feature: measure, ship, then formalize what the measurement proved.
The loop to steal
- Tests before tooling: the team wrote the checks that could fail before instructing anyone, human or agent, to touch navigation code.
- A coding agent did the repetitive middle of the work, and every mergeable result had to survive those tests.
- What survived shipped as guidance in Next 16.3, so the pattern expired from folklore into documented behavior.
For static sites, the anchor points stay the same: measure a real navigation, not a synthetic one; only prefetch what actually navigates; and keep the plain anchor element as the default, which is this site's stance too. The gacor payoff is the same in every framework: a link that feels instant without a bundle in sight.