Bound periodic runtime-effect caller census

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

@@ -159,6 +159,37 @@ So the current blocker is no longer “is trigger kind really a direct gate?”
 loaded rows get a nonzero `[event+0x7ef]` that matches the later `0x00432f40(kind 8)` or follow-on
 `kind 0x0a` service.
 
+## Wider Caller Census
+
+The collection-wide dispatcher above that gate is broader than the narrow queue head alone:
+
+- the recurring simulation-maintenance strip at `0x0040a220..0x0040a9ac` already drives:
+  - kind `1` at `0x0040a276`
+  - kind `0` at `0x0040a55f`
+  - kind `3` at `0x0040a6cb`
+  - kind `2` at `0x0040a7a3`
+  - kind `5` at `0x0040a930`
+  - kind `4` at `0x0040a9ac`
+- the kind-`7` family is already grounded too:
+  - `0x00407682`
+  - `0x0047d293`
+  - `0x0047d42b`
+  - `0x0047d6de`
+- the kind-`6` family is also wider than one site-local branch:
+  - placed-structure post-create tail `0x0040f69e`
+  - build-version-gated startup or roster-refresh tail `0x00428406`
+  - route-entry post-change sweep `0x004a3eae`
+- kind `9` is the `LoadScreen.win` briefing query at `0x004e520b`
+- kind `8` still sits only in the late world-entry one-shot at `0x00444d92`
+
+So the active control-lane question is narrower again:
+
+- `0x00432f40` is not a missing shellless service entrypoint
+- ordinary runtime-effect rows are already swept under many grounded trigger kinds `0..7` plus the
+  special briefing kind `9`
+- the unresolved seam is why ordinary loaded rows still do not present a matching nonzero
+  `[event+0x7ef]` when that later world-entry kind-`8` sweep runs
+
 ## Reload-Side Boundary
 
 The ordinary reload path is narrower in the same negative way now too: