Correlate infrastructure prelude classes by profile span

This commit is contained in:
Jan Petykiewicz 2026-04-18 14:42:01 -07:00
commit d998c08219
3 changed files with 387 additions and 0 deletions

View file

@ -2975,6 +2975,11 @@ The low helper strip beneath that shared family is tighter now too: `0x0052ecd0`
the save-side probe be looking for above the fixed rows?”; it is the narrower partitioning
problem of how the observed `0x55f3`-to-next-`0x55f1` gaps divide between the two `0x52ebd0`
flag bytes and the next records `u16 + byte` prelude.
The widened prelude correlation narrows that again on grounded `q.gms`: the `0x03` post-profile
gap class now collapses cleanly to the next-record prelude `0x0001 / 0xff` across `17/17` rows,
while the zero-length class is a separate `0x0055 / 0x00` outlier across `18/18` rows and the
`0x06` class is the only large mixed frontier left. So the next infrastructure pass should focus
on classifying the mixed `0x06` rows instead of re-proving the pure-prelude `0x03` class.
The child loader family is explicit now too: local `.rdata` at `0x005cfd00` proves the
`Infrastructure` child vtable uses the shared tagged callback strip directly, with
`+0x40 = 0x00455fc0`, `+0x48 = 0x00455870`, and `+0x4c = 0x00455930`. So the remaining