Narrow linked-transit blocker to replay branch

docs/rehost-queue.md

@@ -51,12 +51,16 @@ Working rule:
     `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`
+  - the placed-structure replay strip is tighter now too:
+    `0x00444690 -> 0x004133b0 -> 0x0040ee10 -> 0x0040edf6 -> 0x00480710` already republishes
+    anchor-side linked-peer ids, route-entry anchors, and world-cell owner chains, and later
+    runtime path `0x004160aa -> 0x0040ee10` re-enters the same family outside bring-up
   - that makes the next linked-transit question narrower:
-    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
+    identify which exact branch inside `0x0040e360..0x0040edf6` rehydrates `[site+0x276]`,
+    `[site+0x2a4]`, and the live linked-peer rows beyond the already-grounded `0x00480710`
+    anchor-side refresh before `0x004093d0 / 0x00407bd0 / 0x004a6630`, because the candidate
+    table, route-entry-tracker owners, replay-strip framing, 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