FA-31068 / Keyboard interactions / Member archive
Owned repeat deadline scheduler: Initial timer drain omits exact-boundary or overdue deadlines · case 03
The event trace violates the first inclusive rule and produces incorrect keyboard state or command output.
Case contract
Case [delay,period,events], events [kind,key,time]. First down per key emits immediately and schedules first repeat at time+delay. Tick drains every deadline at or before time, ordered by deadline then key. Up removes only that key, blur clears all. Return emissions [key,time] and sorted pending deadlines. Positive delay and period; times nondecreasing. 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 |
|---|---|---|---|
| repeat-clock scenario 1 | [[[["A", 10]], [["A", 15]]], [[["A", 10]], [["A", 15]]], [[["A", 10]], [["A", 15]]]] | [[[["A", 10], ["A", 15]], [["A", 17]]], [[["A", 10], ["A", 15]], [["A", 17]]], [[["A", 10], ["A", 15]], [["A", 17]]]] | 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 ↗