Decode infrastructure short trailing flag lane
This commit is contained in:
parent
1011f557e5
commit
9f43a27e07
3 changed files with 312 additions and 10 deletions
|
|
@ -95,6 +95,13 @@ Working rule:
|
|||
infrastructure pass should stop asking whether the shared tagged callback sequence is present at
|
||||
all and instead decode the short `0x55f3` payload role and its relation to the compact-prefix
|
||||
regimes and primary-child restore path.
|
||||
- That short trailing lane is tighter now too: direct disassembly of `0x0052ebd0/0x0052ec50`
|
||||
shows the post-`+0x48` helper pair loading and serializing two single-byte lanes that fold into
|
||||
bits `0x20` and `0x40` of `[this+0x20]`, and the save-side probe now shows the dominant
|
||||
`0x06`-byte rows all carrying the same grounded flag pair `0x00/0x00` on `q.gms`. So the next
|
||||
concrete infrastructure question is no longer “is there a short trailing flag lane?”; it is how
|
||||
the compact-prefix regimes and those flag-byte pairs feed the child-count / primary-child restore
|
||||
state above `0x0048dcf0`.
|
||||
- Reconstruct the save-side region record body on top of the newly corrected non-direct tagged
|
||||
region seam (`0x5209/0x520a/0x520b`, stride hint `0x06`, `Marker09` record stems) now that the
|
||||
`0x55f3` payload is known to be fully consumed by the embedded profile collection on grounded
|
||||
|
|
@ -227,6 +234,11 @@ Working rule:
|
|||
and sampled row boundaries. That means the next pass can decode the short embedded `0x55f3`
|
||||
payload lane on top of already grounded row boundaries instead of rediscovering the same
|
||||
envelopes again.
|
||||
- That same probe now also exports the grounded short trailing flag-byte pair summary for the
|
||||
dominant `0x06`-byte rows, while the infrastructure trace carries the matching
|
||||
`0x0052ebd0/0x0052ec50` helper seam. That means the next pass can aim directly at how those
|
||||
flags combine with compact-prefix regimes and primary-child restore state instead of treating the
|
||||
short lane as anonymous payload.
|
||||
- That same trace now also ranks those consumers into explicit hypotheses, so the next
|
||||
infrastructure pass should start with the attach/rebuild strip instead of treating all
|
||||
candidate owners as equally likely.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue