Bound linked-transit upstream live-table owners

docs/rehost-queue.md

@@ -46,11 +46,17 @@ Working rule:
     and world calendar lanes `[world+0x15/+0x0d]`, while the actual cache contents at
     `[site+0x5bd]`, `[site+0x5c1/+0x5c5]`, and `[site+0x0e/+0x12/+0x16]` are live rebuilt scratch
     lanes under `0x004093d0 / 0x00407bd0 / 0x00481910 / 0x004819b0 / 0x004aee2b`
+  - the upstream live-table owners are tighter now too:
+    active-company refresh owner `0x00429c10` walks the live company roster and re-enters
+    `0x004093d0`; candidate table root `0x0062ba8c` is world-load owned by
+    `0x0041f4e0 -> 0x0041ede0 -> 0x0041e970`; and route-entry tracker compatibility / chooser
+    helpers `0x004a6360 / 0x004a6630` already sit under owner-notify refresh `0x00494fb0`
   - that makes the next linked-transit question narrower:
-    identify which restore or service owner guarantees those save-backed site/peer/company identity
-    lanes have already rebuilt the live placed-structure, peer, route-entry tracker, and candidate
-    tables consumed by `0x004093d0 / 0x00407bd0 / 0x004a6630`, because the bounded train-side strip
-    `0x00409770 / 0x00409830 / 0x00409950` and the cache-cell semantics are no longer the blocker
+    identify which placed-structure restore or service continuation guarantees those save-backed
+    site/peer/company identity lanes have already rebuilt the live placed-structure and linked-peer
+    rows before `0x004093d0 / 0x00407bd0 / 0x004a6630`, because the candidate table,
+    route-entry-tracker owners, bounded train-side strip `0x00409770 / 0x00409830 / 0x00409950`,
+    and cache-cell semantics are no longer the blocker
 - 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 minimum persisted peer-site fields on the already-grounded `0x006cec20` placed-structure