Rule down transport batch and queued refresh callers

docs/rehost-queue.md

@@ -131,6 +131,10 @@ Working rule:
     the checked-in atlas ties `0x004707ff` to multiplayer transport selector-`0x13` body
     `0x004706b0`, which attempts the placed-structure apply path through
     `0x004197e0 / 0x004134d0 / 0x0040eba0 / 0x0052eb90 / 0x0040ef10`
+  - the neighboring batch builder is classified too:
+    `0x00472b40` is the multiplayer transport selector-`0x72` counted live-world apply path, and
+    its inner builders `0x00472bef / 0x00472d03` reach `0x004134d0` from counted transport
+    records rather than ordinary save-load restore
   - one surviving non-transport `0x004134d0` caller is bounded away from persisted restore too:
     `0x00422bb4` pushes one live `0x0062b2fc` record plus local args and literal flags `1/0`
     into `0x004134d0`, then returns the created row id through an out-param instead of feeding
@@ -139,6 +143,10 @@ Working rule:
     it caches the created site id in `[this+0x7c]`, re-enters `0x0040eba0` with immediate coords,
     and later calls `0x0040ef10` with a hard zero third arg, so it reads as another live
     controller path rather than the missing persisted owner seam
+  - the adjacent `0x00473c20` family is bounded away too:
+    it drains queued site ids and coordinate pairs from scratch band `0x006ce808..0x006ce988`,
+    re-enters `0x0040eba0` at `0x00473c98`, and clears each queued id slot, so it is a local
+    post-create refresh path rather than a persisted replay owner
   - the remaining owner-company question is therefore narrower than “find any replay seam”:
     identify which non-transport persisted source family feeds that tuple and which companion
     restore/finalize calls are sufficient to repopulate `[site+0x276]` for shellless acquisition