Deleting a source after a successful upload first renames it to
.<name>.mhu-delete-<uuid> and then unlinks it. On a slow disk the unlink
can take several seconds. With an empty extension filter the folder
watcher and the reconcile scan reported the staged file as a new file,
so the automation queued and uploaded it again until the unlink removed
it. The jobs for the vanished staged file were then restarted by every
automatic start and skipped with "Datei nicht gefunden".
- source-cleanup-policy: shared stagedSourceName/isStagedSourceFile.
- folder-monitor and file-discovery skip staged delete files.
- Automatic starts no longer restart queue jobs that point at a staged
delete file; manual starts are unchanged.
- An ENOENT while unlinking the staged file counts as deleted instead of
a failed unlink with a restore attempt. EBUSY/EPERM keep their retries
and stay visible as failures.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Verify update artifacts with exact metadata and SHA-512, require host-confirmed upload completion before cleanup, harden credentials and backups, improve queue recovery and skipped-state reporting, expand Windows path coverage, and add CI packaging checks.