Classify zero-family stock alias clusters

docs/rehost-queue.md

@@ -1285,6 +1285,15 @@ Working rule:
     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
+  - that broader stock-header check is now grounded too: the checked-in `name_0x5e` dword-family
+    summary shows `MunitionsFactory` is not outside stock assets at all. It sits in a zero-valued
+    `WeaponsFactory` alias cluster (`Electric Plant`, `Fertilizer Factory`, `Munitions Factory`,
+    `Nuclear Power Plant`, `Oil Well`, `Weapons Factory`) while the recovered nonzero family keeps
+    its own `TextileMill`, `LumberMill`, `MeatPackingPlant`, `Distillery`, and `Toolndie`
+    clusters. So the next Tier-2 source-selection question is no longer “stock vs non-stock”; it
+    is which stock alias-root cluster gets selected, and why some later clone/replay paths prefer
+    the nonzero `0x000001f4` cluster while the peer-site residue can still surface a zero-family
+    `WeaponsFactory`-side root
   - 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,