{"version":"2.1.229","anchor":"goal-set-events-gain-an-origin-one-shot-warnings-share-a-reg","canonical_anchor":"goal-set-events-gain-an-origin-one-shot-warnings-share-a-reg","heading":"Goal-set events gain an origin, one-shot warnings share a registry","tier":"internal","area":"Goals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/goal-set-events-gain-an-origin-one-shot-warnings-share-a-reg","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Goal-set events gain an origin, one-shot warnings share a registry\n\nGoal events record their origin, and one-time warnings now go through a shared registry.\n\n**What**\n\n`goal_set` telemetry now records where the goal came from, such as \"restored\". Two module-level \"log this once\" booleans, for the provider route event and the max-retries clamp warning, were replaced by a shared registry keyed by name.\n\n**Evidence**\n\n`max_retries_clamp_warning`\n\n- Area: Goals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}