fix(packages): correct spawn result access in package build scripts

Fix incorrect spawn result property access in package-specific build scripts.
Changed result.exitCode and result.status to result.code.

Files fixed:
- packages/node-sea-builder/scripts/build.mjs (result.exitCode → result.code)
- packages/cli/scripts/wasm.mjs (result.status → result.code)
- packages/minilm-builder/scripts/build.mjs (result.status → result.code)

The @socketsecurity/lib/spawn function returns {code, stdout?, stderr?}.
Using incorrect property names resulted in undefined checks and broken builds.

Author: jdalton

packages/cli/scripts/wasm.mjs

@@ -115,12 +115,12 @@ async function exec(command, args, options = {}) {
     ...options,
   })
 
-  if (result.status !== 0) {
-    throw new Error(`Command failed with exit code ${result.status}`)
+  if (result.code !== 0) {
+    throw new Error(`Command failed with exit code ${result.code}`)
   }
 
   return {
-    code: result.status ?? 0,
+    code: result.code ?? 0,
     stderr: result.stderr ?? '',
     stdout: result.stdout ?? '',
   }

packages/minilm-builder/scripts/build.mjs

@@ -312,8 +312,8 @@ async function runPythonScript(scriptName, args, options = {}) {
         throw new Error(result.error)
       }
 
-      if (result.status && result.status !== 'complete') {
-        printStep(`  ${result.status.replace(/_/g, ' ')}...`)
+      if (result.code && result.code !== 'complete') {
+        printStep(`  ${result.code.replace(/_/g, ' ')}...`)
       }
     } catch (e) {
       if (e.message.startsWith('{')) {

packages/node-sea-builder/scripts/build.mjs

@@ -325,9 +325,9 @@ async function buildSeaBlob(nodeBinary, configPath) {
     result &&
     typeof result === 'object' &&
     'exitCode' in result &&
-    result.exitCode !== 0
+    result.code !== 0
   ) {
-    throw new Error(`Failed to generate SEA blob: exit code ${result.exitCode}`)
+    throw new Error(`Failed to generate SEA blob: exit code ${result.code}`)
   }
 
   return blobPath