diff --git a/crates/rrt-runtime/src/smp.rs b/crates/rrt-runtime/src/smp.rs
index aeed779..ed632ef 100644
--- a/crates/rrt-runtime/src/smp.rs
+++ b/crates/rrt-runtime/src/smp.rs
@@ -9529,6 +9529,12 @@ fn parse_event_runtime_collection_summary_with_tag_width(
                 "records with grouped opcodes already in the 0x00431b20 dispatch strip = {:?}",
                 mutation_candidate_record_indexes
             ));
+            if records_with_trigger_kind == 0 {
+                control_lane_notes.push(
+                    "decoded grouped rows already reach the 0x00431b20 dispatch strip in this collection even though the current inspection surface recovered no trigger/control kind bytes for those records"
+                        .to_string(),
+                );
+            }
             control_lane_notes.push(format!(
                 "0x00431b20 dispatch-strip opcodes present in decoded grouped rows = {:?}",
                 mutation_candidate_opcodes
@@ -22305,6 +22311,9 @@ mod tests {
                 "records with grouped opcodes already in the 0x00431b20 dispatch strip = [0]",
             )
         }));
+        assert!(summary.control_lane_notes.iter().any(|line| {
+            line.contains("decoded grouped rows already reach the 0x00431b20 dispatch strip")
+        }));
         assert!(summary.control_lane_notes.iter().any(|line| {
             line.contains("0x00431b20 dispatch-strip opcodes present in decoded grouped rows = [4]")
         }));
diff --git a/docs/rehost-queue.md b/docs/rehost-queue.md
index 9bad311..f6dde2c 100644
--- a/docs/rehost-queue.md
+++ b/docs/rehost-queue.md
@@ -340,6 +340,15 @@ Working rule:
     `[site+0x276]` store at `0x0040f5d4` therefore remains grounded only on explicit tuple/create
     paths, so the next non-hook pass should look for a non-transport persisted tuple family or a
     later ordinary restore owner rather than another generic replay scan.
+  - the loaded runtime-effect lane is narrower now too:
+    real map inspections already show decoded `0x00431b20` grouped-descriptor content inside the
+    ordinary non-direct bundle without any recovered trigger-kind metadata in the current surface:
+    `Texas Tea.gmp` reports `Add Building Port01`, `Alternate USA.gmp` reports
+    `Add Building FarmGrain` and `Add Building Logging Camp`, and `War Effort.gmp` reports only
+    variable bands, while all three currently summarize `trigger_kinds_present = []` and
+    `records_with_trigger_kind = 0`. That means the next non-hook pass on this branch is no longer
+    “do ordinary loaded rows reach `0x00431b20`?”; it is “where is trigger-kind represented or
+    bypassed for those already-decoded ordinary compact rows?”
   - the positive-path caller census is effectively boxed in now too:
     direct `0x0040ef10` callers are the create-side pair `0x00403ef3 / 0x00404489`, the transport
     tuple pair `0x0046f073 / 0x004707ff`, and the already-ruled-down live controller