AddSemanticDomainChange deserialization exception

Describe the bug
System.InvalidOperationException: Each parameter in the deserialization constructor on type 'LcmCrdt.Changes.AddSemanticDomainChange' must bind to an object property or field on deserialization. Each parameter name must match with a property or field on the object. Fields are only considered when 'JsonSerializerOptions.IncludeFields' is enabled. The match can be case-insensitive.

To Reproduce
Sadly, I don't really know how my attached project got into this state.
It started triggering the errors after uploading it (or trying to?). I might have tried to upload it to an existing crdt project, but I'm not actually sure 🤔

• Download boom.sqlite (Right-click -> Save link as)
• Create a new crdt project
• Stop the local web app
• Replace a new crdt project db with the attached sqlite db
• Open the project 💥

Expected behavior
No errors

Start by reproducing the failure with boom.sqlite and inspect deserialization of LcmCrdt.Changes.AddSemanticDomainChange when opening the project. Trace which constructor parameter fails to bind and verify that the attached database opens without the InvalidOperationException.