{"version":"2.1.232","anchor":"one-registry-now-backs-every-warn-about-this-once-case","canonical_anchor":"one-registry-now-backs-every-warn-about-this-once-case","heading":"One registry now backs every \"warn about this once\" case","tier":"internal","area":"Diagnostics","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/one-registry-now-backs-every-warn-about-this-once-case","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### One registry now backs every \"warn about this once\" case\n\nAll warn-once diagnostics are now suppressed the same way through one registry.\n\n**What**\n\nA 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.\n\n**Details**\n\n- 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.\n- One dialog class dropped its own claim and reset pair in favour of a simple marker method.\n\n**Evidence**\n\n`mcp_tree_id_tripwire`, `advisor_unranked_base_warning`\n\n- Area: Diagnostics\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}