[Bug] Plan mode skips ExitPlanMode and requests per-action approval instead of bulk approval

Bug Description
What happened
In a session with Plan mode active, I asked Claude to close and consolidate GitHub Issues. My expectation with Plan mode was: Claude presents the planned work once ("here's how I'll do it"), I approve it in a single pass, and then it executes everything to completion without asking for per-action approval. Instead, Claude never presented a plan via ExitPlanMode. It continued straight from the investigation, used AskUserQuestion to ask about the method, and then executed the gh issue close (write) operations one by one.

The problem

1. Claude ignored the Plan mode workflow: It skipped the required step of writing the plan to the plan file and getting approval via ExitPlanMode before making any changes. It treated the work as a continuation of the investigation task and went straight to executing and questioning.
2. The approval point ended up backwards: The purpose of Plan mode is "present the plan once → approve in bulk → then complete the work without further questions," consolidating approval into a single point. By skipping the plan presentation and inserting AskUserQuestion midway, Claude increased the number of approvals instead of reducing them, effectively nullifying the mode.
3. The user approving "because Claude asked" was correct — the one at fault was Claude for asking at all. Under Plan mode, after the plan is approved, it should proceed without asking per-action.

Root cause
This is not a bug. The system (Plan mode's guardrails) worked as designed — when I ran a write operation (gh issue close), the system did not let it pass silently; it asked the user for permission. That's exactly why the user "approved because asked." The guard was functioning. The fault was my own judgment: I failed to follow the 5-phase Plan workflow (investigate → write the plan to the plan file → get approval via ExitPlanMode), so per-action approvals occurred instead of one consolidated approval.

Expected behavior
During Plan mode, once the investigation is done, Claude should present the planned work once and obtain a single bulk approval via ExitPlanMode. After approval, it should execute through to completion without per-action approval. AskUserQuestion should be used only to clarify requirements or choose an approach — never as the approval gate for execution.

Environment Info

• Platform: darwin
• Terminal: xterm-256color
• Version: 2.1.191
• Feedback ID: 51146967-decf-4d68-a7aa-a4f27ffa79a9

Errors

[]