[FEATURE] Debug logs should indicate origin of matched hook

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

I'm losing my mind trying to figure out why Claude is running a PostToolUse hook after each Read tool call.

Read(....
⎿  PostToolUse:Callback hook succeeded: Success

There are no hooks defined along the ancestral path, nor in $HOME/.claude. It's maddening. I've rg'd and fd'd all the way down from root.

When experimented with hooks I sometimes echo 'Success'. I suspect a stale/cached hook or something.

More info: https://discord.com/channels/1072196207201501266/1354425630011166830/1465380758100246650

Proposed Solution

In the --debug logs, I observe that a hook was in fact matched. Unfortunately, the logs don't tell me where to look for this hook.

Solution: include the file path to the matched hook in the debug logs.

Alternative Solutions

_No response_

Priority

Non-Critical - But very annoying and makes me wonder what else Claude Code isn't doing quite as expected.

Feature Category

Debugging tools

Use Case Example

_No response_

Additional Context

_No response_