find -rm is no longer auto-approved as a read-only command

What

Claude Code automatically allows some shell commands without asking you first, because they only read files. A find command (which searches for files) was on that list unless it used an action such as -delete or -exec. The -rm action has now been added to the blocked actions.

• Read-only check: the auto-allow pattern for find and the set of blocked find actions both now include -rm. The pattern now reads -delete\b|-rm\b|-exec\b|-execdir\b|-ok\b|-okdir\b|-fprint0?\b|-fls\b|-fprintf\b|-files0-from\b, so a find using -rm is no longer treated as safe.
• Spacing: the pattern now accepts only spaces and tabs between arguments ([ \t]+ instead of \s), so a line break can no longer separate find arguments.
• Destructive-command list: the pattern that marks commands as destructive used to match only find ... -delete. It now matches find ... -rm too, so those commands get the same handling as -delete.
• Remote switch: the -rm check sits behind a small helper, called from the bash read-only check and from one other place. It treats -rm as blocked unless the remote flag tengu_warm_sunrise has been explicitly set to false by a server. Nothing has been read about the state of this flag.

Why

Before, a find ... -rm command could match the read-only pattern and run without a permission prompt. It now goes through the normal permission check, and a server-side flag exists that could undo this.