FA-31324 / Keyboard interactions / Member archive

Layered physical keyboard remapping: Falsy defined remaps are confused with transparent missing entries · case 04

The event trace violates the defined entry rule and produces incorrect keyboard state or command output.

Member previewVariant 4 · 3 implementations · 8 checks per implementation

Case contract

Case [layers,events]. layers maps layer names to key-to-output maps; None output blocks a key and empty string is valid output. Events [kind,a,b]. Push adds a known layer unless already active; pop removes named layer; key resolves from newest active layer defining the key, falling through transparent missing entries to original key. Clear removes layers. Return emitted strings and layer stack. 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
remap-layers scenario 5	`[[["A", "B", "C"], ["one"], 0], [["A", "B", "C"], ["one"], 0], [["A", "B", "C"], ["one"], 0], [["A", "B", "C"], ["one"], 0]]`	`[[["", "C"], ["one"], 1], [["", "C"], ["one"], 1], [["", "C"], ["one"], 1], [["", "C"], ["one"], 1]]`	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.