Hooks modules only receive the commands and tool calls they match

What

Plugins can ship hooks modules: code that runs when certain events happen in Claude Code. command.run is the event for running a slash command, and tool.call is the event for Claude using a tool. Claude Code now checks before handing an event to a module whether that module wants it.

• command.run: a module's registration now records a runCommands list. A command goes to the module only if the module has a command.run hook and either lists no commands or lists that one. Before, every slash command went to it. runCommands also now appears in module analysis output.
• A built-in module, the one that reads CLAUDE_CODE_DISABLE_FILE_CHECKPOINTING, now declares runCommands: ["clear", "diff", "resume"]. Its hook now fires only for /clear, /diff and /resume.
• tool.call: the event now declares pinnedKeys. When a module's matcher rejects an event on a pinned key, Claude Code skips that module in the main process instead of sending the event to it. If the matcher fails with an error there, Claude Code logs "matcher threw on the host ...; the hop decides" and lets the module decide.

Why

Modules no longer receive every slash command or every tool call when they only care about some. This avoids an extra round trip to the module for events it would ignore anyway. Plugin authors can rely on a command.run hook seeing only the commands it lists.