Swift Concurrency Fast Path Before proposing a fix: 1. Analyze or to determine Swift language mode, strict concurrency level, default isolation, and upcoming features. Do this always, not only for migration work. 2. Capture the exact diagnostic and offending symbol. 3. Determine the isolation boundary: , custom actor, actor instance isolation, or . 4. Confirm whether the code is UI-bound or intended to run off the main actor. When spawning unstructured tasks, inspect the synchronous prefix (everything before the first ): start on only when that prefix truly needs main-actor access; otherwise…