Problem
Current strict snapshots can contain project-relative workspace files together with canonical absolute sibling-workspace identities. The package reducer and benchmark viewer decide whether to reroot from only the first file. With a relative-first dump, later absolute paths remain machine-specific; reversing node order changes the result.
Public structure comments also promise only project-relative files even though the accepted runtime contract now includes canonical external absolute and bundled:/// identities.
Acceptance criteria
- make reduction independent of node order
- sanitize every mixed absolute identity without changing all-absolute legacy reduction semantics
- keep package and benchmark viewer reducers byte-for-byte aligned
- test relative-first and reversed-order mixed identity dumps
- update public structure contracts to name every valid identity form
Problem
Current strict snapshots can contain project-relative workspace files together with canonical absolute sibling-workspace identities. The package reducer and benchmark viewer decide whether to reroot from only the first file. With a relative-first dump, later absolute paths remain machine-specific; reversing node order changes the result.
Public structure comments also promise only project-relative files even though the accepted runtime contract now includes canonical external absolute and
bundled:///identities.Acceptance criteria