Implement KeybindingRegistry with scope-based resolution (mode/window/global) #138

New issue

Open

opened 2026-03-15 04:13:32 +00:00 by freemo · 0 comments

freemo commented

2026-03-15 04:13:32 +00:00

Owner

Metadata

Commit Message: feat(ui): implement KeybindingRegistry
Branch: feature/m2-keybindings

Background and Context

KeybindingRegistry resolves key input against three scopes in priority order: mode bindings (editor, combat), window bindings (per window type), global bindings. First match wins.

Acceptance Criteria

Implementation matches specification
BDD test coverage

Subtasks

Implement as specified
Write Cucumber feature file and step definitions

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line of the commit message matches the
Commit Message in Metadata exactly.
The commit is pushed to the remote on the branch matching the Branch in Metadata.
The commit is submitted as a pull request to master, reviewed, and merged.

## Metadata - **Commit Message**: `feat(ui): implement KeybindingRegistry` - **Branch**: `feature/m2-keybindings` ## Background and Context KeybindingRegistry resolves key input against three scopes in priority order: mode bindings (editor, combat), window bindings (per window type), global bindings. First match wins. ## Acceptance Criteria - Implementation matches specification - BDD test coverage ## Subtasks - [ ] Implement as specified - [ ] Write Cucumber feature file and step definitions ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged**.