What
When your local hooks are forwarded to a cloud session, each one that is held back now says why in prose rather than being quietly dropped.
Details
- Reasons include: after-edit hooks stay on this machine; only command and http hook types can be forwarded; a matcher written as a pattern rather than a plain list is refused; a script living somewhere the cloud session can write on this machine is held unless pinned; duplicates and registrations past the cap are dropped; an entry marked
cloud: "skip"is skipped. - Standing states get their own wording too: paused, declined, disabled, unsupported, invalid and stale registrations.
Evidence
only command and http hooks can run for a cloud session
Strings lifted out of the shipped bundle, so the claim above can be checked against them.