{"version":"2.1.248","anchor":"bad-hook-matchers-are-reported-against-the-event-they-belong","canonical_anchor":"bad-hook-matchers-are-reported-against-the-event-they-belong","heading":"Bad hook matchers are reported against the event they belong to","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/bad-hook-matchers-are-reported-against-the-event-they-belong","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Bad hook matchers are reported against the event they belong to\n\nBad hook matchers now produce an error naming the event they belong to.\n\n**What**\n\nHook configuration validation now checks each matcher with rules specific to the event it is attached to, and the resulting error names that event instead of failing generically.\n\n**Details**\n\n- Event rules live in a lookup table keyed by event name; a `tool.call` entry is read from it.\n\n**Evidence**\n\n`SITE_RULES`\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}