User reported that on Windows PowerShell 7.1, pressing Shift+Tab to cycle edit modes does nothing — the mode stays on auto and never reaches yolo.

Likely cause: src/cli/ui/key-normalize.ts:30 only matches the xterm-style back-tab sequence \x1b[Z for Shift+Tab. Windows-side terminals can encode Shift+Tab differently depending on which host the user is in (Windows Terminal forwards xterm-style sequences, but legacy conhost / some PowerShell host configurations send Windows console input records that don't translate to [Z).

Need:

• Confirm which host the user is in (Windows Terminal vs conhost vs VS Code integrated)
• Capture the actual byte sequence Shift+Tab produces in that environment (a small process.stdin.on('data') dump is enough)
• Either add the alternate sequence to the back-tab match list, or document a fallback (e.g. a slash command / explicit key) for environments that don't emit [Z

Workaround for the user in the meantime: a typed command path to switch modes (today edit-mode is keyboard-only AFAIK), so users on terminals that drop Shift+Tab aren't stuck.