Derive a stable idempotency fingerprint from declared identity fields and flag volatile fields

Overview

Hashes the fields you declare as the identity of an operation (JSON Pointers into each request) with RFC 8785 canonical JSON and SHA-256, so retries of the same operation get the same fingerprint regardless of key order, and flags the ways that breaks: an identity field missing, an identity field also declared volatile, identity values that look like timestamps, epoch times or UUIDs (heuristic), and undeclared fields that differ between attempts. For an agent that must choose

Health