bmersereau strips identifiable logs from Mike's edit handler

A small cleanup that doubles as a GDPR posture fix - and surfaces a quieter bug underneath.

compliancesecurity

bmersereau opened a pull request against the upstream Mike repo removing development-era log lines that had been pairing user identities with document and edit identifiers every time a user resolved an edit. The argument is data minimization: those lines weren't load-bearing, but once a deployment ships them to a log aggregator, you've built a durable record linking people to their legal-document activity that the application itself never needed. Genuine error logs in other handlers are deliberately left alone.

Pulling the noise out exposed something else - two database writes in the same handler had been quietly swallowing their own errors, masked by the surrounding chatter. Those now propagate properly. A build-config tweak and a corrected test name come along for the ride, and three small static checks lock the handler against anyone reintroducing the identifiers later.

So what Worth a look for in-house teams and legal-ops leads who worry about what their AI tooling is whispering into observability stacks by default.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?