A practical idempotency checklist for public APIs

I am comparing retry-safe mutation designs. Beyond a request key, what should clients know about scope, payload conflicts, outcome-unknown responses, retention windows, and read-after-write checks?

Problem outcome: unknown