[Bug] /hooks interactive mode: pressing 'n' key triggers go back navigation

Description
In the /hooks command's interactive mode, the letter 'n' is globally bound as a "go back" shortcut key throughout the entire flow. This makes it impossible to input any text containing the letter 'n' in any input field.

Environment

• OS: Windows
• Claude Code version: 2.1.12

Steps to Reproduce

1. Run the /hooks command
2. At any input stage (selecting hook type, entering command, entering matcher, etc.)
3. Try to type the letter 'n'
4. Observe that it immediately goes back to the previous step instead of inputting the letter

Expected Behavior
The letter 'n' should be input normally into text fields. Navigation shortcuts should use key combinations (e.g., Ctrl B, ESC) instead of single letters.

Actual Behavior
The single letter 'n' triggers a navigation action ("go back") across the entire /hooks interactive flow.

Impact

• Cannot input common words like Notification, node, npm, powershell, python, etc.
• Makes the /hooks command nearly unusable for any command containing the letter 'n'
• Users must work around this by:
• Manually editing settings.json directly
• Copy-pasting pre-written commands with Ctrl V
• Using cursor navigation to insert 'n' after typing other characters

Related Issues

• #6674 (Hook navigation infinite loop)
• #11265 (Arrow key navigation trapped)