Retire peer-site selector class-identity blocker

docs/rehost-queue.md

@@ -106,16 +106,18 @@ Working rule:
     `0x00420030 / 0x00420280 / 0x0047efe0 / 0x0047fd50` consume the resulting selector, with the
     current first target being the save-backed
     `0x0045c150 -> 0x0045c310 -> 0x0045c36e -> 0x00456100` family
-  - use the structured periodic-company trace candidate fields now checked into
+  - use the structured periodic-company trace selector fields now checked into
     `inspect-periodic-company-service-trace`: owner strip
     `0x0045c150 -> 0x0045c310 -> 0x0045c36e -> 0x00456100 -> 0x00455b70`, persisted tag
     `0x5dc1`, selector lane `[owner+0x23e]`, class-identity status
-    `direct_local_helper_linked_candidate`, and helper linkage
-    `0x0040ceab -> 0x0045c150` / `0x0040d1a1 -> 0x0045c310`
-  - 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
+    `grounded_direct_local_helper_strip`, and helper linkage
+    `0x0040ceab -> 0x0045c150` / `0x0040d1a1 -> 0x0045c310` /
+    `0x0040cd70 seeds [site+0x3cc/+0x3d0] from 0x62b2fc / 0x62b268`
+  - treat the peer-site selector seam itself as grounded enough for planning purposes
+  - make the next periodic-company slice about the smaller shellless-simulation question instead:
+    which subset of persisted site/peer fields (`[site+0x3cc/+0x3d0]`,
+    `0x5dc1`-backed `[owner+0x23e/+0x242]`, `[site+0x2a8]`, `[peer+0x08]`) is actually
+    sufficient to run `0x004014b0` and the city-connection sibling without shell state
 - 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>`,