During that rollout, did you hit any issues with async tests that looked correct but still failed?

Async tests that use timing-based waits instead of state-based signals can produce flaky results. Swift Testing is stricter than XCTest about async completion, meaning code that returned before side effects finished would silently pass in XCTest but fail in Swift Testing. The fix is making async boundaries explicit and waiting on real completion signals rather than arbitrary delays.