Narrow linked-transit replay branch consumers

docs/rehost-queue.md

@@ -55,11 +55,19 @@ Working rule:
     `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
+  - the subtype-`4` follow-on is tighter now too:
+    `0x0040eba0` already republishes `[site+0x2a4]` through `0x004814c0 / 0x00481480` plus
+    world-cell chain helpers `0x0042c9f0 / 0x0042c9a0`, so self-id replay is no longer the open
+    linked-transit blocker
+  - the owner-company branch is tighter now too:
+    direct inspection of `0x0040ea96..0x0040eb65` shows that it consumes `[site+0x276]` and
+    branches through owner/company helpers, but does not itself rehydrate `[site+0x276]`
   - that makes the next linked-transit question narrower:
-    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
+    identify which earlier restore or service owner feeds `[site+0x276]` and the live linked-peer
+    rows before replay continuation `0x0040e360..0x0040edf6`, beyond the already-grounded
+    `0x00480710` anchor-side refresh, before `0x004093d0 / 0x00407bd0 / 0x004a6630`, because the
+    candidate table, route-entry-tracker owners, replay-strip framing, subtype-`4` self-id replay,
+    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: