Promote candidate table row families into export

This commit is contained in:
Jan Petykiewicz 2026-04-21 17:56:53 -07:00
commit f7a2342a7c
4 changed files with 370 additions and 10 deletions

View file

@ -1246,12 +1246,14 @@
families.
The root scan narrows the real corpus for that question too. `runtime scan-candidate-table-headers
rt3_wineprefix/drive_c/rt3/maps` shows `37` probe-bearing shipped maps and `4` skips, while the
narrower `runtime scan-candidate-table-named-runs` command shows two stable `00`-row families
across those `37` probe-bearing maps: `30` maps keep `Port00` / `Warehouse00` at rows `35` /
`43`, while `7` maps move just those two `00` rows earlier to `10` / `18`; the
`Port01..11` and `Warehouse01..11` runs stay fixed at rows `45..55` and `56..66` in every
probe-bearing map. Trailer families split independently too: `28` maps keep the numbered rows
on trailer `0x00000001`, while `9` maps keep the same row layout but zero the same trailers.
narrower `runtime scan-candidate-table-named-runs` command now keeps those aggregates explicit
too: `port00_warehouse00_row_pair_map_counts` records the two stable `00`-row families across
those `37` probe-bearing maps as `35/43 -> 30 maps` and `10/18 -> 7 maps`, while
`files_with_port01_11_run_at_45_55_count = 37` and
`files_with_warehouse01_11_run_at_56_66_count = 37` keep the `Port01..11` / `Warehouse01..11`
runs fixed at rows `45..55` and `56..66` in every probe-bearing map. Trailer families split
independently too: `numbered_port_warehouse_trailer_family_map_counts` keeps the fixed numbered
rows on `0x00000001 -> 28 maps` versus `0x00000000 -> 9 maps`.
The checked-in evidence join is explicit now too:
`artifacts/exports/rt3-1.06/building-type-sources.json` still bounds the stock side to bare
`port` / `warehouse`, `artifacts/exports/rt3-1.06/event-effects-building-bindings.json` keeps