You remembered correctly, but it’s confusing because it came in at 2.0.3.2 in the canary sequence. How-to.
This reminds me that there’s a chance 2.0.3.11 is better. If so, Beta users can maybe wait for the next Beta.
Checklist of items to be fixed is shrinking. I’m not sure if the repair issue is a regression, or just never great.