A scripted key tap the game never saw

Symptoms

Reference frames captured with a key script drift from the port by one step: one capture shows the screen as it was before the key, and every later capture is one key behind.

Cause

The game reads the keyboard's state (DirectInput GetDeviceState) once a frame. A script that sends key down and key up within a few milliseconds can fall between two reads, and the game never sees the key. In POD one "Enter" on the records screen was lost this way.

What to do

Hold scripted keys for at least two frames (podinput steps KEY with a wait while held, or a hold option). When checking existing captures, find the step the game missed and replay the sequence as the game saw it; crates/pod-ui/tests/frames.rs lists such captures in MISSED with the reason.