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

Correct Tier2 stock import owner strip

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 14:53:51 -07:00
commit b7cb61ca79
3 changed files with 26 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

22
docs/rehost-queue.md
View file

@ -15,15 +15,17 @@ Working rule:
now shows:
- `0x00416ce0` is the stock `gpdBuildingTypeDB` `%1*.bty` load callback and already rewrites
bare `port` / `warehouse` to `Port00` / `Warehouse00`
- `0x004197e0` iterates the stock style/source-family table at `0x005f3c6c` through
`0x00414490`, not a map-specific alternate catalog; the current recovered source names are
- `0x004196c0` is the stock import owner that walks `%1*.bty` matches, routes them through
`0x00414490`, calls the same `0x00416ce0` load callback, and only then tails into
`0x00419230`; the current recovered source names are
`StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`, `Kyoto`,
`Persian`, `SoWest`, `Tudor`, and `Victorian`
- `0x00419230` is then the later two-bank, twelve-ordinal clone-and-rename pass that stamps
`Warehouse%02d` / `Port%02d`
- so the next honest question is which source rows out of that stock style-family strip first
satisfy each later `(bank, ordinal)` pair before `0x00419230` clones them
- that means the queue should keep tracing `0x004197e0 -> 0x00414490 -> 0x00419230` and its
- that means the queue should keep tracing `0x004196c0 -> 0x00414490 -> 0x00416ce0 -> 0x00419230`
and its
callsites, not return to the older generic hidden-writer hypothesis
- Treat the periodic-company trace as the main shellless simulation frontier now that the
@ -814,13 +816,13 @@ Working rule:
stock `BuildingTypes/*.bty` discovery for the numbered families either; the remaining `01..11`
source work belongs under scenario/live candidate-table projection and row-family choice above
the already-grounded bare-name remap.
The stock source-family strip above that remap is grounded now too. `0x004197e0` formats file
names from the source-name table `0x005f3c6c` and companion path table `0x005f3c80`, feeds the
result into `0x00414490`, and only then tails into `0x00419230`. The recovered source-name
table is `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`,
`Kyoto`, `Persian`, `SoWest`, `Tudor`, and `Victorian`, so the next Tier-2 source question is
no longer “where do numbered names come from?” but “which style-family rows first survive into
the later two-bank, twelve-ordinal clone pass?”
The stock source-family strip above that remap is grounded now too. `0x004196c0` walks the
`%1*.bty` file set, routes each match through `0x00414490`, calls the stock load callback
`0x00416ce0`, and only then tails into `0x00419230`. The recovered source-name table is
`StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`, `Kyoto`,
`Persian`, `SoWest`, `Tudor`, and `Victorian`, so the next Tier-2 source question is no longer
“where do numbered names come from?” but “which style-family rows first survive into the later
two-bank, twelve-ordinal clone pass?”
The exact-match resolver beneath that style-family strip is grounded now too. `0x00419590`
copies one source-kind name from `0x005f3c6c`, combines it with one style/theme entry from the
smaller subset table `0x005f3c80` through format `"%1%2"` at `0x005c8730`, and then scans the