FA-30864 / Keyboard interactions / Member archive
Physical press ownership registry: Peak simultaneous keys is replaced by the latest or cumulative count · case 04
The event trace violates the peak count rule and produces incorrect keyboard state or command output.
Case contract
Events are [kind,device,code,location]. Down inserts a unique physical token; up removes exactly that token; disconnect clears that device; blur clears all. Track maximum simultaneous held count, accepted presses, releases, orphan ups and sorted held tokens. 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 |
|---|---|---|---|
| physical-registry scenario 5 | [[[["a", "D", 0]], 1, 4, 3, 0], [[["a", "D", 0]], 1, 4, 3, 0], [[["a", "D", 0]], 1, 4, 3, 0], [[["a", "D", 0]], 1, 4, 3, 0]] | [[[["a", "D", 0]], 2, 4, 3, 0], [[["a", "D", 0]], 2, 4, 3, 0], [[["a", "D", 0]], 2, 4, 3, 0], [[["a", "D", 0]], 2, 4, 3, 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.
Sign in to the archive ↗