Rule out dynamic side-buffer ownership of acquisition tri-lane

docs/rehost-queue.md

@@ -108,6 +108,10 @@ Working rule:
     the checked-in `0x36b1/0x36b2/0x36b3` triplet seam and the
     `0x4a9d/0x4a3a/0x4a3b` side-buffer seam still do not serialize `[site+0x310/+0x338/+0x360]`
     directly, so the known save seams are ruled down even though a later restore family is still open
+  - the dynamic side-buffer load seam is ruled down too:
+    `0x00481430 -> 0x0047d8e0` repopulates the route-entry list, three byte arrays, five
+    proximity buckets, and the trailing scratch band from stream, but still does not claim the
+    cached tri-lane
   - the third hypothesis is now a cached source/candidate bridge question, not just a raw
     `[site+0x04]` selector question:
     `0x0040cd70` seeds `[site+0x3cc/+0x3d0]` from `0x62b2fc / 0x62b268`,