fix(cp): prevent WriteStream error handler from orphaning subsequent file's stream

When a WriteStream error fires asynchronously after we've moved on to processing
the next file, only nullify currentFile if it still points to the errored stream.
This prevents a race condition where a late-firing error could orphan the new file's stream.

Author: rgarcia

src/lib/cp.ts

@@ -428,10 +428,15 @@ export async function cpFromInstance(cfg: CpConfig, opts: CpFromInstanceOptions)
                 fs.mkdirSync(path.dirname(targetPath), { recursive: true });
                 currentFile = fs.createWriteStream(targetPath, { mode: currentHeader.mode });
                 // Add error handler to prevent unhandled 'error' events from crashing
+                // Capture reference to avoid race condition if error fires after we've moved to next file
                 const fileBeingWritten = currentFile;
                 currentFile.on('error', (err) => {
                   fileBeingWritten.destroy();
-                  currentFile = null;
+                  // Only nullify currentFile if it's still pointing to this stream
+                  // This prevents orphaning a subsequent file's stream if this error fires late
+                  if (currentFile === fileBeingWritten) {
+                    currentFile = null;
+                  }
                   doReject(new Error(`Failed to write file ${targetPath}: ${err.message}`));
                   ws.close();
                 });