Note

Medium Risk
Changes GitCore.execute behavior to optionally return truncated stdout/stderr (with a [truncated] marker) rather than erroring when output exceeds limits, which could affect downstream consumers that assume full diffs/patches.

Overview
Adds opt-in output truncation to GitCore command execution via truncateOutputAtMaxBytes, capping collected stdout/stderr and appending a \n\n[truncated] marker instead of throwing when maxOutputBytes is exceeded.

Applies per-call byte limits with truncation enabled for prepareCommitContext staged patches and readRangeContext commit/diff summaries and patches, while leaving checkpoint diffs untruncated.

Adds integration tests to verify oversized staged/range patches are truncated (and marked) and that CheckpointStore.diffCheckpoints still returns a full large diff without truncation.

^{Written by Cursor Bugbot for commit 1b1872c. This will update automatically on new commits. Configure here.}

Note

Truncate oversized git diffs instead of failing in GitCore

• collectOutput in GitCore.ts gains a truncateOutputAtMaxBytes option; when enabled, output is capped and suffixed with [truncated] instead of throwing a GitCommandError.
• prepareCommitContext and readRangeContext now use per-field byte limits (49 KB for staged patches, 19–59 KB for range diff fields) with truncation enabled.
• Integration tests in GitCore.test.ts verify that large repos produce truncated output containing [truncated] rather than errors.
• Behavioral Change: commands that previously failed on oversized output now succeed with a truncated result; callers consuming the full diff string may now receive incomplete data.

^{Macroscope summarized 1b1872c.}