{"version":"2.1.232","anchor":"one-shot-telemetry-latches-share-a-claim-registry","canonical_anchor":"one-shot-telemetry-latches-share-a-claim-registry","heading":"One-shot telemetry latches share a claim registry","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/one-shot-telemetry-latches-share-a-claim-registry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### One-shot telemetry latches share a claim registry\n\nOnce-per-process telemetry latches share one registry; event names are unchanged.\n\n**What**\n\nModule-level booleans that kept certain events to once per process were replaced by a shared registry. Event names, including the first-scan and MCP role fallback events, are unchanged.\n\n**Evidence**\n\n`coordinator_mcp_no_comms_role_fallback`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}