A data-integrity fix for scans interrupted by a restart.
Fixed
- A scan interrupted by a restart is no longer recorded as "completed" (#343). When the app was restarted while a parallel scan was running, the scan could be marked
completedat partial progress instead ofinterrupted- so it never resumed on the next start, and the rest of the library was silently left unscanned (observed: a 31,118-file scan recorded complete at file 3,514). The cause was a gap in the parallel scanner: the dispatch loop spends most of its time waiting for a free worker, and a shutdown that arrived during that wait stopped the scan without recording why, after which finalization defaulted it to "completed" - overwriting the resumable state the shutdown had already saved. The scanner now records the correct reason from every stop path, and finalization will never mark a still-running scan complete: an interrupted scan stays interrupted (and resumes), a cancelled one stays cancelled. Only the parallel scan path was affected; serial scans already recorded the correct status.
Full Changelog: v1.3.15...v1.3.16