Correct Tier2 stock import owner strip

docs/control-loop-atlas/map-and-scenario-content-load.md

@@ -57,13 +57,13 @@
   `aux_candidate_collection_rebank_or_clone_records_by_availability_pass_and_refresh_owner_links`
   `0x00419230` before the later world-load side continues, with destructor
   `aux_candidate_collection_release_templates_queues_and_indexed_storage` `0x00419680`. The fixed
-  stock source-family layer above that clone pass is bounded now too: `0x004197e0` formats source
+  stock source-family layer above that clone pass is bounded now too: the same `0x004196c0`
-  names from the `0x005f3c6c` / `0x005f3c80` style tables, routes them through parser
+  import owner walks the `%1*.bty` file set, routes each match through parser `0x00414490`,
-  `0x00414490`, and only then falls into the same `0x00419230` rebank-or-clone sweep. The
+  calls the stock load callback `0x00416ce0`, and only then falls into the same `0x00419230`
-  recovered source-name table is `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`,
+  rebank-or-clone sweep. The recovered source-name table is `StationSml`, `StationMed`,
-  `Maintenance`, `ClpBrd`, `Kyoto`, `Persian`, `SoWest`, `Tudor`, and `Victorian`, so the
+  `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`, `Kyoto`, `Persian`, `SoWest`, `Tudor`,
-  remaining Tier-2 load-side question is the style-family row-selection path into that later bank
+  and `Victorian`, so the remaining Tier-2 load-side question is the style-family row-selection
-  pass rather than another hidden naming stage.
+  path into that later bank pass rather than another hidden naming stage.
   The fixed
   tail is explicit now too: `0x00444dd0` writes one direct dword from
   `[world+0x19]`, one zeroed `0x1f4`-byte slab under `0x32cf`, closes the package, derives the

docs/control-loop-atlas/runtime-roots-camera-and-support-families.md

@@ -1282,13 +1282,13 @@
   stay in `named_binding_comparison.binding_only_canonical_stems`. So the numbered Tier-2
   families no longer belong under stock `BuildingTypes/*.bty` discovery either; they belong under
   the scenario/live candidate-table projection seam above the now-grounded bare-name remap.
-  The stock source-family loader above that remap is bounded now too. `0x004197e0` builds source
+  The stock source-family loader above that remap is bounded now too. `0x004196c0` walks the
-  names from the table at `0x005f3c6c` plus companion path table `0x005f3c80`, feeds each result
+  `%1*.bty` file set, routes each match through `0x00414490`, calls the stock load callback
-  into `0x00414490`, and only then tails into `0x00419230`. The currently recovered source-name
+  `0x00416ce0`, and only then tails into `0x00419230`. The currently recovered source-name set is
-  set is `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`,
+  `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`, `Kyoto`,
-  `Kyoto`, `Persian`, `SoWest`, `Tudor`, and `Victorian`, so the remaining Tier-2 source frontier
+  `Persian`, `SoWest`, `Tudor`, and `Victorian`, so the remaining Tier-2 source frontier is the
-  is the style-family row-selection path into the later banked clone pass, not another hidden
+  style-family row-selection path into the later banked clone pass, not another hidden name
-  name generator.
+  generator.
   The exact-match helper under that family is bounded 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 live

docs/rehost-queue.md

@@ -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
+  - `0x004196c0` is the stock import owner that walks `%1*.bty` matches, routes them through
-    `0x00414490`, not a map-specific alternate catalog; the current recovered source names are
+    `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
+    The stock source-family strip above that remap is grounded now too. `0x004196c0` walks the
-    names from the source-name table `0x005f3c6c` and companion path table `0x005f3c80`, feeds the
+    `%1*.bty` file set, routes each match through `0x00414490`, calls the stock load callback
-    result into `0x00414490`, and only then tails into `0x00419230`. The recovered source-name
+    `0x00416ce0`, and only then tails into `0x00419230`. The recovered source-name table is
-    table is `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`,
+    `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`, `Kyoto`,
-    `Kyoto`, `Persian`, `SoWest`, `Tudor`, and `Victorian`, so the next Tier-2 source question is
+    `Persian`, `SoWest`, `Tudor`, and `Victorian`, so the next Tier-2 source question is no longer
-    no longer “where do numbered names come from?” but “which style-family rows first survive into
+    “where do numbered names come from?” but “which style-family rows first survive into the later
-    the later two-bank, twelve-ordinal clone pass?”
+    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