on the entity scheduler state: since we are maintaining the invariant (entity exists) <=> (serialized state is not null) there is no reason for defining (and serializing/deserializing) an entityExists field. Instead, just use a property.
in client entity helpers, provide access to helper functions so external code can deserialize strings that represent EntityStatus and SchedulerState without us having to make the serialization format public. This is needed by backends that provide entity query functionality directly.
also provide a shortcut (optimized) way to determine if an entity exists when looking at the entity status. Again, this is useful for backends implementing queries.
Three changes here:
entityExistsfield. Instead, just use a property.EntityStatusandSchedulerStatewithout us having to make the serialization format public. This is needed by backends that provide entity query functionality directly.