Narrow acquisition owner-company lane to live writers

docs/rehost-queue.md

@@ -133,14 +133,19 @@ Working rule:
     `0x2329/0x0d`, candidate field `[candidate+0x22]`, and the projected-cell validation strip
     `0x00417840 -> 0x004197e0`, then commits the linked-site mutation through
     `0x0040d1f0 / 0x00480710 / 0x0045b160 / 0x0045b9b0 / 0x00418be0 / 0x0040cd70`
+  - the direct writer census now narrows the remaining owner-company question too:
+    grounded `[site+0x276]` writes cluster under create-side and live mutation families such as
+    `0x004269b0 / 0x00426a10`, the create-side `0x0040ef10 / 0x0040f6d0` strip, and the bulk
+    reassignment families `0x00426dce..0x00426ea1` and `0x00430040..0x004300d6`, not under the
+    known `0x00444690 -> 0x004133b0 -> 0x0040ee10` replay strip
   - the create-side family is grounded separately too:
     city-connection direct placement already reaches
     `0x00402cb0 -> 0x00403ed5/0x0040446b -> 0x004134d0 -> 0x0040ef10`
     as the shared constructor/finalize strip for newly created site rows
   - so the acquisition blocker is no longer “is there any real consumer family above these
-    lanes?” or “how do new placed structures finalize?”; it is specifically the restore or replay
-    owner that populates those live preconditions for already-restored rows before shellless
-    acquisition runs
+    lanes?”, “how do new placed structures finalize?”, or “is `[site+0x2a4]` still missing?”; it
+    is specifically the restore or replay owner that populates `[site+0x276]` plus the cached
+    tri-lane for already-restored rows before shellless acquisition runs
   - direct disassembly now shows the generic base constructor `0x0052edf0` clearing base state
     through `0x0052ecd0` and then writing `[this+0x04]` from caller arg `1`
   - `0x00455b70` is the concrete placed-structure specialization constructor feeding