Local edits, saving and reconnect

Status: planned integration contract. See release status before assuming an API or service is available.

An accepted edit, a durable local save and a remote durable receipt are different states. Show them separately in your application. Network delivery alone does not mean a server has persisted an update.

A cached or new local document can become editable before network connection. An uncached remote document still needs to be retrieved. A browser store is subject to the host browser's persistence and eviction behavior; provide exports and recovery appropriate to your product.

Persist the update journal and outbox under the session's storage contract. When persistence fails after an in-memory commit, keep recovery data and expose the failure. The shared session freezes dependent writes and outbound publication until ordered recovery succeeds. Keep reading and clearly labeled recovery export available.

On reconnect, recheck authorization and exchange retained updates. Rejected uploads must not erase recoverable local work. Sharing a database between tabs or processes does not itself deliver live updates to each view.

For contract details, see storage and sync and shared clients.