Cloud device hooks treated as author opt-in and run from the project folder

What

A hook is a command that runs automatically at certain moments, such as when Claude uses a tool. A cloud session can mark a hook device in its settings so it runs on your machine. This release changes how such hooks are described and treated:

• Description: the author_opt_in field now reads "Runs at the hook author's explicit request (cloud: 'device' in its settings entry): it starts in the project folder, and its command may not be pinned to a script the session cannot change." Before, it said the hook was forwarded at the author's request although its command was not pinned to such a script.
• Counted as opted in: author_opt_in is now set for a hook with authorOptIn, and also for a cloudDevice hook of type command. Before, only authorOptIn set it.
• Hooks listing: entries can now carry optedIn, taken from author_opt_in, and exceptAfterEdits, set from a check on the hook's event and matcher.

Why

If a cloud session runs hooks on your machine, those command hooks start in your project folder and are now treated as opted in by their author, and the hooks listing can show which ones are.