[FEATURE] Keep the "No" option on a consistent key across all permission prompts

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Problem Statement
The numeric key that maps to a given action in the permission prompt is inconsistent depending on how many options the prompt shows. This creates a real risk of granting persistent permission by mistake through muscle memory.
Concretely, the same key (2) means different things in different prompts:
Two-option prompt:
❯ 1. Yes

1. No, and tell Claude what to do differently (esc)

Three-option prompt:
❯ 1. Yes

1. Yes, and don't ask again for similar commands in <path>
2. No, and tell Claude what to do differently (esc)

In the first prompt, 2 is No (a safe, reversible rejection).

In the second prompt, 2 is Yes, and don't ask again (which grants persistent permission and writes a rule to settings).
A user who has built up muscle memory pressing 2 to decline will, on a three-option prompt, instead grant a permanent allow-rule — the single most consequential and hardest-to-undo action in the menu. The dangerous action and the safe action share a key.

Proposed Solution

Proposed Solution
Pin the "No, and tell Claude what to do differently" option to a stable, predictable position in every prompt — ideally always the last numbered option — and keep all "Yes" variants in the earlier positions.
This guarantees that:

"No" never shares a key with any "Yes" variant.
The most consequential option (persistent allow) is never reachable by the key a user associates with declining.
Users can build reliable muscle memory regardless of how many options a given prompt happens to show.

The key principle is positional consistency for the safe/destructive actions: the meaning of a key should not change based on the number of options rendered.

Alternative Solutions

Always keeping "Yes, and don't ask again" in a fixed slot instead — also acceptable, as long as one of the two (the decline action or the persistent-allow action) is positionally locked so they never collide on the same key.

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_