Rendering Philosophy:
- Remove defensive "not accidental complexity" phrasing
- Reframe infrastructure requirements as trade-off, not hierarchy
- Fix Remix characterization (acknowledge React Router v7, deliberate SSR stance)
- Remove Astro name-drop from server islands description
- Add governance language to adapter test suite ("open to contributions")
- Change "no architectural blockers" to "primitives to build support"
- Fix "developers don't need to predict" overclaim

Deploying to Platforms:
- Move fidelity definitions before feature matrix (interpretive frame first)
- Clarify "Recommended" vs "Required" in matrix footnotes
- CDN table: "primitives to build" not "primitives needed for"
- Acknowledge table shows primitives, not finished integrations
- Rewrite framework comparisons to use trade-off language

CDN Caching:
- Restructure to lead with wins (Cache-Control, static assets, prefetches)
- Move cache variability problem after what works
- Split graceful degradation into "safely drop" vs "must preserve"
- Pair Vary limitation with _rsc workaround + pathname direction
- Fix "cache poisoning" mention with context and resolution

Revalidation:
- Remove "deliberate design choice" self-justification
- Lead graceful degradation with design principle, not failure list
- Add recovery path framing ("every failure mode has a defined recovery")

PPR Platform Guide:
- Tighten postponedState guidance ("must" not "should")

Self-Hosting:
- PPR streaming: "required" not "optimal experience"

PPR Platform Guide:
- Distinguish CDN-to-origin (HTTP POST) from adapter-based (direct
  function invocation) resume paths
- Explain minimal mode activation (NEXT_PRIVATE_MINIMAL_MODE)
- Add hybrid architecture note: edge shell + Node.js resume is valid
  for routes using runtime: 'nodejs'

Revalidation:
- Add refreshTags() failure handling guidance: catch errors, continue
  with local tag state, serve temporarily stale content
- Clarify atomic writes are not required for correctness

- CDN Cache-Control: clarify that on-demand revalidation does NOT
  propagate to CDN cache without explicit purge logic
- Minimum requirements: Node.js server (not streaming specifically),
  streaming is needed for progressive delivery but features work without
- HTML/RSC mismatch: remove incorrect claim about client-side detection,
  mismatch causes data inconsistency not auto-recovery unless
  deploymentId is configured
- Multi-instance: worst case is data inconsistency across instances,
  not full page reload

Tested 19 header combinations against a real Next.js app:
- Add next-router-prefetch to "safely drop" list (verified identical
  responses for static/ISR)
- Add rsc header to "must preserve" list with explanation of why
  stripping it breaks client-side navigation
- Clarify _rsc enforcement: server responds with 307 redirect when
  _rsc is missing or wrong, not just silent misbehavior
- Remove stale-while-revalidate conditional framing for state-tree
  (static/ISR responses are byte-identical with or without it)

- Rename "Graceful Degradation" to "Handling Headers at the CDN" to
  avoid contradiction of having "must preserve" under "degradation"
- Merge two back-to-back "Good to know" callouts into one
- Add next-router-segment-prefetch to "safely drop" list (was in Vary
  list but missing from both safely-drop and must-preserve)
- Replace "cache-busting mechanism" with "cache-key discriminator"
  (_rsc differentiates variants, not busts cache)
- Expand RSC on first use: "React Server Components (RSC)"
- Fix tense consistency in interception routes direction section
- Consolidate "What this means for CDNs" into "How it works" to
  remove redundant three-point list
- Add CDN query-param stripping warning for _rsc

Rendering Philosophy:
- Fix missing comma creating run-on sentence in Remix description
- Consistent use-cache links (both point to directive API reference)
- Expand RSC on first use in cache consistency bullet
- Align streaming requirement with deploying page (Node.js minimum,
  streaming for progressive delivery)
- Remove repeated "real" in adjacent sections

Deploying to Platforms:
- CDN table intro: "available building blocks, not finished integrations"
- Remove redundant footnote (qualifier now in intro)
- Tighten closing sentence in framework comparisons

How Revalidation Works:
- Split mismatch section into two paragraphs for scannability
- Unify terminology: "version skew" used consistently
- Fix "without shared cache" appearing under "with shared cache" heading
- Strengthen refreshTags error handling from suggestion to requirement
- Simplify getExpiration description (remove Infinity, link to API ref)

PPR Platform Guide:
- Fix double "opaque" in postponedState description
- Clarify dual mechanism (POST body preferred, requestMeta.postponed
  as equivalent in-process alternative)
- Move Storing PPR Artifacts before Edge Compute (prerequisite knowledge)
- Expand Edge Compute: hybrid vs full-edge architecture, KV storage
- Update checklist step 3 to cover both CDN and adapter paths

Edited Pages:
- ISR: merge two related caveats into one bullet
- cacheHandlers: rename "Understanding Soft Tags" to "Soft Tags"

… consistency

- Resume protocol works in both minimal and standard mode (app-page.ts template has no minimalMode gate)
- Separate within-deployment HTML/RSC cache inconsistency from cross-deployment skew (deploymentId)

…bullet

Don't imply all adapter-based deployments use minimal mode.

… guide

Edge compute section is about where platforms serve the shell, not about
Next.js runtime: 'edge' configuration. Remove runtime references.

- Fix addRequestMeta reference (internal API, not adapter-facing)
- Soften CDN concurrency claim ("ideally in parallel" not "simultaneously")
- Use "concatenates" instead of "stitches" for streaming response
- Document x-next-resume-state-length for combined Server Action + PPR resume

- Move "Storing PPR Artifacts" before implementation levels (prerequisite)
- Promote "Resume Protocol" to top-level section (applies to CDN and adapter)
- Fold Edge Compute into CDN section as a brief note
- Move adapter output details into resume protocol section (actionable context)
- Remove client-side implementation details (script tags, self.__next_f)
- Remove filler (TTFB depends on origin latency)
- Fix "stitching" terminology inconsistency

- Akamai: "KV" → "EdgeKV" (official product name)
- Fastly: "KV" → "KV Store" (official product name)
- ALB: clarify buffering is with Lambda integration, not HTTP mode

Replace named framework comparisons with architectural pattern
descriptions. The point is to explain the trade-off Next.js makes
(component-level vs route-level boundaries), not to categorize
competitors.

Describe three levels of static/dynamic boundary (build-time, route-level,
component-level) with their trade-offs, without naming specific frameworks.

…ides

The adapter API is documented and live. Replace the "we are working on"
note with links to the actual adapter docs and the new
deploying-to-platforms guide.

- ISR: shorten multi-instance bullet, link to how-revalidation-works
- streaming: add rendering-philosophy to related links