Is it the navigation property that is throwing the rogue entry for the property?
If that navigation property could be persisted somehow in the entity change set it would be great. In my own implementation I could cut into EntityHistoryStore.SaveAsync() and add parent properties to my Bson document.
Yes, you could do that. EntityChange has a reference to EF's EntityEntry. You can persist the navigation property as EntityPropertyChanges.