Warnings that should appear once per run now share one registry instead of each tracking itself.
What's wrong with this entry?
Warnings that should only be logged once per run no longer each keep their own boolean; they take a named key from a shared registry that returns false after the first use. Behaviour is unchanged, but the keys are now namespaced and inspectable.
- Keys include voice init gating, a left-arrow rejection, a bad cron extra-tasks load, a color-diff emitter shape error, and a malformed precompute arm table.
- The same mechanism already backed the MCP tree tripwire and frontmatter shadow warnings.
cA.claim("cron_extra_tasks_load_bad"), cA.claim("precompute_arm_table_malformed")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Stall detection separates real hangs from clock jumps
Both mention diagnostic
-
v2.1.239
Warn-once budgets are now tracked per host rather than per process
Both mention diagnostic
-
v2.1.239
Message list warnings and the permission bell join the per-host registry
Both mention diagnostic