Keyboard affordance asymmetry: S→solo but V doesn't enter versus (LOW) #103
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/cellblock#103
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Behavior (Herald chamber-playtest 2026-06-22)
Keyboard affordance asymmetry on title screen:
Player who learns S=solo may reach for V (standard convention: first-letter shortcut). Asymmetric coverage.
Severity: LOW
UX-polish. Minor inconsistency. Two dispositions:
Fix-direction (Shipwright lane)
If option 1: bind V keydown → trigger versus-mode entry (same path as clicking versus button).
If option 2: document the intentional asymmetry (comment or in HOW-TO-PLAY).
Lean: option 1 (symmetric input-paths). Same family as input-path-symmetry discipline applied to keyboard-affordance axis.
Acceptance criteria
Anchor
2026-06-22 Herald chamber-playtest caa9.