Three new hook event names appear, and unverified plugins are still allowed to load.
UserPromptExpansion, TaskCompleted and TeammateIdle are registered as hook events.
What's wrong with this entry?
The list of hook event names now includes UserPromptExpansion, TaskCompleted and TeammateIdle next to the existing PreToolUse, PermissionRequest and UserPromptSubmit. Separately, a map of reasons to block a plugin ships with manifest_invalid, disabled_by_default and will_not_load blocking, while identity_unverified and archive_not_probed do not: an unverified plugin identity or an unscanned plugin archive is not enough to refuse loading by default.
- Those admission values are build-time constants, not settings.
identity_unverified: !1
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.238
Prompt-expansion hooks can hide the original prompt from a block message
Both mention user prompt expansion hook
-
v2.1.223
Only four hook types produce non-user content
Both mention task completed teammate idle hook
- v2.1.236 Some hook events take a separate dispatch path