[BUG] Plan mode skips re-confirmation after user provides additional clarification

Bug Description

When in plan mode, after Claude presents a plan and offers three options (auto-accept edits / manually approve / provide additional input), choosing "provide additional input" and submitting new requirements causes Claude to skip re-confirmation entirely and jump straight into acceptEdits execution mode — instead of revising the plan and presenting it again for approval.

Steps to Reproduce

1. Enter plan mode (via /plan or Shift+Tab)
2. Ask Claude to write a plan for a task
3. Claude generates a plan and presents the confirmation dialog with options:

• Yes, clear context and auto-accept edits
• Yes, and manually approve edits
• No, provide additional input

1. Select "No, provide additional input"
2. Type additional requirements/clarifications and submit

Expected Behavior

Claude should:

1. Receive the additional requirements
2. Revise the plan based on the new input
3. Re-present the updated plan with the same confirmation dialog
4. Wait for user to explicitly accept before executing

Actual Behavior

Claude receives the additional requirements and immediately exits plan mode into acceptEdits mode, beginning execution without ever showing the revised plan or asking for re-confirmation.

The user's feedback is treated as implicit approval rather than a request for plan revision.

Environment

• Claude Code version: 2.1.87
• OS: macOS (Darwin 25.3.0, arm64)
• Terminal: Kitty + Fish shell

Related Issues

This appears to be part of a broader class of plan mode state transition bugs:

• #9701 — ExitPlanMode bypasses plan mode restrictions and auto-approves without user consent
• #14004 — Claude executes edits when "Exited Plan Mode" reminder appears without user approval
• #2988 — Auto-Accept mode auto-enables when exiting plan mode
• #3452 — Unclear plan mode completion and mode transitions
• #21292 — Claude makes non-readonly edits after ExitPlanMode is rejected

Possible Root Cause

The model appears to interpret the user's additional input as a signal to proceed with execution, rather than as a request to revise and re-confirm the plan. The ExitPlanMode tool may be auto-invoked after receiving feedback, bypassing the plan revision → re-confirmation loop.