Narrow event retagger trigger coverage

docs/rehost-queue.md

@@ -288,6 +288,15 @@ Working rule:
     already-live records carrying `[event+0x7ef] == 8`. So the remaining ordinary bundle question
     is no longer “does the service loop itself bypass the per-record trigger byte?”; it is which
     later owner, if any, materializes or retags `[event+0x7ef]` for the nondirect compact rows.
+  - the post-load retagger is narrower than that missing owner too:
+    direct disassembly of `0x00442c30` (called from `0x00443a50` at `0x00444b50`) shows a
+    hardcoded scenario-name patch table over already-live records in `0x0062be18/0x0062bae0`.
+    The checked cases mostly tweak modifier bytes `[event+0x7f9/+0x7fa]` or nested payload scalars
+    on records that already carry concrete kinds such as `7` (`Open Aus`, `The American`), `6`
+    (`Test connections`), `5` (`Win - Gold`), and `1` (`Win - Silver` / `Win - Bronze`). So the
+    remaining trigger-kind frontier is no longer “maybe the name sweep bulk-materializes null
+    kinds”; it is the smaller set of scenario-specific records where that sweep explicitly writes
+    `[event+0x7ef]` itself or a still-later owner does.
   - cross-map probing now gives a better static-analysis lead too:
     `British Isles.gmp` shows no current `0x00431b20` dispatch-strip rows, `Germany.gmp` stays on
     `Game Variable 1` plus `Company Variable 3..4`, while `Texas Tea.gmp` adds `Economic Status`