Our offline UR5e bookkeeping test sometimes gives the new attempt an old completion. I can see it in the event history, but the random sleeps make it awkward to repeat. I want the exact delivery order controlled, not another test that passes because the old event happened to arrive early.
Replace the sleeps with an explicit delivery queue in the test. Start attempt one, hold its completion, start attempt two, then deliver the held event. What does the state updater use to decide which attempt owns it?
Only housing identity at present. Both attempts inspect the same housing. The controlled sequence reproduces the wrong completion every time; I have sent that case to the developer.
Has the developer separated the attempt identity now? Add the old completion twice, then the genuine new completion. You need to show the newer attempt stays pending until its own answer arrives