Skip to content

docs/comments: stale ⌃C-family hotkey mentions contradict the published hotkeys.json contract (#1920/#1924 follow-up) #1925

Description

@qingyun-wu

Follow-up to #1920 / #1924 (single-source hotkey contract via state/hotkeys.json). Both reviews noted a remaining family of stale hotkey mentions that are comments/docs only — not consumers of the contract — so they were correctly left out of those PRs, but they still assert hotkeys (⌃C family) that the current Electron app build does not register:

  • src/Sutando/main.swift:13 — header comment still lists the ⌃C/⌃V/⌃M globals from the retired Swift menu-bar app lineage.
  • context-drop skill docs — reference the ⌃C-family capture hotkeys; on Electron builds (0.7.0-rc2+) the working capture path is ⌘⇧M / menu-bar drop.

Why it matters: these are exactly the copies that mislead live debugging when hotkeys "don't work" (this bit us on 2026-07-03 — an operator + agent spent a session chasing dead ⌃C bindings that the false-positive health-check line, since fixed in #1924, appeared to confirm).

Suggested fix: sweep for the ⌃C-family strings across comments/docs (grep -rn '⌃C\|⌃V\|⌃M'), and either delete the stale claims or replace them with a pointer to the published state/hotkeys.json contract ("hotkeys are whatever the app publishes — see docs/…"). No behavior change.

Refs: john-the-dev's #1920 review note and #1924 LGTM (2026-07-05) which enumerated the remaining copies.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions