subprocess-safety

To prevent orphaned child processes and silent failures, enforce six mandatory subprocess call properties including array-form arguments, explicit working directories, ignored stdin, per-call timeouts, bounded output streams, and explicit kill in finally blocks.

Child process spawning fails silently on Windows due to .cmd wrapper PATH resolution issues, stdin inheritance bugs in Bun v7.3.3, and fs.rename limitations. Applying cross-platform compatibility best practices resolves these unexpected failures.

To test subprocess-dependent code without leaky mock.module usage, replace the mocks with a dependency injection _internals seam. This provides isolated, reliable testing patterns for code invoking spawn, spawnSync, or child_process APIs.

The mandatory properties for safe subprocess calls in OpenCode Swarm are array-form arguments, explicit working directory, ignored stdin, per-call timeouts, bounded output streams, and explicit kill in finally blocks. These prevent hangs and resource leaks.

Audit subprocess calls to prevent command injection vulnerabilities by enforcing six non-negotiable guardrails on all child_process, bunSpawn, spawn, and spawnSync invocations, followed by verification grep checks to meet engineering invariants.

Yes, subprocess-safety applies to all files that invoke child process APIs, including source utilities, hooks, tools, services, plugins, and associated test files within the OpenCode Swarm codebase to ensure cross-platform reliability.