FA-31038 / Keyboard interactions / Member archive

Release activated command binding: Owner departure removes a token named after the owner or clears other owners · case 03

The event trace violates the departure remove rule and produces incorrect keyboard state or command output.

Member previewVariant 3 · 3 implementations · 10 checks per implementation

Case contract

Events [kind,key,owner]. Down arms a key for its owner; repeated down preserves the original owner. Up emits key only for matching key and owner then always disarms that physical key. Cancel clears all pending keys; owner-left clears that owner. Return emitted key-owner pairs and sorted pending pairs. 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 fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
release-binding scenario 7	`[[[], [["A", "one"], ["B", "one"], ["C", "two"]], 2, 0], [[], [["A", "one"], ["B", "one"], ["C", "two"]], 2, 0], [[], [["A", "one"], ["B", "one"], ["C", "two"]], 2, 0]]`	`[[[], [["C", "two"]], 2, 0], [[], [["C", "two"]], 2, 0], [[], [["C", "two"]], 2, 0]]`	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.