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

Ground blocked owner strips with direct disassembly

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 13:04:00 -07:00
commit fa19d1b89a
4 changed files with 38 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/rehost-queue.md
View file

@ -40,6 +40,12 @@ Working rule:
first owner-visible bridge from the side-buffer seam into route-entry rebuild; and which child
fields or grouped rows absorb the side-buffer payload before `0x00448a70/0x00493660/0x0048b660`
become relevant.
- Targeted disassembly now tightens that strip further: `0x0048a1e0` clones the first child through
`0x0052e880/0x0052e720`, destroys the prior child, seeds a literal `Infrastructure` child
through `0x00455b70` with payload seed `0x005c87a8`, and republishes the two sampled bands
through `0x0052e8b0/0x00530720` after attaching through `0x005395d0`; the non-clone branch
attaches through `0x0053a5d0`. So the next unknown is no longer whether this strip owns the
child/rebuild seam, but which `0x38a5` compact-prefix groups drive the clone-vs-payload choice.
- 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
@ -69,6 +75,14 @@ Working rule:
how far the grounded city-connection peer/linkage helpers
(`0x00420030/0x00420280`, `0x0047efe0`) can be reused directly before the transient queued-notice
family matters again.
- Targeted disassembly now tightens that strip too: `0x004358d0` calls `0x00420030` twice plus
`0x00420280`, then resolves the linked company through `0x0047efe0`, posts company stat slot `4`
on success, and stamps `[region+0x302]` or `[region+0x316]` while clearing `[region+0x276]`.
`0x00420030` itself now reads as the real peer gate over collection `0x006cec20`, combining
`0x0042b2d0`, the optional company filter through `0x0047efe0`, the station-or-transit gate
`0x0047fd50`, and the status branch `0x0047de00 -> 0x0040c990`; `0x00420280` is the same scan
returning the first matching site id. So the remaining unknown is the persisted latch/id seam,
not the live peer/service logic.
- Reconstruct the save-side placed-structure collection body on top of the newly grounded
`0x36b1/0x36b2/0x36b3` header seam so the blocked city-connection / linked-transit branch can
stop depending on atlas-only placed-structure and local-runtime refresh notes, especially the