fix: use exit event instead of close to resolve process hang with background jobs

The cross-spawn spawner relied on the 'close' event to mark a process as
complete. In Node.js, 'close' fires only after all stdio streams are closed.
When a shell spawns a background child (e.g., 'cmd &'), the child inherits
stdout/stderr pipe descriptors, keeping the streams open even after the shell
exits. This caused the 'close' event to never fire, making the bash tool hang
indefinitely.

Switching to the 'exit' event resolves this — it fires as soon as the
process terminates, regardless of inherited pipe descriptors.

opencode-cli

@@ -0,0 +1 @@
+Subproject commit 224b297604143373d680621ac4e9cb0def609be6

packages/opencode/src/effect/cross-spawn-spawner.ts

@@ -272,12 +272,10 @@ export const make = Effect.gen(function* () {
         resume(Effect.fail(toPlatformError("spawn", err, command)))
       })
       proc.on("exit", (...args) => {
-        exit = args
-      })
-      proc.on("close", (...args) => {
         if (end) return
         end = true
-        Deferred.doneUnsafe(signal, Exit.succeed(exit ?? args))
+        exit = args
+        Deferred.doneUnsafe(signal, Exit.succeed(exit))
       })
       proc.on("spawn", () => {
         resume(Effect.succeed([proc, signal]))