Tianyi Cui 8f2ef9dc9b docs(hook-protocol): matcher's invalid-regex handling is SILENT, not bridge-logged ...

Review noted the module docs promised an invalid regex is "logged by the bridge",
but matchesMatcher only returns `false` — callers cannot distinguish a genuine
non-match from a compile failure, so a typo'd pattern silently disables that
matcher with no warning. Both bridges call matchesMatcher directly, so no log
happens anywhere. Correct the docs to state the silence explicitly; surfacing bad
config would need a diagnostic-returning variant or parse-time validation, marked
TODO(matcher-diagnostics). No behavior change.

2026-07-01 15:58:56 +08:00

..

codec.ts

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

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

events.ts

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

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

index.ts

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

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

matcher.ts

docs(hook-protocol): matcher's invalid-regex handling is SILENT, not bridge-logged

2026-07-01 15:58:56 +08:00

merge.ts

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

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

runner.ts

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

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

types.ts

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

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