Summary

Migrates packages/opencode/src/git/index.ts to use AppProcess.run (added in #27178) for its run helper. The file-local spawn-collect-truncate boilerplate is replaced by a single call.

Stacked on top of #27178 (effect/app-process-service).

Collapsed helpers

The file-local run Effect.fn in packages/opencode/src/git/index.ts previously contained:

• ChildProcessSpawner.spawn(...) plus scope management
• A local collect helper wrapping Stream.runFold with maxOutputBytes truncation accounting (chunk slicing, bytes/truncated accumulator)
• Effect.all([collect(stdout), collect(stderr)], { concurrency: 2 })
• A yield* handle.exitCode and manual Result assembly
• Effect.scoped wrapping

All of that now lives in AppProcess.run. The git wrapper now just calls appProcess.run(...) and re-shapes the result to preserve the Result contract (which includes the text() accessor used by other methods in this file).

Lines

packages/opencode/src/git/index.ts: 365 -> 350 lines (-15). The diff is +23 / -38 net inside the run body; the bulk of the file (every other git method) is untouched.

Behavior preservation notes

• Return shape. Every git method in this file calls run and reads .text(), .stdout, .stderr, .exitCode, and .truncated. All of those are preserved exactly. The text() accessor still computes from stdout lazily.

• Truncation. Today's code reported truncated = stdout.truncated || stderr.truncated. AppProcess.run only tracks truncation on stdout (stderr is unbounded for diagnostics), so the new result.truncated is just stdout truncation. In practice stderr never hit the limit here — the only callers that pass maxOutputBytes (patch, patchAll, patchUntracked, statUntracked) care about stdout (the diff/numstat output), not stderr.

• Exit-code semantics. Git frequently returns non-zero exit codes that are not errors from this code's perspective: git symbolic-ref --quiet returns non-zero when there's no symbolic ref, git rev-parse --verify HEAD returns non-zero on an empty repo, git merge-base returns non-zero when there is no merge base, git show ref:file returns non-zero for missing files, git diff --no-index returns 1 to mean "files differ", etc. Every caller in this file inspects result.exitCode !== 0 to branch.

  To preserve this, the wrapper passes interpretExitCode: () => "success" so AppProcess.run never converts a non-zero exit code into an AppProcessError. All exit-code interpretation stays where it is today — in the individual git methods.

• Failure handling. The original run wrapped its body in Effect.catch((err) => Effect.succeed(fail(err))), returning a synthetic Result (exitCode 1, empty stdout, error message in stderr) instead of failing. The new code keeps the exact same Effect.catch(...) => fail(err) wrapper around the appProcess.run call, so spawn failures and any other internal errors still degrade to the same synthetic Result and the public method signatures remain Effect.Effect<...> with no error channel.

• Layer chain. Switched from Layer.provide(CrossSpawnSpawner.defaultLayer) to Layer.provide(AppProcess.defaultLayer) (which already bundles CrossSpawnSpawner.defaultLayer).

interpretExitCode

No git command needed a custom interpretExitCode mapping (e.g. exit-1-as-no-match). The blanket () => "success" is correct because every caller in this file is already responsible for its own exit-code branching, and the previous implementation never failed the Effect on non-zero exit either.

Test plan

• bun run typecheck from packages/opencode (clean)
• bun run test test/git/ (9 pass, 0 fail)
• CI