chore(execution): remove verbose comments from isolated-vm changes

Author: waleedlatif1

apps/sim/lib/execution/isolated-vm-worker.cjs

@@ -142,10 +142,6 @@ async function executeCode(request) {
     stdoutTruncated = true
   }
 
-  // Hoist all ivm handle declarations so finally can release them deterministically.
-  // Per isolated-vm upstream issues #198 and #377: child handles (scripts, callbacks,
-  // references, external copies) must be released before isolate.dispose() to avoid
-  // stuck-GC states and native memory leaks outside the V8 heap.
   let context = null
   let bootstrapScript = null
   let userScript = null
@@ -376,10 +372,6 @@ async function executeCode(request) {
       },
     }
   } finally {
-    // Release child handles first (scripts, callbacks, references, external copies),
-    // then dispose the isolate. Order matters: disposing the isolate while child
-    // handles still exist can cause stuck-GC states (isolated-vm issue #198).
-    // .release() is idempotent — safe to call even if the object was never assigned.
     const releaseables = [
       userScript,
       bootstrapScript,

apps/sim/lib/execution/isolated-vm.ts

@@ -727,9 +727,7 @@ function spawnWorker(): Promise<WorkerInfo> {
 
     import('node:child_process')
       .then(({ spawn }) => {
-        // isolated-vm v6 requires --no-node-snapshot on Node.js 20+.
-        // Without it, Node's shared V8 snapshot heap is incompatible with isolated-vm
-        // and causes SIGSEGV on worker startup (isolated-vm issue #377).
+        // Required for isolated-vm on Node.js 20+ (issue #377)
         const proc = spawn('node', ['--no-node-snapshot', workerPath], {
           stdio: ['ignore', 'pipe', 'pipe', 'ipc'],
           serialization: 'json',
@@ -839,10 +837,6 @@ async function acquireWorker(): Promise<WorkerInfo | null> {
   const existing = selectWorker()
   if (existing) return existing
 
-  // Count only non-retiring workers toward pool occupancy so that a replacement
-  // can be spawned pre-emptively while a retiring worker is still draining its
-  // in-flight executions.  Retiring workers stay in `workers` until they drain,
-  // but they no longer accept new work, so they shouldn't block new spawns.
   const activeWorkerCount = [...workers.values()].filter((w) => !w.retiring).length
   const currentPoolSize = activeWorkerCount + spawnInProgress
   if (currentPoolSize < POOL_SIZE) {