Split acquisition readiness from region gaps

docs/rehost-queue.md

@@ -133,9 +133,16 @@ Working rule:
     stat-family reader `0x2329/0x0d`, chairman byte `[profile+0x291]`, company byte `[company+0x5b]`
     plus indexed lane `[company+0x67 + 12*0x0042a0e0()]`, and the company-root argument passed into
     `0x0040d540 / 0x00455f60`
+  - use the new shellless-readiness split in the same trace:
+    runtime-backed families
+    peer-site restore subset plus bring-up reconstruction, company stat-family `0x2329/0x0d`,
+    chairman byte `[profile+0x291]`, and save-native company/chairman identity;
+    remaining owner gaps
+    `[region+0x276]`, `[region+0x2a4]`, `[region+0x310/+0x338/+0x360]`, and the stable region
+    class/type discriminator consumed through `0x0040d360`
   - make the next periodic-company slice about the smaller shellless-simulation question instead:
-    which persisted region/company linkage fields are still missing for `0x004014b0` and the
-    city-connection sibling once the peer-site runtime subset is no longer the blocker
+    which later restore or rebuild owner rehydrates the remaining region-side `0x004014b0` inputs
+    once the peer/company inputs are treated as grounded
 - 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>`,