Saved data changes appear on the next read

Updating or deleting a data entity could report success just before the portal's shared read view had processed the same change. An immediate follow-up read could therefore return the previous value or briefly return an item that had just been deleted.

Data-entity update and delete responses now wait for their matching change to reach that read view. Once the operation reports success, the next read no longer replays the state from before the operation. File-provider operations keep their existing provider-specific completion semantics.