terminal-setup incorrectly claims Warp does not support Shift+Enter

Description

The /terminal-setup command (terminal setup skill) outputs the following message when running inside Warp terminal:

Note: Warp does not support custom Shift+Enter keybindings.
Use backslash (\) + Enter for multi-line input.

This is incorrect — Warp does support Shift+Enter for multi-line input. The keybinding works natively in Warp without any extra configuration.

Expected behavior

The /terminal-setup command should not display the note about Warp lacking Shift+Enter support, or should accurately reflect Warp's current keybinding capabilities.

Actual behavior

The command warns users to use \ + Enter as a workaround for a limitation that doesn't exist.

Steps to reproduce

1. Open Claude Code inside Warp terminal
2. Run /terminal-setup
3. Observe the incorrect note about Shift+Enter

Environment

• Claude Code v2.1.25
• Warp terminal v25.2.1
• macOS

Screenshot

The screenshot below shows the /terminal-setup output with the incorrect note, running inside Warp where Shift+Enter works fine:

<img width="1867" height="793" alt="how it's shown on cc terminal: no issue on shift+enter" src="https://github.com/user-attachments/assets/29e46e48-9451-4c58-8424-3362c7b7685f" />

(Screenshot available — Warp terminal showing Claude Code /terminal-setup output with the incorrect Shift+Enter warning)