Permission prompt: inconsistent accept/reject key positions cause miskeys

Problem

The permission prompt key mappings are inconsistent — sometimes 2 means accept, other times 2 means reject. When you're in a flow approving/denying tool calls rapidly, it's very easy to accidentally approve or reject because the key positions swap meaning between prompts.

Expected Behavior

The reject/decline option should always be in a consistent, well-separated position from the accept keys. For example:

• Accept: 1 or y
• Reject: 5, 9, or n — something well away from accept so a miskey doesn't accidentally flip the intent

Impact

Users develop muscle memory for "1 = yes" but then get burned when a different prompt style maps 2 to something unexpected. This erodes trust in the permission system because you can't be sure what you just approved or denied.

Environment

• Claude Code CLI on Windows 11
• Heavy MCP tool usage (multiple tool calls per response)
• Multiple permission prompts per session