Skip to content

chore(deps): bump ctxzip to v0.4.1 - #465

Closed
initializ-mk wants to merge 1 commit into
mainfrom
chore/bump-ctxzip-v0.4.1
Closed

initializ-mk wants to merge 1 commit into
mainfrom
chore/bump-ctxzip-v0.4.1

Conversation

@initializ-mk

Copy link
Copy Markdown
Contributor

Bumps github.com/initializ/ctxzip v0.3.0 → v0.4.1 in forge-core.

Why

v0.4.1 tightens the compressor's error-keep heuristic. Previously looksError was a bare substring match, so any content merely mentioning "error"/"fail" — Go error return types, log lines like "0 errors" — was pinned and never compressed. The JSON crusher now keeps only structural errors (log levels, stack traces, structured level fields) and routes the rest through an adaptive scored keep-budget, so repetitive/structured tool output compresses instead of being over-kept. Genuine error rows still survive verbatim, and every drop stays reversible via CCR.

Who this affects

The committed ctxzip consumers get the improved crushers:

  • forge-core/compress — the agent's context compression
  • the markdown channel converter (forge-plugins/channels/markdown)

Impact (offline crusher benchmark, v0.4.0 → v0.4.1)

payload before after
json-logs (1 FATAL) 73.9% 97.6%
search-results 0.0% 97.4%

FATAL/error rows are preserved in both.

Scope

Dependency bump only (forge-core/go.mod + go.sum). forge-core builds and ./compress/... tests pass on v0.4.1.

v0.4.1 tightens the compressor's error-keep heuristic. The prior `looksError`
was a bare substring match, so any content mentioning "error"/"fail" (Go `error`
return types, log lines like "0 errors") was pinned and never compressed. The
JSON crusher now keeps only structural errors (log levels, stack traces,
structured level fields) and routes the rest through an adaptive scored
keep-budget, so repetitive/structured tool output compresses instead of being
over-kept. Real error rows still survive verbatim; drops remain reversible.

Upgrades the committed ctxzip consumers: forge-core/compress (agent context
compression) and the markdown channel converter.

Offline crusher benchmark (v0.4.0 -> v0.4.1):
  json-logs (1 FATAL):  73.9% -> 97.6%
  search-results:        0.0% -> 97.4%
@initializ-mk

Copy link
Copy Markdown
Contributor Author

Superseded by #466, which includes this same ctxzip v0.3.0 → v0.4.1 bump alongside the optimizer engine + CLI that consume it. Closing in favor of #466.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant