What's wrong with this entry?
The /goal skill now reports a more specific reason when it cannot run due to hook policy settings.
- Old message:
"/goal is disabled by your organization's policy (disableAllHooks)." - New message:
"/goal can't run while hooks are disabled (disableAllHooks or allowManagedHooksOnly is set in settings or by policy)." - The
allowManagedHooksOnlypolicy mode (which restricts hooks to a managed subset) is now correctly cited as a blocking reason in addition to the existingdisableAllHookssetting.
Updated goal-blocked message (search for "allowManagedHooksOnly is set in settings or by policy")
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.