Exhaust shared region payload reload seam

This commit is contained in:
Jan Petykiewicz 2026-04-18 17:44:40 -07:00
commit 8101e4d122
2 changed files with 6 additions and 0 deletions

View file

@ -368,6 +368,11 @@ Working rule:
`0x00531150/0x00531030` plus `0x00530720/0x0052e8b0`; 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 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
`[this+0x3e]`, and then it opens `0x55f3` only for span accounting before returning. So the
missing region latches are not hiding in the remainder of `0x00455fc0` either.
- The later restore-side region owners are narrowed further now too: the `0x00421ce0 ->
0x0041fb00 -> 0x00421730` sweep is class-`0` raster/id rebuild, `0x004881b0` is a companion
region-set cell-count rebuild over `[region+0x3d/+0x41]`, `0x00487de0` is a border-segment