Repository navigation
[triage test] Proposal: unify the power keybind dispatch #83
Description
Is your proposal related to a problem? Please describe.
The 9 power keybinds each map to a fixed PowerList index, which makes per-suit keybind layouts rigid and hard to extend when a suit has more than 9 powers.
Describe the solution you'd like to propose
Introduce a keybind-to-power binding layer so each suit can declare its own ordered keybind map, decoupling the physical key from the PowerList index.
Describe alternatives you've considered
Leaving the fixed 1-9 mapping and just documenting it; or a radial menu instead of fixed keys.
Additional context
This is a test issue to verify how the AI triage handles proposals - safe to close.
Activity
github-actions commentedon Jun 7, 2026
🤖 auto-triage (github models)
🛠️ Recommended implementation
Implementing a keybind-to-power binding layer would allow each suit to specify its own key arrangement, enhancing usability. This may be integrated within the PowerRegistry or a new configuration class that manages bindings. The task involves changing how keypress events are processed in relation to the assigned power indices.
labels and insight are a best guess, a maintainer will confirm.
duzos commentedon Jun 7, 2026
triage test complete (proposal path verified) - closing.