[FEATURE] User Input - consistent numerical selections

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

Some user input is a 1-2-3 selection and some is 1-2. The two has different meanings, which
increases the likelihood of the wrong selection.

Proposed Solution

I would make 1 (affirmative) and 2 (decline) the same all the time and 3 would be the exception (usually
an always allow)

Alternative Solutions

no ideas

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_