v0.4.4

Fixed

• Clone no longer overwrites the end of the cloned data on a larger target — the "clear the target's old end-of-disk GPT area" step introduced in v0.4.3 zeroed the last 1 MiB of the target. When the target was less than 1 MiB larger than the source, that range reached back into the freshly cloned data and wiped the clone's own backup GPT header. The cleared range now starts at max(target.size − 1 MiB, source.size) (rounded up to a sector), and the step is skipped entirely when there is nothing beyond the source's size to clear.
• Identity check no longer rejects disks without a friendly name — the pre-operation identity check (added in v0.4.3 for backup/clone sources) compared the live FriendlyName against the name shown in the list. Disks that report no name are displayed with a placeholder, so the comparison always failed and those disks could not be backed up or cloned. The name is now only compared when the disk actually has one; size and serial are still checked.

Full Changelog: v0.4.3...v0.4.4