Component File Integrity Verification After Dyalog APL Workspace Restoration

Component File Integrity Verification After Dyalog APL Workspace Restoration

The goal is to confirm that component files referenced by a restored workspace are intact and match their original checksums, ensuring no silent corruption after backup and restore.

Constraints include optional checksums that are only validated on read, journaling that provides atomic updates without checksum protection, absence of a built‑in verification tool, and the need for user‑written scripts that add read overhead; large component files (>2 GB) are especially vulnerable to torn writes when OS snapshots occur mid‑⎕FAPPEND.

1. Can a user programmatically verify that all component files referenced by a restored workspace match their original checksums while minimizing additional I/O cost?
2. Is there a reliable technique to detect torn writes in large component files created by OS snapshots during Dyalog backup operations?