I sent the report a few hours too early. The enclosed picture should have been:

with a status of Critical due to bug 1392937. And update the SQLite on M-C has broken Gloda. This happened during the reporting period but due to various other failures I only detected it after the report was sent. Quoting Andrew Sutherland from that bug:

pragmatically (and dramatically speaking), now that we've hit Firefox 57 and no longer need to worry about maintaining compatibility for legacy extensions, there's a non-trivial potential for mozStorage to break gloda going forward in other ways. I think one of the following needs to happen:

• Thunderbird does the gecko fork thing that was discussed at some point (I haven't kept up), maybe forking prior to this change.
• Someone on the Thunderbird team needs to take on responsibility for updating gloda to compensate for mozStorage changes. Gloda has very meager binding needs other than the FTS3 stuff, so this might not be that hard to do. Especially if someone already has to un-break the calendar pieces. (I think calendar does database stuff?) This is the type of thing I'm willing to help mentor someone on as needed.
• Turn off/disable gloda.