Reject scan --workers below 1 as a usage error (closes #10)

A --workers value of 0 or less used to be quietly raised to 1, so a typo ran the whole scan on one worker with nothing on stderr to say why. scan now refuses it before anything is scanned: one line on stderr and exit 2, like the other usage errors. The clamp in runScan is gone, and README states the rule and the default. Model: opus-5-5
2026-10-04 14:30:21 +02:00
parent 7278c354f0
commit c9c8b1d06c
5 changed files with 69 additions and 10 deletions
@@ -29,6 +29,10 @@

 # Completed Steps

+- `scan` rejects `--workers` below 1 as a usage error instead of
+  running single-threaded (2026-10-04,
+  https://git.eeqj.de/sneak/sfdupes/issues/10)
+
 - a test fails when either walk cancellation check in `scan.go` is
  removed (2026-10-04, https://git.eeqj.de/sneak/sfdupes/issues/81)