Swift Testing Code Review Hard gates Complete in order before recording Swift Testing review findings. Stack with for universal review rules. 1. Scope: You have an explicit list of paths under review (or a user-named single file). Pass: Paths captured in working notes or one line: — then stop with no findings. 2. Swift Testing surface: For each path you treat as Swift Testing code, confirm or / / / appears in that file (open or search). Pass: At least one match per critiqued file, or you exclude that file from Swift Testing review with a one-line reason (e.g. XCTest-only). 3. Evidence + proto…