Compare a baseline file manifest with a revised delivery list and expose changed, added or removed files before an old proof or approval is trusted against a new export.
Use JSON exported from Print File Delivery Manifest. SHA-256 is used when both versions contain it; otherwise the comparison falls back to file size and raster dimensions and labels that evidence accordingly.
The diff keeps filenames and content identity separate.
When both manifests contain SHA-256, matching hashes are strong evidence that the file bytes match. A renamed file with the same hash is still reported under its filename because this diff is organized around delivery identity.
Equal byte count and dimensions do not prove identical content. The tool labels metadata-only matches so they are not mistaken for cryptographic identity.
A changed, added or removed delivery file should trigger review of the associated preflight, proof and approval evidence even when the revision was intentional.