Naming inconsistency: CLI flag says "skip" but UI/settings say "bypass" permissions

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single issue (not multiple)

Description

There's a naming inconsistency between the CLI flag and the internal mode/UI terminology:

• CLI flag: --dangerously-skip-permissions / --allow-dangerously-skip-permissions
• SDK field: allow_dangerously_skip_permissions
• Terminal indicator: displays "bypass permissions" (pink text)
• Settings/internal mode: bypassPermissions

"Skip" and "bypass" are used interchangeably to refer to the same feature, which is confusing.

Proposed Fix

Either:

1. Rename the flag to --dangerously-bypass-permissions (and --allow-dangerously-bypass-permissions) to match the UI/settings terminology, or
2. Change the UI text to say "skip permissions" to match the flag name

Option 1 seems more natural since the internal mode is already bypassPermissions and the terminal indicator already says "bypass permissions" — the flag is the odd one out. A deprecation alias for the old flag name would ease the transition.

Related Issues

• #20093 — references both --allow-dangerously-skip-permissions and bypassPermissions in the same issue
• #23623 — references "bypass permissions indicator"
• #5466 — title says "Bypass Permissions", body uses --dangerously-skip-permissions

Priority

Low — cosmetic/consistency issue, not a functional bug