v1.55.0

Fixed

• Config backups could be stored incomplete while looking perfectly normal. When a pooled SSH connection was recycled while an export was still being read, the export was cut short and the partial result was saved as an ordinary backup — correct device, plausible size, no error shown. Restoring from such a backup would have replayed only part of the config. Exports are now verified before they are stored: a read that ends early fails the backup instead of saving it, and a connection is never recycled while it is still being read from. Found during internal testing; no user reported it.

Added

• Backup completeness checks. Backups taken before this release are checked when you upgrade. Any that do not contain a whole config are marked incomplete in the backups list, with a warning when you open one. Re-run the backup for that device to replace it. Devices on slow or unstable links were the most affected — they are the ones worth reviewing first.