records.db is not closed, data left in WAL
It appears that records.db is never properly closed as the write-ahead log (WAL) is always left behind.
The latest call in my records.db is from about 2.5 months ago (and the timestamp is still July 29 2022) and all call data after that is still in the WAL. It seems like it would be beneficial for data integrity if the database were properly closed when the program exits so the WAL data can be written to the actual database.
I'm on version 43~rc.0-1+b1 from debian bookworm (on a PinePhone) though this has apparently been going on for a long while.