Expose tri-lane save shape family candidates
This commit is contained in:
parent
2998d93615
commit
52a55c0a0e
2 changed files with 119 additions and 0 deletions
|
|
@ -95,6 +95,11 @@ Working rule:
|
|||
`runtime compare-region-fixed-row-runs p.gms q.gms` shows shared shape-family matches even
|
||||
though the best raw `rows_offset` drifts between saves, so the tri-lane-adjacent row family
|
||||
should be treated as a stable shape-family seam rather than a fixed-offset seam
|
||||
- the periodic-company trace now carries that save-native seam directly too:
|
||||
it exposes the current top tri-lane-adjacent fixed-row shape-family candidates with row-count,
|
||||
stride, rows-offset, and probable-density-lane hints, so the tri-lane frontier is now
|
||||
structured as “save shape-family candidates present, fixed offset ruled down” instead of only
|
||||
a prose note
|
||||
- the `0x5dc1/0x5dc2` serializer bundle is tighter now too:
|
||||
atlas-backed recovery bounds `0x0040c980 -> 0x0045b560` as emitting the derived payload over
|
||||
`[site+0x23e/+0x242/+0x246/+0x24e/+0x252]`, so the remaining restore-owner question should
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue