{"version":"2.1.246","anchor":"hook-event-catalogue-is-rebuilt-rather-than-cached","canonical_anchor":"hook-event-catalogue-is-rebuilt-rather-than-cached","heading":"Hook event catalogue is rebuilt rather than cached","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/hook-event-catalogue-is-rebuilt-rather-than-cached","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Hook event catalogue is rebuilt rather than cached\n\nThe hook event table is rebuilt each time instead of cached; wording is unchanged.\n\n**What**\n\nThe table describing every hook event, its summary, exit-code meaning and matcher rules, used to be cached against the sorted list of tool names. That cache and its reset method are gone and the table is now built fresh on each call. The events and their wording are unchanged.\n\n**Evidence**\n\n`Before tool execution`\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}