Rule out shell trigger-kind selector path

docs/rehost-queue/periodic-company-control-lane-2026-04-21.md

@@ -178,3 +178,25 @@ So the remaining control-lane question is narrower again:
 - the late service strip gates strictly on `[event+0x7ef]`
 - and the currently grounded nonzero seed outside the scenario-name retags is the follow-on
   builder reached from the service/dispatch family rather than from the reload loop itself
+
+## Ruled-Out Shell Seed Table
+
+The largest remaining direct writer family is no longer ambiguous either:
+
+- `0x004d8ea0`
+  - is the shell-side `EventConditions.win` commit helper already grounded in `function-map.csv`
+  - resolves the currently selected live event from the editor window singleton, not from post-load
+    bringup
+  - writes `[event+0x7ef] = 0..10` from the fixed control family `0x4e98..0x4ea2`
+  - also commits neighboring editor-strip fields such as `[event+0x7f9]`, `[event+0x7fa]`,
+    `[event+0x7f5]`, and `[event+0x7f0]`
+- `0x004db120`
+  - is the paired shell refresh helper
+  - republishes that same `0x4e98..0x4ea2` family one-to-one from stored `[event+0x7ef]`
+
+So the active shellless queue head narrows again:
+
+- the broad `0..10` trigger-kind selector table is real
+- but it belongs to the shell editor strip rather than ordinary post-load simulation bringup
+- the remaining runtime question stays above ordinary reload `0x00433130` and below final service
+  `0x00432f40(kind 8)`, not inside the explicit shell editor commit path