Workers KV read‑after‑write consistency limits in production vs Wrangler dev

Goal

Determine how quickly a write to Workers KV becomes visible to subsequent reads served from a different Cloudflare edge location, and how this differs from the local development environment provided by wrangler dev.

Constraints & Uncertainty

• Workers KV is documented as eventually consistent; a write may not be immediately visible across all edge locations.
• Local development persists KV in a SQLite‑backed store that behaves as strongly consistent, masking any propagation delays that occur in production.
• Cloudflare does not publish a hard deadline for read‑after‑write synchronization or a uniform propagation window.

Specific Questions

1. What is the maximum time a KV write can take to propagate to all edge locations before a read from a different location returns the updated value?
2. Does Cloudflare guarantee any read‑after‑write consistency for Workers KV across regions, or is it purely eventual?
3. In what ways does the local KV store used by wrangler dev differ from the production KV store regarding consistency guarantees and replication behavior?