Add compact dispatch count summary command

This commit is contained in:
Jan Petykiewicz 2026-04-19 02:36:41 -07:00
commit a9906f8bad
2 changed files with 102 additions and 26 deletions

View file

@ -268,11 +268,18 @@ Working rule:
mutation-capable rows in those sampled maps.
- the widened compact-cluster probe now makes that same gap first-class too:
`runtime inspect-compact-event-dispatch-cluster <map-or-dir>` now reports all dispatch-strip
descriptor occurrences, their `trigger_kind`, and payload family instead of only unknown
descriptor ids. On `Texas Tea.gmp`, the widened report now shows `548 Add Building Port01`,
`8 Economic Status`, and `43 Company Variable 1` all arriving on
`real_packed_nondirect_compact_v1` rows with `trigger_kind = null`, so the next pass can work
from a checked probe rather than ad hoc `inspect-smp` scrapes.
descriptor occurrences, their `trigger_kind`, payload family, and the aggregated
`dispatch_descriptor_occurrence_counts` / `dispatch_descriptor_map_counts` summaries instead of
only unknown descriptor ids. On `Texas Tea.gmp`, the widened report now shows
`548 Add Building Port01`, `8 Economic Status`, and `43 Company Variable 1` all arriving on
`real_packed_nondirect_compact_v1` rows with `trigger_kind = null`, while the count summary
reports `Company Variable 1 = 4` occurrences and the other two once each, so the next pass can
work from a checked scalable probe rather than ad hoc `inspect-smp` scrapes.
- the scalable summary sibling is grounded too:
`runtime inspect-compact-event-dispatch-cluster-counts <map-or-dir>` reuses the same analysis
but emits only the corpus-level count fields, so the next broader map-install pass no longer
needs to wade through every occurrence payload just to compare descriptor or trigger-kind
coverage.
- 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`