Problem
Pls refer to #726  for context
Phase 1 layout persistence works by always rendering all entries on the server and merging them on the client.
The planned Phase 3 skip-header optimization (X-Vinext-Router-Skip) needs to know which layout entries are safe to skip re-rendering. That requires a way to classify persisted layout entries as either:
- static: safe to reuse from client cache
- dynamic: must be re-rendered, or later handled with explicit stale-time semantics
Without this classification, skip-header work has no reliable foundation. This can be based off main I think since it's orthogonal
Problem
Pls refer to #726  for context
Phase 1 layout persistence works by always rendering all entries on the server and merging them on the client.
The planned Phase 3 skip-header optimization (
X-Vinext-Router-Skip) needs to know which layout entries are safe to skip re-rendering. That requires a way to classify persisted layout entries as either:Without this classification, skip-header work has no reliable foundation. This can be based off main I think since it's orthogonal