FA-31232 / Keyboard interactions / Member archive
Keyboard binding registration lifecycle: Tie ordering is accidentally oldest-first outside a special scope · case 02
The event trace violates the tie recency rule and produces incorrect keyboard state or command output.
Case contract
Events [kind,id,scope,chord,priority]. Register replaces the same id with a fresh serial. Remove deletes id; clear deletes a scope. Resolve returns highest priority matching scope/chord, breaking ties by newest registration. Empty chord never resolves. Return resolution IDs and live registrations [id,scope,chord,priority,serial]. Inputs are finite ordered event traces; return the stated deterministic state. Batch entries are independent. N varies the number of independent input transactions.
Why this case matters
Controlled keyboard event processing model for debugging application event logic.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| binding-registry scenario 3 | [[["b"], [["a", "x", "A", 2, 1], ["b", "x", "A", 1, 2]]], [["b"], [["a", "x", "A", 2, 1], ["b", "x", "A", 1, 2]]]] | [[["a"], [["a", "x", "A", 2, 1], ["b", "x", "A", 1, 2]]], [["a"], [["a", "x", "A", 2, 1], ["b", "x", "A", 1, 2]]]] | Failed |
MEMBER ARCHIVE
The complete case is available to members.
This record includes three runnable implementations, regression fixtures, execution results, and source hashes.
Member access is invitation-based. Sign in with your invited account to inspect the sources.
Sign in to the archive ↗