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

Extend add-building candidate bridge artifact

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 02:48:05 -07:00
commit 7d9240c277
4 changed files with 105 additions and 54 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/rehost-queue.md
View file

@ -335,10 +335,11 @@ Working rule:
grouped descriptor ids `521`, `526`, `528`, `548`, and `563` are now recovered as
`Add Building FarmGrain`, `Add Building Furniture Factory`, `Add Building Logging Camp`,
`Add Building Port01`, and `Add Building Warehouse05` respectively. The checked-in
`event-effects-building-bindings.json` artifact now widens that same bridge across the whole
first `67` add-building rows (`503..569`), grounding candidate names from the stable RT3 1.05
candidate-table order plus the direct `descriptor_id - 503` candidate-id bridge in
`0x00430270` and the load-side `0x0041ede0` name-catalog copy keyed by live candidate id
`event-effects-building-bindings.json` now carries the full descriptor-side candidate bridge
across all `111` add-building rows (`503..613`) through the direct `descriptor_id - 503`
mapping in `0x00430270`, while concrete candidate names remain grounded only for the stable
RT3 1.05 live-catalog run `0..66` exposed by `0x0041ede0` and the checked candidate-table
corpus
- the earlier `label_id - 2000` bridge for `548` and `563` is now known to be a false lead:
those numeric collisions hit the special-condition label table
(`Disable Building Stations`, `Completely Disable Money-Related Things`), but the extended
@ -349,8 +350,9 @@ Working rule:
grouped opcode at all for descriptor strip `503..613`; it consumes the descriptor-derived
candidate id, placement count byte `0x11`, and the packed span words at `0x14/0x16`.
The next static-analysis pass should therefore target the remaining span-field meaning and
shell-owned placement-flow ownership on that strip, then continue the candidate bridge past the
currently grounded `503..569` front half of the widened strip, not more missing-label recovery
shell-owned placement-flow ownership on that strip, not more missing-label recovery: the
descriptor-side candidate bridge is now checked in across `503..613`, and the honest remaining
boundary is the missing non-hook name catalog for candidate ids `67..110`
- the concrete owner strip above that bundle is grounded now too:
`0x00433060` is the direct non-direct serializer loop that writes `0x4e99/0x4e9a/0x4e9b`,
calls `0x00430d70` per live collection row, and sits beside the sibling `0x00433130` size/load