Refine peer-site collection owner questions

docs/rehost-queue.md

@@ -23,7 +23,8 @@ Working rule:
     `0x004019e0 -> 0x00409950`
 - Make the next static/rehost slice the near-city industry acquisition owner seam under
   `0x004014b0`, not another generic infrastructure pass. The concrete questions are:
-  - which save-owned or runtime-owned collection feeds near-city unowned-industry candidates
+  - which minimum persisted peer-site fields on the already-grounded `0x006cec20` placed-structure
+    collection feed near-city unowned-industry candidates
   - which city/region/company linkage survives save/load strongly enough to drive the proximity
     scan
   - whether the acquisition branch can be rehosted as a shellless sibling beside the already
@@ -38,12 +39,16 @@ Working rule:
   - `0x0040d360` filters the region-type lane behind the region vtable `+0x80` byte `0x32`
   - `0x0040d540` scores region/company proximity with pending-bonus context
   - `0x0040cac0` samples the cached region tri-lane at `[region+0x310/+0x338/+0x360]`
-  - `0x00405920` walks same-company linked site peers above the live site/industry collection
-    seam
+  - `0x00405920` walks same-company linked site peers above the live placed-structure / peer-site
+    collection seam
+  - `0x00420030 / 0x00420280` is the boolean/selector peer-site pair over `0x006cec20`, combining
+    `0x0042b2d0`, the optional company filter through `0x0047efe0`, the station-or-transit gate
+    `0x0047fd50`, and the status branch `0x0047de00 -> 0x0040c990`
   - the winning linked company id comes from `[region+0x2a4]`
   So the next owner question is no longer “what does the acquisition branch do?” but “which
-  persisted site/industry collection and linkage helpers feed `0x004010f0/0x00405920`
-  shelllessly?”
+  persisted peer-site row fields above `0x004010f0/0x00405920/0x00420030/0x00420280` are the
+  minimum shellless set: current region key `[site+0x00]`, linked region id `[site+0x04]`,
+  route-anchor or linked-site handle `[site+0x08]`, and linked company peer id `[site+0x2a8]`?”
 - Use the higher-layer probes as the standard entry point for the current blocked frontier instead
   of generic save scans:
   `runtime inspect-periodic-company-service-trace <save.gms>`,