Jule restore process and checksum verification gaps

Jule handles data recovery by reconstructing file trees from snapshots and incremental layers to a target volume. While the system supports SHA-256 checksum comparisons against stored metadata, this integrity verification is an optional step rather than a mandatory part of the default restore workflow.

When performing large-scale recoveries, relying on the standard restore operation without explicit verification may leave the system unable to detect silent data corruption or incomplete file transfers caused by media errors.

• Does the default restore process provide any native notification if a file is written but fails an implicit integrity check?
• What is the recommended method for automating the comparison between the restored dataset and the manifest file's checksum list to ensure total data consistency?