{"version":"2.1.257","anchor":"hook-execution-now-distinguishes-did-not-run-from-other-fa","canonical_anchor":"hook-execution-now-distinguishes-did-not-run-from-other-fa","heading":"Hook execution now distinguishes 'did not run' from other failures","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/hook-execution-now-distinguishes-did-not-run-from-other-fa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Hook execution now distinguishes 'did not run' from other failures\n\nHook results now say specifically when the hook's process never ran, separate from a bad exit code or invalid JSON.\n\nHook execution results now record a distinct `hook_did_not_run` failure reason, with an explicit stderr-inclusive message, when a PreToolUse or other hook's script process never actually ran. This is separate from a generic nonzero exit code or JSON-validation failure, making it clearer why a hook had no effect.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}