Tianyi Cui 24e9c0fa70 fix(hook-protocol): discard a hookSpecificOutput block whose hookEventName mismatches the firing event ...

The reference schemas key the `hookSpecificOutput` block by `hookEventName`, so
a block naming a DIFFERENT event than the one firing is malformed — a hook
emitting `hookSpecificOutput.hookEventName: "PreToolUse"` on a `Stop` event must
not deny the Stop. The codec surfaced `hookEventName` for a bridge to compare but
never enforced the discard, so both bridges pushed every parsed output into the
merge unconditionally.

parseHookOutput now takes an optional `expectedEventName`; when the block's
`hookEventName` names a different event, its event-scoped fields
(permissionDecision/permissionDecisionReason/additionalContext/updatedInput) are
discarded (the discriminator is still surfaced for the log, and the
event-agnostic top-level decision/continue/etc. are unaffected). runHook threads
it via RunHookOptions.expectedEventName; a caller that omits it opts out.

Codex review finding on the bridges PR (PR-F); fixed here on the codec that owns
the fold and knows field provenance, then flows down to both bridges.

2026-07-01 10:45:58 +08:00

..

codec.spec.ts

fix(hook-protocol): discard a hookSpecificOutput block whose hookEventName mismatches the firing event

2026-07-01 10:45:58 +08:00

events.spec.ts

feat(hooks): dsh-hook-protocol — shared Claude Code / Codex hook wire-protocol core

2026-07-01 00:41:53 +08:00

matcher.spec.ts

feat(hooks): dsh-hook-protocol — shared Claude Code / Codex hook wire-protocol core

2026-07-01 00:41:53 +08:00

merge.spec.ts

fix(hooks): merge surfaces the WINNING decision's reason, not only deny's

2026-07-01 02:20:12 +08:00

runner.spec.ts

fix(hook-protocol): discard a hookSpecificOutput block whose hookEventName mismatches the firing event

2026-07-01 10:45:58 +08:00