/terminal-setup rejects Windows Terminal despite suggesting it

Bug

/terminal-setup in Windows Terminal fails with:

Terminal setup cannot be run from windows-terminal.
...
To set up the shortcut (optional):
1. Exit tmux/screen temporarily
2. Run /terminal-setup directly in one of these terminals:
   • Windows: Windows Terminal

The error message tells the user to run the command in Windows Terminal — which is exactly where they already are.

Root Cause

Found by searching the compiled binary (claude.exe v2.1.100). The gate function hCH() controls which terminals are allowed to proceed with setup:

function hCH() {
    return bt.platform() === "darwin" && M$.terminal === "Apple_Terminal"
        || M$.terminal === "vscode"
        || M$.terminal === "cursor"
        || M$.terminal === "windsurf"
        || M$.terminal === "alacritty"
        || M$.terminal === "zed"
}

"windows-terminal" is not in this list, so hCH() returns false and the error branch runs. The error branch then detects platform === "windows" and helpfully suggests "Windows: Windows Terminal" — creating a contradictory message.

Additionally, the setup dispatcher Ci8() has no case "windows-terminal" handler, so even if the gate were fixed, there's no setup logic to execute.

Expected Behavior

Either:

1. Implement Windows Terminal support — add "windows-terminal" to hCH() and a corresponding handler in Ci8() that configures the Shift+Enter keybinding (Windows Terminal supports custom keybindings via settings.json), OR
2. Remove the misleading suggestion — don't suggest "Windows: Windows Terminal" in the error message if it's not actually supported

Environment

• Claude Code 2.1.100
• Windows 11 Pro (Build 26200)
• Windows Terminal with PowerShell 7.6
• Terminal correctly detected as windows-terminal