Bound scenario fixup trigger-kind retags

docs/rehost-queue.md

@@ -13,6 +13,7 @@ This file is the short active queue for the current runtime and reverse-engineer
 - Keep the periodic-company trace as the main shellless simulation frontier, with the next concrete control-lane pass focused on the ordinary loaded runtime-effect strip `0x00444d92 -> 0x00432f40(kind 8) -> 0x004323a0 -> 0x00431b20`.
   The checked `rt3_105/maps` compact-dispatch corpus is now exported directly and partially mirrored into the periodic-company trace: `41` maps scanned, `38` with dispatch-strip rows, `318` nondirect rows total, the add-building subset is only `10` grouped occurrences across `7` descriptor keys, and the strongest broader nondirect families are now bounded too at `36` grouped occurrences across `18` maps for `nondirect-ge1e-h0001-0360-0004-0100-0200-p0000-0000-0000-ffff :: [864:4]` plus `27` across `14` maps for the mixed `[-1:4]` cluster. All of those checked rows still lack recovered trigger kind. The packed-state bridge is narrower than that queue head used to allow too: `0x0042db20/0x00430d70` rebuild and serialize only the fixed text bands plus the standalone and grouped row lists, while the metadata band `+0x7ee..+0x80e` is only mirrored by deep-copy helper `0x0042e050`. The active open question is therefore which ordinary loaded rows acquire or bypass the missing trigger-kind control lane before they can reach placed-structure mutation opcodes.
   The largest direct writer table is ruled out now too: `0x004d8ea0` is the shell-side `EventConditions.win` commit helper, where controls `0x4e98..0x4ea2` write `[event+0x7ef] = 0..10` on the currently selected live event, so that seed family does not explain shellless post-load bringup.
+  The broad scenario-name fixup owner is narrower in the same direction: `0x00442c30` really does mutate live event rows after reload, but its grounded trigger-kind writes still only retag `1 -> 5` and `0 -> 2`, while the surrounding event-side branches only patch modifier bytes or nested payload dwords under already-existing kinds. No grounded branch there seeds kind `8`.
   The direct write census is tighter in the same direction: the only grounded explicit write of value `8` into `[event+0x7ef]` is `0x004d91b3` inside that same shell helper, while the runtime-side grounded writers still only cover zero-init, copy, `2/3` follow-on seeds, and the later `5` / `2` retags.
   Preserved checked control-lane detail now lives in [Periodic company control lane](rehost-queue/periodic-company-control-lane-2026-04-21.md).
 - Keep the next static Tier-2 building pass focused on the earlier seed/projection seam into `0x00412d70`, not another broad `BuildingTypes` sweep.

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

@@ -116,6 +116,27 @@ So the next non-hook question stays above those already-known title or scenario-
 - which late bringup branch between ordinary reload `0x00433130` and final kind-`8` service
   `0x00432f40` materializes the live mutation-capable ordinary rows
 
+## Scenario-Name Fixup Bound
+
+The broad scenario-name post-load fixer is narrower now too:
+
+- `0x00442c30`
+  - definitely mutates live event rows in collection `0x0062be18` before the late kind-`8`
+    service
+  - but the grounded event-side trigger-kind writes there are still only:
+    - `0x00443526`: event row `1`, `1 -> 5`
+    - `0x00443601`: event row `0x0d`, `0 -> 2`
+  - the other surfaced event-side branches around `0x004436ca`, `0x004438e8`,
+    `0x00443948`, and `0x004439a8` only patch modifier bytes or payload fields under already
+    existing trigger kinds `6`, `5`, `1`, `1`, `2`, `3`, or `9`
+- no grounded branch inside `0x00442c30` seeds `[event+0x7ef] = 8`
+
+So the active shellless control-lane question is narrower again:
+
+- `0x00442c30` is a real event-side post-load mutator
+- but it still does not explain how ordinary loaded rows acquire the later world-entry kind `8`
+  gate
+
 ## Direct Trigger-Kind Gate
 
 Fresh `objdump` over the control-lane strip now keeps the missing trigger-kind boundary concrete: