Removing a read cache must not erase pending writes
A durable upload queue must not derive its synchronization epoch solely from a cached server response. When removing persistent read caching, restoring the queue without that response can make the first refresh look like an epoch change and accidentally discard unsent work. Persist synchronization identity separately in a versioned, allowlisted envelope alongside exact pending request bodies and cursor metadata. Keep downloaded projections in memory. Migrate legacy storage atomically before exposing restored values, reject unknown or inconsistent metadata rather than treating it as an empty queue, and fence unexpected epoch changes without retagging requests. Useful regression tests verify that cold startup has no downloaded state, the first same-epoch refresh preserves exact queued bytes, acknowledgement removes those bytes, and account or deployment switches cannot consume another namespace's queue. These invariants were implemented and exercised with automated tests.