Greptile Summary

This PR fixes a redundant summarization pass in summarizeWithFallback (src/agents/compaction.ts). When full summarization failed and no messages were marked as oversized, the fallback path would re-attempt summarization against the identical transcript — duplicating all API calls (including retries) and emitting a spurious second warning log. The fix adds a strict-subset check (smallMessages.length !== messages.length) so the partial path only runs when at least one oversized message was actually excluded, preserving the intended fallback behavior for mixed transcripts.

• src/agents/compaction.ts: adds smallMessages.length !== messages.length to the partial-path guard in summarizeWithFallback
• src/agents/compaction.summarize-fallback.test.ts: new test file asserting generateSummary call counts for the no-oversized (3 calls) and mixed-oversized (6 calls) scenarios; the vi.importActual pattern matches the existing convention in compaction.retry.test.ts
• CHANGELOG.md: entry added correctly under the active unreleased block

Confidence Score: 4/5

Safe to merge; the fix is logically correct and well-tested with a minor observability concern

The strict-subset guard correctly prevents duplicate API calls when no messages are oversized. Both the fixed case and the regression case are covered by exact call-count assertions. The only issue is the warning log still says 'trying partial' even in the newly-skipped path, which is a minor inaccuracy in log messaging rather than a correctness bug.

src/agents/compaction.ts lines 400-405 (warning log says 'trying partial' even when partial summarization will be skipped)

This is a comment left during a code review.
Path: src/agents/compaction.ts
Line: 400-405

Comment:
**Misleading log message after guard change**

The warning `"Full summarization failed, trying partial:"` is logged unconditionally in the `catch` block, but partial summarization is no longer always attempted after this fix. When no messages are oversized (`smallMessages.length === messages.length`), the code logs "trying partial" yet immediately falls through to the final fallback without running the partial pass.

Consider dropping the "trying partial" framing from the message so the log stays accurate:

```suggestion
    log.warn(
      `Full summarization failed: ${
        fullError instanceof Error ? fullError.message : String(fullError)
      }`,
    );
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "Agents: skip redundant partial compactio..." | Re-trigger Greptile}

Addressed the current AI review feedback on this PR.

What changed:

• Updated src/agents/compaction.ts so the full-failure warning now logs Full summarization failed: ... instead of claiming it is always "trying partial".
• This keeps the log accurate after the new guard, since we now skip the partial path when smallMessages is identical to the original transcript.

What I verified:

• Re-ran the compaction unit coverage:
  • src/agents/compaction.summarize-fallback.test.ts
  • src/agents/compaction.test.ts
  • src/agents/compaction.retry.test.ts
  • src/agents/compaction.tool-result-details.test.ts
• All 26 tests passed.

Follow-up commit:

• bf663aec32

I did not find any other actionable AI review comments on the PR at the moment.

Landed via temp rebase onto latest main and squash merge.

Scoped verification:

• pnpm test src/agents/compaction.summarize-fallback.test.ts src/agents/compaction.test.ts src/agents/compaction.retry.test.ts src/agents/compaction.tool-result-details.test.ts
• pnpm lint -- src/agents/compaction.ts src/agents/compaction.summarize-fallback.test.ts
• pnpm build

Repo-wide note:

• pnpm check is currently blocked on unrelated latest-main drift in apps/macos/Sources/OpenClaw/HostEnvSecurityPolicy.generated.swift.

• Land branch head: neeravmakwana@69d551d

• Merge commit: 7df5f70

Thanks @neeravmakwana!