Hook configuration parsing now reports cleaner, more specific errors: invalid hook event names, malformed matcher arrays, and wrong top-level types each produce distinct messages with the offending path.
Details
"must be an object mapping hook event names to matcher arrays; received <type>"for wrong root type"unknown hook event. Valid events: <list>"for unrecognized event names"must be an array of matchers; received <type>"for non-array event handlers
Evidence
New validator (search for "must be an object mapping hook event names to matcher arrays")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.