What
Hook presence checks, SessionEnd dispatch, stop-prompt registration, the permission-request check and the StopFailure dispatcher all now query a per-session hook registry rather than reading hooks out of global app state. No change to how your configured hooks fire.
Details
- The hook runner takes a
sessionHooksargument with ahas(id, event)lookup. - Tool aliases used for matcher filtering come from an optional
getToolAliases()callback instead of the tool permission context. - Teammate setup registers its Stop hook via
addFunctionHookrather than a global registration helper. - A React error was added for using the registry hook outside its provider.
Evidence
useSessionHooksRegistry cannot be called outside of an <AppStateProvider />, hook_event_name: "StopFailure", addFunctionHook
Strings lifted out of the shipped bundle, so the claim above can be checked against them.