Persist and retry mutations

Is there a plan to support retrying mutations (and persisting them) accross session like React Query does? This would be very useful when we need to mutate backend data but are offline.

No files, tests, or entry points are named. Start by tracing the package's mutation and cache-persistence entry points, then compare the desired offline behavior with React Query's persisted mutation retries. Done means the scope and expected behavior for retrying backend mutations across sessions are defined and implemented.

Written by the indexing model from the issue text.