ysbaddaden
This happens on both Intel and ARM so it's not an ARM issue (like atomic memory ordering), so maybe another case of "a thread assumption that's wrong on darwin"? See for example https://github.com/ysbaddaden/sync/actions/runs/18980770977/job/54212434592