Summarize stock alias roots and peer residues

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

@@ -90,6 +90,12 @@
   `ConcretePlant`, `ConstructionFirm`, `Hospital`, `Museum`, `PaperMill`, and `Steel Mill`. So
   the later numbered clone seam is now bounded above that narrower `0x000001f4` stock family
   rather than above the full style/source strip.
+  The checked-in header-name summaries sharpen that source split again: inside the nonzero family,
+  `name_0x40` / `name_0x7c` mostly stay on direct display/file roots, but `name_0x5e` clusters
+  the shared alias roots (`TextileMill x10`, `LumberMill x4`, `MeatPackingPlant x4`,
+  `Distillery x2`, `Toolndie x2`). So the next load-side source-selection pass should bias toward
+  that `0x5e` alias-root lane when testing why the later chooser seeds only part of the stock
+  family into the numbered Tier-2 bank.
   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

@@ -1331,6 +1331,14 @@
   current residue outside the recovered `0x000001f4` stock header family. So the acquisition-side
   post-secondary-byte question and the Tier-2 numbered-bank question now share one narrower
   industrial/commercial subset frontier instead of two unrelated broad families.
+  The stock header lanes within that family are narrower now too: `name_0x40` / `name_0x7c`
+  mostly stay on direct file/display roots (`Warehouse x7` plus singletons like `Brewery`,
+  `Port`, and `Toolndie`), while `name_0x5e` is the real clustered alias-root lane
+  (`TextileMill x10`, `LumberMill x4`, `MeatPackingPlant x4`, `Distillery x2`, `Toolndie x2`).
+  So the next Tier-2 chooser/source-selection pass should treat `0x5e`-style alias roots as the
+  stronger stock-family clue than the direct-name lanes, and keep the explicit non-overlap residue
+  (`MunitionsFactory/MunitionsFactory x1`) separate instead of folding it into the recovered
+  industrial/commercial subset.
   The direct `+0xba/+0xbb` writer census now rules out a broad false lead too. The obvious new
   stores at `0x004ecd42/0x004ecdaa` and `0x004ed5d5/0x004ed625` are only shell-side
   portrait/string refresh helpers over a different id-keyed collection rooted through

docs/rehost-queue.md

@@ -1273,6 +1273,18 @@ Working rule:
     is `TextileMill`, `Toolndie`, `Brewery`, and `MeatPackingPlant` while
     `MunitionsFactory` remains the clear current residue outside the recovered
     `0x000001f4` stock header family
+  - the checked-in building-source summary now says which stock header lane is actually carrying
+    the shared alias roots too: within that recovered nonzero `0x000001f4` family,
+    `name_0x40` / `name_0x7c` mostly stay on direct file/display roots (`Warehouse x7` plus
+    singletons such as `Brewery`, `Port`, and `Toolndie`), while `name_0x5e` is the real
+    clustered alias-root lane (`TextileMill x10`, `LumberMill x4`, `MeatPackingPlant x4`,
+    `Distillery x2`, `Toolndie x2`). So the next Tier-2 source-selection pass should treat
+    `0x5e`-style alias roots as the stronger stock-family clue than the direct-name lanes
+  - the trace now keeps the explicit non-overlap residue first-class too: the current list outside
+    that recovered nonzero family is just `MunitionsFactory/MunitionsFactory x1`, so the next
+    chooser-side/source-selection slice can focus on whether that residue belongs to a zero-valued
+    stock-header family or to a later live projection seam rather than treating the whole nonzero
+    post-secondary set as one undifferentiated mystery
   - keep the already-grounded `0x0047fd50` class gate separate from that byte: direct disassembly
     now says `0x0047fd50` resolves the linked peer through `[site+0x04]`, reads candidate class
     byte `[candidate+0x8c]`, and returns true only for `0/1/2` while rejecting `3/4` and above,