Talos v1.5: Does --verify flag replace manual snapshot status?

Talos v1.5 snapshot restore and verification

Goal: After restoring an etcd snapshot with talosctl, confirm that the recovered data is intact before re‑activating the control plane.

Constraints: In v1.4.x the restore command does not automatically run an integrity check, requiring a separate etcdctl snapshot status invocation. In v1.5 the experimental --verify flag can trigger this check, but its default status and long‑term stability are unclear.

Uncertainty: If the --verify flag is enabled, does it check all critical metadata (hash, version, size) and guarantee the snapshot is usable? Will future releases alter the flag’s semantics or deprecate it?

Questions:

1. In Talos v1.5, does the experimental --verify flag fully replace manual etcdctl snapshot status for integrity verification?
2. Does the --verify flag cover all aspects of snapshot health, such as cluster version compatibility and member consistency?
3. Will upcoming Talos releases modify the behavior or default state of the --verify flag, potentially impacting existing restore scripts?