Enrich periodic company service traces

docs/rehost-queue.md

@@ -10,6 +10,24 @@ Working rule:
 
 ## Next
 
+- Treat the periodic-company trace as the main shellless simulation frontier now that the
+  infrastructure footer-bit residue is layout/presentation-owned. The checked-in
+  `runtime inspect-periodic-company-service-trace <save.gms>` report now exposes concrete branch
+  owners instead of generic blockers:
+  - `industry_acquisition_side_branch` carries
+    `0x004019e0 -> 0x004014b0` with the city-connection sibling `0x00406050`
+  - `city_connection_announcement` carries
+    `0x004019e0 -> 0x00406050` plus peer helpers
+    `0x00420030 / 0x00420280 / 0x0047efe0`
+  - `linked_transit_roster_maintenance` carries
+    `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 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
+    grounded annual-finance helper
 - 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>`,