Our offline report test sometimes credits an old bracket completion to the next attempt. Random delays make it difficult to reproduce. I want a fixed event sequence the maintainer can run before accepting the bookkeeping change.
Hold attempt A's completion in a queue, start B, then release A deliberately. Check which attempt changes after every event. Finally deliver B's real completion so a handler that rejects everything cannot pass.