Link peer-site selector strip to local helpers

docs/rehost-queue.md

@@ -82,6 +82,8 @@ Working rule:
     it zeroes those fields, runs the shared tagged loader `0x00455fc0`, reads tagged payload
     `0x5dc1`, and copies the two recovered lanes into `[owner+0x23e/+0x242]` before
     `0x0045c310 -> 0x0045c36e` later feeds `[owner+0x23e]` into `0x00456100`
+  - the local linked-site helper neighborhood now reaches that same owner strip directly:
+    `0x0040ceab` calls `0x0045c150`, and `0x0040d1a1` jumps straight into `0x0045c310`
   - `0x00485819` is one typed placed-structure caller of `0x0052edf0` through the generic
     three-arg wrapper `0x00530640`
   - `0x00490a79` is one chooser-side caller of `0x00455b70`, feeding literal selector
@@ -104,8 +106,10 @@ Working rule:
     `0x00420030 / 0x00420280 / 0x0047efe0 / 0x0047fd50` consume the resulting selector, with the
     current first target being the save-backed
     `0x0045c150 -> 0x0045c310 -> 0x0045c36e -> 0x00456100` family
-  - confirm that this save-backed owner family is the same class-0 site family consumed by
-    `0x00420030 / 0x00420280 / 0x0047efe0 / 0x0047fd50`
+  - decide whether the direct `0x0040ceab / 0x0040d1a1` linkage is enough to treat that
+    save-backed owner family as the same class-0 site family consumed by
+    `0x00420030 / 0x00420280 / 0x0047efe0 / 0x0047fd50`, or whether one more helper-field bridge
+    is still needed
 - Use the higher-layer probes as the standard entry point for the current blocked frontier instead
   of generic save scans:
   `runtime inspect-periodic-company-service-trace <save.gms>`,