Test: lib.backup() takes no new original once onProgress has thrown or its lock is lost

The onProgress test now runs eight photos with a pool of five and holds
only the first five downloads, so a backup that went on after the throw
would download and store the other three. The end-to-end test of a
removed backup.lock expects the backup to stop after its three originals,
before it fetches ML data.

Model: opus-5-5

test/cli/backup-end-to-end.test.ts

@@ -705,9 +705,10 @@ describe("a backup whose lock is lost", () => {
     };
 
     // The backup downloads up to five originals at once, so all three are
-    // under way when the lock is lost, and beach.jpg is stored. `quak backup`
-    // prints why as one line, with no stack trace, and exits 1.
-    it("stops quak backup before its next file when backup.lock is removed, and exits 1", async () => {
+    // under way when the lock is lost, and beach.jpg is stored. The backup
+    // then stops before it fetches ML data. `quak backup` prints why as one
+    // line, with no stack trace, and exits 1.
+    it("stops quak backup before it fetches ML data when backup.lock is removed, and exits 1", async () => {
         const result = backup(dir, {}, fetch);
         await heldRequested;
         rmSync(lockPath, { recursive: true });
@@ -722,7 +723,6 @@ describe("a backup whose lock is lost", () => {
                 "Fetching original beach.jpg (100)...\n" +
                 "Fetching original IMG_0002.HEIC (300)...\n" +
                 "Fetching original toast.mp4 (200)...\n" +
-                "Fetching ML data...\n" +
                 `quak: lost the lock on ${dir}: ENOENT: no such file or directory, stat '${lockPath}'\n`,
         );
         expect(downloads.sort()).toEqual([100, 200, 300]);