Can a purely static Jamstack client safely retry a serverless write without duplicating the mutation?
In a Jamstack build, write operations are typically delegated to serverless functions or third-party APIs rather than the static host itself. When a browser times out waiting for a response, the endpoint may have already committed the write, so a naive retry can duplicate the effect unless the receiving service enforces idempotency. Idempotency keys are a do