Text fields swallow standard editing keys (Ctrl+A et al.)

[aksOps]

Question

Dogfood finding (user, 2026-08-20): Ctrl+A does not work in the text area. Text fields should follow standard editing conventions.

Diagnose and fix: bubbles textinput/textarea ship a default readline-style keymap (ctrl+a line start, ctrl+e line end, ctrl+k kill-to-end, ctrl+u kill-to-start, ctrl+w delete-word, alt arrows). Find where kb's key routing intercepts these before the focused field sees them (editor, settings, filter, kill-reason prompt, ADR/import inputs) and let every focused text field receive the full default editing keymap. Audit for other swallowed editing keys while there - fix the class, not the instance. Note: if a wanted key conflicts with a frozen v1.0.1 global binding while a field has focus, field focus wins (typing context beats global shortcuts) - record any such call in the resolution.

Assumption recorded: 'Ctrl+A' means the readline line-start convention (charm's own default). Select-all does not exist in bubbles' textarea (no selection model) - if the user meant select-all, that is a charm gap needing separate discussion.

Regression tests for the editing keys per field. Coverage gates hold. Interaction outside focused-field typing stays frozen.

Part of #136.

[aksOps]

Scope correction (user, 2026-08-20): no new readline aliases. The convention here is Home/End for line start/end - "no need to add extra keybinding". Revised scope for this ticket:

1. Verify Home/End and the editing keys bubbles fields already bind by default (word-wise alt+arrows, backspace variants, cursor arrows) actually reach every focused text field, and fix anywhere kb routing swallows or shadows them. The typing-context-beats-global-shortcuts rule stands.
2. No kb-level ctrl+a binding is added. Whatever bubbles ships by default is left as-is.
3. Regression tests target Home/End per field class instead of ctrl+a.

Ctrl+A-as-select-all remains a separate open question and is out of scope here.

[aksOps]

Resolved in #160 (squash-merged, 744f945).

Root cause

The root key routing was already clean. internal/tui/model.go forwards every key to whichever overlay is open, and ctrl+c is the only key that stays global. The swallowing lived inside two panes, where a stepper control claimed keys that belong to whatever text field currently has focus.

What was swallowed, where

• Card editor, due field (internal/tui/cardeditor/model.go, updateDuePicker): alt+left and alt+right were bound to date -1/+1. Those are textinputs WordBackward and WordForward, so word motion was dead in that field.
• Issue import, reference field (internal/tui/issueimport/model.go, updateInput): left, right, h, and l were handled before dispatching to the input, for every focus. With the reference field focused, cursor motion was dead and the letters h and l could not be typed at all - any owner/repo containing either was unenterable. This was the worse of the two.

Audited and found already correct: board filter input, kill-reason prompt, settings AI and integration-row inputs, ADR split paste/file-path/row-title inputs, card detail comment and link inputs. All forward unconsumed keys straight to the focused field.

Focus-conditional calls on frozen v1.0.1 bindings

Both are the same rule - a pane shortcut that collides with a focused field yields to the field:

• left/right/h/l in the issue import overlay still step the source and count controls, but only while those controls hold focus, never while the reference input does.
• alt+left/alt+right in the card editor no longer step the due date at all. [ and ] remain the date stepper, so the keyboard path to adjust a date is intact; [ and ] are not in the bubbles default keymap, so nothing collides.

Scope as corrected

Per the user correction above, no readline aliases were added. ctrl+a gains no kb-level binding; whatever bubbles ships is left untouched. Ctrl+A-as-select-all stays a separate open question.

Verification

Regression tests per field class assert Home moves the cursor to line start and End to line end, in: card editor title/emoji/desc/due/checks/labels/ai-prompt, board filter input, kill-reason prompt, settings AI input, settings integration-row input, ADR split paste/file-path/row-title, issue import reference, card detail comment and link inputs. Plus word-motion tests on the title and due fields and a test pinning [/] as the date stepper. Both defects were caught red first.

• go build ./... clean
• go vet ./... clean
• go test -race ./internal/tui/... 672 pass
• sh scripts/check-go-coverage.sh 96.9% total against the 96.4% gate; no package below its floor
• CI: 9/9 green