/doctor flags context-scoped cmd+c binding as macOS conflict (false positive)

Summary

/doctor reports cmd+c in ~/.claude/keybindings.json as a potential conflict with macOS system copy, but the binding is scoped to the Scroll context only — it doesn't shadow the system shortcut at the chat prompt, and copy works correctly in practice.

Repro

~/.claude/keybindings.json contains:

{
  "context": "Scroll",
  "bindings": {
    "ctrl+shift+c": "selection:copy",
    "cmd+c": "selection:copy",
    ...
  }
}

Run /doctor. Output includes:

✘ Keybinding configuration issues · /Users/<me>/.claude/keybindings.json
  └ "cmd+c" may not work: macOS system copy

In practice, cmd+c works fine — both as the macOS system copy outside scroll/selection mode and as selection:copy inside the Scroll context after entering selection mode (shift+arrow, wheelup, etc.).

Expected

/doctor's keybinding validator should consider the binding's context before flagging a conflict. A cmd+c binding scoped to Scroll (or any non-Global/non-Chat context that requires explicit entry) is not a conflict with the system shortcut. Only flag cmd+c when it appears in Global or in always-active input contexts.

Environment

• Claude Code 2.1.153
• macOS 26.4.1 (build 25E253)