my old UR5e result keeps winning the race

I can reproduce this offline now: hold the completion for one inspection attempt, start the next, then release the held event. The new row gets marked complete. Or rather, the shared current-row handler marks it complete without checking which attempt answered. I want the regression test to choose that delivery order explicitly; another longer sleep only makes the bug less keen to turn up.