Silent key update broke 40 verified records, exposing a gap in dual-tool checks

A developer discovered that 40 signed records failed verification after a cryptographic key row was edited in place rather than retired and replaced with a new entry. Both independent verification tools correctly reported failure, but neither could detect that the key material had changed since the records were originally signed. The root cause was a database row update that overwrote the public key and scheme fields under the same key ID, making legitimately signed records indistinguishable from forgeries. The issue went unnoticed for a day, highlighting that two independent tools share the same blind spots when both read from the same flawed source. The fix involved adding the retired key as a second row rather than deleting anything, and the writer was updated to loudly log key material on every run to surface future changes immediately.