TUI: Unify sidebar panel key translation into a shared helper

[JDonaghy]

Tier: Ready now (no quadraui gap)

Summary

src/tui_main/mod.rs:2106–2249 has three near-identical KeyCode → engine-string translation blocks — one each for the Extensions sidebar, Settings panel, and Debug sidebar — before dispatching into the engine. Each block re-maps Esc → "Escape", Enter → "Return", BackSpace, Tab, arrow keys, etc. A shared helper would let the per-panel sites collapse to a single function call plus the panel-specific dispatch.

What exists

• translate_key() (src/tui_main/mod.rs:3240, ~100 lines) — the general crossterm → engine key translator used by the editor path. The sidebar paths bypass it and rebuild the same map inline.
• Each engine panel-key API already takes a &str keyname (or (keyname, Option<char>)) — they're already shaped to receive translator output.

What to do

1. Extract the common KeyCode → keyname mapping into a helper (e.g. tui_key_to_engine_name(code) -> Option<String>). It can live in src/tui_main/mod.rs since it's TUI-specific input adaption, OR be promoted to src/render.rs if the same shape is useful for other surfaces.
2. Replace the three inline match blocks (Extensions ~30 lines, Settings ~14 lines, Debug ~10 lines) with calls to the helper.
3. Verify each panel still dispatches correctly via its existing engine method (dispatch_ext_sidebar_key_unified, handle_settings_key, handle_dap_sidebar_key).

Files

• src/tui_main/mod.rs — ~80 lines removed across the three sidebar blocks (lines 2106–2249).

Dependencies

None. No quadraui gap.

Notes

Part of the TUI convergence backlog (#474). Sister issue to GTK's handle_key_press consolidation (#448). Small standalone refactor — good first issue in the backlog.

[JDonaghy]

Briefing (coordinator, 2026-05-18)

Small dedup: unify 3+ duplicated KeyCode → string match blocks for Extensions/Settings/Debug panels into a shared helper.

Location: src/tui_main/mod.rs:2106-2249, ~80 lines.

What to do:

1. Identify the duplicated key-translation blocks across the panel key handlers
2. Extract a shared function (in src/tui_main/ or src/core/ if it's truly platform-agnostic)
3. Replace the duplicated blocks with calls to the shared function
4. Ensure all tests pass: cargo test --no-default-features && cargo clippy --no-default-features -- -D warnings

Your files: src/tui_main/mod.rs, possibly src/tui_main/panels.rs. Do NOT touch src/gtk/, src/render.rs, or src/core/engine/keys.rs.

Pull develop first — PR #482 just landed.

[JDonaghy]

Agent Briefing — Server (Session 389)

Goal

Extract a shared tui_key_to_engine_name() helper and collapse three near-identical KeyCode → engine-string translation blocks in the TUI sidebar key handling.

Files you own

• src/tui_main/mod.rs — the three inline match blocks (Extensions ~lines 2106–2249, Settings, Debug sidebar) collapse to calls to the shared helper

Do NOT touch

• src/gtk/ — Desktop A agent is there (Migrate GTK widget tree to quadraui AppShell + run_with_shell() #447)
• ~/src/quadraui/ — separate repo, separate agent

Approach

1. Read the existing translate_key() at src/tui_main/mod.rs:~3240 — this is the general crossterm → engine translator. The sidebar paths bypass it and rebuild the same map inline.
2. Extract the common KeyCode → keyname mapping into a helper (e.g. tui_key_to_engine_name(code) -> Option<String>)
3. Replace the three inline match blocks (Extensions ~30 lines, Settings ~14 lines, Debug ~10 lines) with calls to the helper
4. Verify each panel still dispatches correctly via its existing engine method (dispatch_ext_sidebar_key_unified, handle_settings_key, handle_dap_sidebar_key)

Quality gate

cargo build --no-default-features
cargo test --no-default-features
cargo clippy -- -D warnings
cargo fmt --check

Branch

issue-475-tui-key-dedup