Under the hood
Useful1 Signal1
All warn-once diagnostics are now suppressed the same way through one registry.
What's wrong with this entry?
Anonymous. No account, no email.
What
A shared claim-once registry replaces the assorted booleans and sets that each warn-once site kept for itself, so repeated diagnostics are suppressed the same way everywhere.
Details
- Callers now include the MCP tree-id tripwire under the key
mcp_tree_id_tripwire, bare-primitive tool-result warnings keyed per tool, tool search, ink tree depth, frontmatter shadowing, the advisor unranked-base-model warning and the gateway retention sweep permission warning. - One dialog class dropped its own claim and reset pair in favour of a simple marker method.
Evidence
mcp_tree_id_tripwire, advisor_unranked_base_warning
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