Probe infrastructure payload 0x55f1 triplets

This commit is contained in:
Jan Petykiewicz 2026-04-18 13:50:07 -07:00
commit ae67719ac6
3 changed files with 104 additions and 11 deletions

View file

@ -2933,6 +2933,13 @@ The low helper strip beneath that shared family is tighter now too: `0x0052ecd0`
next unknowns are no longer inside that row layout itself; they are in the payload streams those
rows point at, and how those streams align with the save-side `0x55f1` name-pair groups and
compact prefix regimes.
The shared child payload callback is tighter now too: `0x00455fc0` zeroes the route-entry and
cached bridge bands, opens `0x55f1`, parses three len-prefixed strings through `0x00531380`,
opens `0x55f2`, seeds the child through `0x00455b70`, dispatches slot `+0x48`, runs the local
follow-on `0x0052ebd0`, and then opens `0x55f3`. The widened save-side probe currently still
sees only two embedded `0x55f1` strings on grounded `q.gms`, so the remaining payload question is
whether that third parsed string is absent on ordinary saves, hidden behind different framing, or
only populated on a narrower infrastructure subset.
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