[Bug] Plan mode incorrectly requiring approval prompts for read-only operations

Bug Description
Until last weekend whenever I would start a session in plan mode, it would act in some ways as auto-mode, just limited to read-only (or scratch-only) operations; while in plan mode, all commands from plan-related sub-agents would go through auto-mode classifier, and I would be able to go entirely AFK, except for ask-user prompts and plan approval itself. Starting from last weekend something changed: now every plan mode surfaces at least some approval prompts directly to me, including trivial read-only shell commands. Auto mode itself still works correctly: after exiting plan mode into auto mode I receive no direct command approval requests. It’s only the plan mode (and its sub-agents) that got downgraded, and it degrades the experience considerably. I am forced to essentially avoid plan mode, and work in auto mode even for plan-then-implement sessions. I much prefer the prior experience.

Environment Info

• Platform: darwin
• Terminal: ghostty
• Version: 2.1.217
• Feedback ID: af3eca37-b8b4-4cae-a618-e61e75f701fb

Errors

[]