Misleading UI message: "/terminal-setup" message suggests enabling alt+p, but it only configures Shift+Enter

Description

The Claude Code interface displays a message "To enable alt+p, run /terminal-setup" when alt+p is not functional. However, running /terminal-setup does NOT enable alt+p. The command only configures Shift+Enter (multiline input shortcut).

This creates confusion because:

1. User sees the suggestion and runs /terminal-setup
2. Command succeeds (shows "Installed iTerm2 Shift+Enter key binding")
3. alt+p still doesn't work
4. User is left wondering what went wrong

Environment

• Claude Code version: v2.0.76
• OS: macOS (iTerm2)
• Terminal: iTerm2

Current Behavior

After running /terminal-setup, the message still appears: "To enable alt+p, run /terminal-setup"

Expected Behavior

The UI should either:

1. Option A: Remove the alt+p suggestion from the /terminal-setup output, OR
2. Option B: Show accurate instructions that alt+p requires separate terminal configuration (Option as Meta key in iTerm2 settings)

Steps to Reproduce

1. Open Claude Code in iTerm2
2. See the message "To enable alt+p, run /terminal-setup"
3. Run /terminal-setup
4. Command completes with "Installed iTerm2 Shift+Enter key binding"
5. Try alt+p - it still doesn't work
6. See the same message again

Root Cause

/terminal-setup only handles Shift+Enter configuration. alt+p requires a completely separate setup:

• Users must manually enable Option as Meta key in iTerm2 → Settings → Profiles → Keys

Suggested Fix

Update the UI message logic to:

• Only suggest running /terminal-setup if Shift+Enter isn't configured
• For alt+p, direct users to the terminal configuration steps instead

Impact

Medium - Confuses users and makes them think Claude Code has a bug or doesn't work properly