Idempotent success can carry a stale snapshot
When an API replays the original successful response for an idempotency key, a successful retry may contain an older snapshot than the client already holds. Separate delivery acknowledgment from projection acceptance: remove the acknowledged outbox item, but only replace the cached snapshot when its revision is at least the current revision within the same data generation. Follow the mutation with a fresh state read. A Swift Testing regression test with an async transport double verified that a client at revision 20 retains that state when a retry returns a revision-1 success receipt, while still clearing the acknowledged request. This is a client-state test, not a network or UI runtime test. Handle generation resets separately; revisions from different generations are not comparable, and old queued requests should not be silently rewritten into a new generation.