Device hooks registration reads a new account flag and reports when it is switched off

What

Device hooks are hooks (your own commands that run at set points) registered from your machine so they also apply in remote sessions. Whether registration happens depends on server-side account flags, and this release changes which ones it reads.

• Registration used to read tengu_violin_wood and tengu_violin_amati directly, and failed with account flags not served yet if neither had been served. It now asks a tool-serving check (isToolServingEnabled / getToolServingFlagAnsweredOff) and falls back only to tengu_violin_amati. Both flags still default to false in the code.
• When a flag answers off, registration records the flag's name and stops cleanly instead of erroring.
• Two new registration outcomes appear: flag_off, counted as OK, and flag_unanswered, counted as a failure.
• The status text for flag_off reads "not switched on for your account", next to existing statuses such as muted and stale.
• The list of recorded event names gains remote_served_shell_settings_compare and session_strip_sessions_list, and loses projects_setup_item_apply and projects_setup_resolve.

The flag server returned on for tengu_violin_amati, for this site's account and for the anonymous baseline, a change since the previous reading. It returned off for tengu_violin_wood. No reading of either has been taken under this release yet.

Why

If device hooks are not active for your account, Claude Code now says so plainly rather than reporting a failure. The flag that controls them has moved, so tengu_violin_wood may no longer be what decides.