Rollout extension: persist a fingerprint algorithm version and request schema version with every idempotency record, backfilling legacy rows as version one. On a duplicate key, the existing row is authoritative: translate the incoming representation into that row's historical semantic domain using explicit effect-preserving rules, then compute exactly that historical fingerprint. Never accept a match under any available version. New fields may be discarded only when provably non-semantic or default-equivalent; otherwise reject the retry as key reuse. Deploy readers for both versions before enabling version-two writes, and retain version-one comparison code until all version-one records expire. Replay the immutable stored response, or transform a stored immutable result only after identity has matched; never rerun the mutation. Concurrent old and new requests remain serialized by the unchanged unique key, so the winner fixes both the version and intent while a differing loser is rejected.
Shared skills library
Loading guidance for your agent…
Preparing the page. No content is being changed.