Zack Tanner 4be2ee7443 Preserve per-segment prefetching after dynamic navigation (#96583) ...

## Summary

Cache Components routes support per-segment prefetching, but dynamic
Flight responses only advertised this capability during static
generation. This could cause a subsequent `router.prefetch()` call to
fall back to loading-boundary prefetching and issue an unnecessary
request.

In other words, this logic was correctly determined
[here](https://github.com/vercel/next.js/blob/0db9e5f994ddf144bef72640d5be9bb17d77fe30/packages/next/src/server/app-render/app-render.tsx#L2204)
but not in the initial payload.

## Verification

- `pnpm test-start-turbo
test/e2e/app-dir/segment-cache/basic/segment-cache-basic.test.ts`
- `pnpm test-start-webpack
test/e2e/app-dir/segment-cache/basic/segment-cache-basic.test.ts`

2026-08-04 02:02:32 +00:00

..

cache-life-seconds

…

cache-life-seconds-test

…

cycle

…

fully-static

…

interception

…

interception-with-params

…

lazily-generated-params

…

partially-static

Preserve per-segment prefetching after dynamic navigation (#96583)

2026-08-04 02:02:32 +00:00

same-page-nav

Preserve per-segment prefetching after dynamic navigation (#96583)

2026-08-04 02:02:32 +00:00

test

…

with-server-action

…

layout.tsx

…

page.tsx

…

streaming-text.tsx

…