offline property
How a write this model made offline is resolved when it is replayed, or
null when it declared no offline: at all.
Null is what keeps the route that applies replayed writes from being an arbitrary-table write primitive: only the models that said so are in its registry, and a spec that defaulted to a strategy would put every model in it.
Here rather than in a registry of its own because the backend cannot import models.g.dart -- that file imports Flutter -- and this spec already carries everything else a remote needs to resolve the table.
Implementation
final DVConflict? offline;