jan/rrt
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Expose region payload prefix dword candidates

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 19:25:36 -07:00
commit ad7576b65b
2 changed files with 148 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/rehost-queue.md
View file

@ -544,6 +544,11 @@ Working rule:
`[region+0x2a4]` or `[region+0x310/+0x338/+0x360]`, and they still do not touch
`[region+0x276/+0x302/+0x316]`. That means the remaining region restore target is now the later
owner that rebuilds those latches or the separate tagged body seam that persists them.
- The save-side region payload probe is wider now too: the checked-in `region_record_triplets`
surface no longer stops at raw pre-name prefix bytes and now also emits structured prefix dword
candidates per record. That gives the next region payload pass a direct way to compare the
opaque pre-`0x55f1` band against the remaining acquisition-side lane shapes instead of redoing
raw hex inspection by hand.
- The rest of `0x00455fc0` is ruled down further now too: after the `+0x48` callback it only runs
`0x0052ebd0`, which reads two one-byte generic flags through `0x531150` into base object bytes
`[this+0x20]`, `[this+0x8d]`, `[this+0x5c..+0x61]`, `[this+0x1ee]`, `[this+0x1fa]`, and