## Summary

Backports documentation fixes and improvements from canary to the
`next-16-2` branch.

### Included commits:
- eddbd54 docs: clarify that proxy/middleware matches static assets
by default (#92441)
- 43d1229 docs: clarify serverless runtime behavior for use cache
(#92232)
- 630d905 docs: add note on React canary version to View transitions
guide (#92315)
- 08f6f62 docs: note PPR default in cacheComponents reference
(#92378)
- 07182b5 docs: clarify cacheLife() cannot be called at module scope
(#92326)
- 7bb8e7d docs: add note on installing `server-only` in data security
guide (#92445)
- 6440b9e docs: update details about `unstable_retry()` behavior
(#91827)
- 246c5e1 docs: link updateTag from cacheTag reference (#92379)
- a99d7fd docs: native db drivers with sync queries (#92572)
- aef9105 docs: add Link transitionTypes version history (#92624)
- db1d2cc docs(cli): clarify that `--debug-build-paths` requires
route group folders in paths (#92618)
- 82f3f48 docs: fix broken bun.sh Nextjs documentation link (#92698)
- 5a15986 docs: add migration note for experimental cache flags to
cacheComponents (#92318)
- d1cf752 docs: draftMode alignment (#92794)
- ccc6d36 docs: amends to preserving-ui-state guide (#92270)
- 44e3208 docs: link Activity guide from Cache Components migration
guide (#92571)
- 2217cba docs: add guide for displaying dates without hydration
flash (#92786)
- d233d05 docs: remove broken error-handling overlay screenshot
(#93279)
- 356644b Update 05-server-and-client-components.mdx (#93374)
- ae88a95 docs: clarify rendering flow in Server/Client interleaving
example (#93381)
- b419190 docs: clarify proxy runtime history (#93467)
- e41fc92 docs: remove unreachable forms and mutations (#93509)
- 405a912 docs: broken link from usePathname compat call out (#93528)
- 58ea332 docs: escape literal triple-backticks in contribution guide
(#93584)
- d98ea7c docs: clarify cacheTag limit - it is per call (#93768)
- 7988818 docs: devIndicators with usage example (#93784)

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Joseph <icyJoseph@users.noreply.github.com>
Co-authored-by: MK <135491799+wwenrr@users.noreply.github.com>
Co-authored-by: wwenrr <wwenrr@users.noreply.github.com>
Co-authored-by: Aurora Scharff <66901228+aurorascharff@users.noreply.github.com>
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
Co-authored-by: Abhishek Mardiya <97448460+abhishekmardiya@users.noreply.github.com>
Co-authored-by: Jiwon Choi <devjiwonchoi@gmail.com>
Co-authored-by: Hamed <55133282+hamedniroomand@users.noreply.github.com>
Co-authored-by: Jimmy Lai <laijimmy0@gmail.com>
Co-authored-by: christopherkindl <53372002+christopherkindl@users.noreply.github.com>
Co-authored-by: Zana Abdi <zana.abdi@hotmail.com>
Co-authored-by: Armando A. Calderón <armandoandrecalderon@gmail.com>

…requestFailed` (#93920)

Backports:

- #93802

…TP cache (#93492)

Backports:

- #92892
- #93486

…`rewrites` (#93917)

Backports:

- #93294

…93918)

Backports:

- #93617
- #93601

---------

Co-authored-by: Swarnava Sengupta <swarnava.sengupta@vercel.com>
Co-authored-by: Or Nakash <ornakash@gmail.com>

…#93919)

Backports:

- #93792

Co-authored-by: Elisha Greenwald <ejgreenwald@gmail.com>
Co-authored-by: LiamBoz <thisamazingnow@gmail.com>
Co-authored-by: kmaclip <kmartclips@proton.me>

)

Backport of #91832

For #93790 and
#92711

Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
Co-authored-by: Tobias Koppers <sokra@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>

…#94164)

https://vercel.slack.com/archives/C0B0LKK5QD7/p1779825011578549

> I'm not having any luck reproducing this locally, and there's no
useful logs from GitHub Actions. Looking at the timestamps, it
successfully completes `pnpm install` and then hangs for 30m until it
times out.

> I'm not seeing these failures in the `canary` branch, and this only
happens with node 24. I'm just going to disable this job on the
`next-16-2` branch. The failure doesn't appear to be indicative of any
real issue on our end, it's more likely an issue with node or pnpm.

Example failure:
https://github.com/vercel/next.js/actions/runs/26503905088/job/78051437920

… adapters (#94050)

Backports [Fix "type: module" in project dir when using standalone or
adapters](#93612) to `next-16-2`.

<!-- NEXT_JS_LLM_PR -->

Backports [Propagate adapter preferred
regions](#94123) to `next-16-2`.

<!-- NEXT_JS_LLM_PR -->

… resolution (#94284)

Backports [feat(turbopack): add LocalPathOrProjectPath PostCSS config resolution (#91338)](#91338) to `next-16-2`.

<!-- NEXT_JS_LLM_PR -->