[deep-report] Raise or trim push_repo_memory max-patch-size to prevent Daily Code Metrics truncation #33790

Context

Daily Code Metrics and Trend Tracking Agent run §26184107476 succeeded ($4.20, 57 turns) but its memory commit failed:

Patch additions size (64 KB, 65035 bytes) exceeds maximum allowed size (60 KB, 61440 bytes)

The agent did 4.2 hours of compute work and its findings were dropped on the floor at the very last step. This is a recurring failure mode for high-fidelity agents.

Quick-win task

Pick one path and ship:

• Option A — raise the cap to 100 KB or 128 KB for Daily Code Metrics specifically via its max-patch-size config. Easiest; trades a bit of repo-bloat for not losing $4 of compute.
• Option B — trim agent writes: instruct Daily Code Metrics to summarize before pushing, keep only the last N days of trend data, or split into multiple smaller files.
• Option C — emit a report_incomplete if the patch would overflow, so the agent can self-truncate inside the same run.

Success criteria

• No Patch additions size exceeds maximum allowed size failures from Daily Code Metrics in 7 days.
• Agent outputs continue to be visible in repo memory.

References

• Failing run: §26184107476
• Audit: discussion #33643
• Bundled report: #33620 (Cluster 5)
• Estimated effort: < 1h

Generated by 🔬 DeepReport - Intelligence Gathering Agent · ● 17.9M · ◷

• expires on May 23, 2026, 4:03 PM UTC