[Bug] Terminal setup incorrectly rejects Windows Terminal on Windows

Bug Description
I ran /terminal-setup and the Claude wrote to me that "Terminal setup cannot be run from windows-terminal.". At the same time in the instructions it mentions, that I should run it in one of these terminals: "Windows: Windows Terminal". I am in Windows Terminal/PowerShell. Windows Terminal version 1.24.10921.0.

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.119
• Feedback ID: ed2ccdc3-b649-43a7-bfab-9122801a75ff

Errors

[{"error":"Error: Request was aborted.\n    at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:3448)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-26T13:33:24.325Z"},{"error":"McpToolCallError: MCP error -32602: Input validation error: Invalid arguments for tool resolve-library-id: [\n  {\n    \"expected\": \"string\",\n    \"code\": \"invalid_type\",\n    \"path\": [\n      \"libraryName\"\n    ],\n    \"message\": \"Invalid input: expected string, received undefined\"\n  }\n]\n    at XC_ (B:/~BUN/root/src/entrypoints/cli.js:4885:63)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-26T13:35:38.094Z"},{"error":"McpToolCallError: MCP error -32602: Input validation error: Invalid arguments for tool resolve-library-id: [\n  {\n    \"expected\": \"string\",\n    \"code\": \"invalid_type\",\n    \"path\": [\n      \"query\"\n    ],\n    \"message\": \"Invalid input: expected string, received undefined\"\n  }\n]\n    at XC_ (B:/~BUN/root/src/entrypoints/cli.js:4885:63)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-26T13:35:42.964Z"}]