fix: use explicit pyodide.loadPackage() instead of packages parameter

The packages parameter in loadPyodide() appears unreliable in CI environments.
Instead, load Pyodide first, then explicitly load packages using
pyodide.loadPackage() to ensure they're actually available.

Author: rgbkrk

packages/pyodide-runtime-agent/src/pyodide-worker.ts

@@ -81,10 +81,9 @@ async function initializePyodide(
     data: `Using cache directory: ${packageCacheDir}`,
   });
 
-  // Load Pyodide with packages in parallel for faster initialization
+  // Load Pyodide first without packages (more reliable in CI)
   pyodide = await loadPyodide({
     packageCacheDir,
-    packages: packagesForInit, // Load packages in parallel with Pyodide initialization
     stdout: (text: string) => {
       self.postMessage({
         type: "stream_output",
@@ -99,17 +98,25 @@ async function initializePyodide(
     },
   });
 
+  // Explicitly load packages after Pyodide is initialized
+  self.postMessage({
+    type: "log",
+    data: `Explicitly loading packages: ${packagesForInit.join(", ")}`,
+  });
+
+  await pyodide.loadPackage(packagesForInit);
+
   // Set up interrupt buffer
   if (interruptBuffer) {
     const interruptView = new Int32Array(interruptBuffer);
     pyodide.setInterruptBuffer(interruptView);
     self.postMessage({ type: "log", data: "Interrupt buffer configured" });
   }
 
-  // Packages are already loaded in parallel during Pyodide initialization
+  // Packages have been explicitly loaded after Pyodide initialization
   self.postMessage({
     type: "log",
-    data: `Packages loaded in parallel: ${packagesForInit.join(", ")}`,
+    data: `Packages loaded successfully: ${packagesForInit.join(", ")}`,
   });
 
   // Load our Python bootstrap file