opencode-acp 1.14.8-dev.4 → 1.14.8-dev.5

package/README.md

@@ -492,6 +492,15 @@ For the complete list with root cause analysis, see the [bug tracker](https://gi
 
 ## Changelog
 
+### v1.14.8-dev.5 — Dev Prerelease (1 PR since v1.14.8-dev.4)
+
+Dev prerelease covering PR #257. Published to `dev` npm tag for early testing.
+
+**PRs included**:
+- **#257** — Bump `context-compress-algorithms` from 1.2.1 to 1.3.0. cc-alg 1.3.0 ships holistic TIER2/TIER3 compression prompts — summarize by theme instead of per-block. The old per-block format (Source header + 3-5 bullets + 50-150 tokens per block) caused length overflow when compressing 70+ T1 blocks (~30K chars exceeding `maxSummaryLengthHard`). No source code changes needed (prompts consumed from dependency).
+
+**Install**: `opencode plugin opencode-acp@dev --global`
+
 ### v1.14.8-dev.4 — Dev Prerelease (1 PR since v1.14.8-dev.3)
 
 Dev prerelease covering PR #252. Published to `dev` npm tag for early testing.

package/README.zh-CN.md

@@ -446,6 +446,15 @@ ACP 是 DCP 的直接替代品。迁移步骤：
 
 ## 更新日志
 
+### v1.14.8-dev.5 — Dev 预发布（v1.14.8-dev.4 以来 1 个 PR）
+
+Dev 预发布，涵盖 PR #257。发布到 `dev` npm tag 供早期测试。
+
+**包含的 PR**：
+- **#257** — 升级 `context-compress-algorithms` 从 1.2.1 到 1.3.0。cc-alg 1.3.0 提供整体式 TIER2/TIER3 压缩提示——按主题综合而非逐块处理。旧的逐块格式（Source 头 + 每块 3-5 条 + 每块 50-150 tokens）在压缩 70+ 个 T1 块时导致长度溢出（~30K 字符超过 `maxSummaryLengthHard`）。无需源码修改（提示从依赖中获取）。
+
+**安装**: `opencode plugin opencode-acp@dev --global`
+
 ### v1.14.8-dev.4 — Dev 预发布（v1.14.8-dev.3 以来 1 个 PR）
 
 Dev 预发布，涵盖 PR #252。发布到 `dev` npm tag 供早期测试。

package/dist/index.js

@@ -5500,7 +5500,7 @@ function evaluatePreCommitQuality(rawMessages, messageIds, messageTokenById, sum
   }
 }
 
-// node_modules/context-compress-algorithms/dist/chunk-EBKMI537.js
+// node_modules/context-compress-algorithms/dist/chunk-YCHW53QG.js
 var COMPRESS_PHILOSOPHY = `Compression Philosophy:
 - All compression serves the primary task, but be frugal.
 - Context capacity is precious. Save context by compressing consumed outputs, not by avoiding tools.
@@ -5547,7 +5547,7 @@ PRIORITY \u2014 when the summary must be compact, preserve in this order:
 Write dense, scannable bullets \u2014 not narrative prose. If the range spans distinct concerns (request \u2192 findings \u2192 decision), group bullets under short thematic headers so a reader can scan to the part they need. Every line must earn its place. Do not mimic the style of existing summaries in context; follow these rules.`;
 var TIER2_DISTILL_RULES = `TIER 2 COMPRESSION \u2014 DISTILLATION
 
-You are compressing historical summaries (not raw conversation). These summaries have already captured the details. Your job is to DISTILL them: extract only what matters for future work, discard the process.
+You are compressing historical summaries (not raw conversation). These summaries have already captured the details. Your job is to DISTILL them: write a holistic summary of what matters for future work, discarding the process.
 
 KEEP \u2014 these are the only things that survive distillation:
 - Decisions and their rationale ("chose X over Y because Z" \u2014 the "because" is load-bearing).
@@ -5555,9 +5555,9 @@ KEEP \u2014 these are the only things that survive distillation:
 - Key lessons: what failed and why ("tried X, failed because Y"). These prevent repeating mistakes.
 - Critical constraints discovered ("must support Node 22", "AGENTS.md forbids as any").
 - Design decisions with architectural impact ("chose compress-as-anchor over synthetic messages because prefix cache").
-- Whether content is OBSOLETE or SUPERSEDED \u2014 mark with one line: "[SUPERSEDED by PR #NNN]" or "[OBSOLETE: deleted in vX.Y.Z]". Do NOT keep the obsolete content's details \u2014 just the marker and reason.
-- Function/class/type names and module paths that are the SUBJECT of the work \u2014 e.g., "fixed filterCompressedRanges in prune.ts", "added SessionStateRegistry in state.ts". Not exact line numbers or full signatures \u2014 just enough to LOCATE the code without searching.
-- Exploration findings: if a block was exploratory with no decision, keep the CONCLUSION in one line ("explored X, not viable because Y"). Do not keep the exploration process.
+- Whether content is OBSOLETE or SUPERSEDED \u2014 mark with one line: "[SUPERSEDED by PR #NNN]" or "[OBSOLETE: deleted in vX.Y.Z]".
+- Function/class/type names and module paths that are the SUBJECT of the work \u2014 e.g., "fixed filterCompressedRanges in prune.ts". Not exact line numbers or full signatures \u2014 just enough to LOCATE the code.
+- Exploration findings: if a block was exploratory with no decision, keep the CONCLUSION in one line.
 
 DROP \u2014 these were useful during the work but are no longer needed:
 - Exact line numbers, diffs, verbose function signatures, full code listings.
@@ -5566,20 +5566,17 @@ DROP \u2014 these were useful during the work but are no longer needed:
 - Verbose logs, command output, intermediate debugging steps.
 
 FORMAT:
-- Start each distilled block with a source header line:
-  \`Source: bN+bM+... (XK\u2192YK tok, Zx). [original topic]\`
-  Example: \`Source: b5+b7 (56K+44K\u2192268 tok, 375x). [Tool-result recap + publish]\`
-- 3-5 bullet points per source block, each a self-contained fact.
-- Dense, scannable \u2014 no narrative prose.
-- Start with the outcome, not the process: "v1.13.0 shipped (7 PRs bundled)" not "implemented 7 PRs then reviewed then merged".
-- Cross-block synthesis: if multiple source blocks cover the same topic (same PR, same feature, same bug), MERGE them into a single group of bullets. Do not repeat the same fact from different blocks \u2014 keep it once under the most relevant source header.
-
-SIZE TARGET: 50-150 tokens per source block (excluding the header). If you can't fit it in 150 tokens, you're keeping too much process. If a block has nothing worth keeping (pure noise), output just the header followed by "[no actionable content]".`;
+- Write a HOLISTIC summary grouped by THEME, not by source block.
+- NO per-block headers. NO "Source: bN" lines. This is a review of what happened, not a catalog of blocks.
+- Group related work together: all releases in one section, all bug fixes in another, all architecture decisions in a third.
+- Start with the most important outcomes (shipped releases, merged PRs, critical bugs).
+- Dense, scannable bullets \u2014 no narrative prose.
+- Most blocks will collapse into 1-2 bullets within a theme group. Many will have nothing worth keeping \u2014 omit them entirely.`;
 var TIER3_CONDENSE_RULES = `TIER 3 COMPRESSION \u2014 ULTRA-CONDENSATION
 
 You are compressing distilled summaries (Tier 2) into ultra-condensed facts (Tier 3). The distilled summaries already contain only decisions and outcomes. Your job is to reduce them to bare factual references.
 
-PRIORITY \u2014 when a source block has more facts than the size target allows, keep in this order:
+PRIORITY \u2014 keep in this order:
 1. Shipped outcomes (versions released, PRs merged) \u2014 these are permanent record.
 2. Open work (PRs/issues still pending) \u2014 these may need follow-up.
 3. Key decisions with architectural impact ("chose X over Y because Z").
@@ -5587,12 +5584,11 @@ PRIORITY \u2014 when a source block has more facts than the size target allows,
 Drop everything else. Tier 3 is a lookup index, not a knowledge base.
 
 FORMAT:
-- Start with a source header line:
-  \`Source: bN+bM+... (XK\u2192YK tok, Zx). [original topic]\`
-- Output 1-3 facts per source block. Each fact is a single line: subject + outcome.
+- Write a HOLISTIC list of bare facts, grouped by theme \u2014 not by source block.
+- NO per-block headers. NO "Source: bN" lines.
+- Each fact is a single line: "[PR/Issue/Version] \u2014 [outcome in \u22648 words]"
+- Merge related facts aggressively. If multiple blocks concern the same release/feature/bug, output ONE line covering all of them.
 - No explanations, no rationale, no process \u2014 just the fact.
-- Format: "[PR/Issue/Version] \u2014 [outcome in \u22648 words]"
-- Merge related facts from different source blocks if they concern the same topic.
 
 EXAMPLES:
 - "v1.13.0 shipped \u2014 quality gate + GC fix (7 PRs)"
@@ -5605,9 +5601,7 @@ DROP:
 - Multi-sentence context. If a fact needs >1 sentence, it's too detailed for Tier 3.
 - Lessons learned ("tried X, failed because Y") \u2014 drop UNLESS the failure is likely to recur and the block is <30 days old.
 - Design rationale details \u2014 keep the decision, drop the "because" unless it's a critical constraint.
-- Anything marked [OBSOLETE] or [SUPERSEDED] \u2014 drop entirely, note "[N blocks obsolete]" in the summary.
-
-SIZE TARGET: 30-60 tokens per source block (including header). For a batch of N source blocks, total output \u2248 N \xD7 40 tokens. If a source block has only one trivial fact, output just the header + one line.`;
+- Anything marked [OBSOLETE] or [SUPERSEDED] \u2014 drop entirely, note "[N blocks obsolete]" at the end.`;
 
 // lib/compress/quality-gate/rejection.ts
 function formatMetric(result, name) {
@@ -8836,7 +8830,7 @@ import { writeFile as writeFile2, mkdir as mkdir2 } from "fs/promises";
 import { join as join3 } from "path";
 import { existsSync as existsSync3 } from "fs";
 import { homedir as homedir3 } from "os";
-var LOG_VERSION = true ? "1.14.8-dev.4" : "dev";
+var LOG_VERSION = true ? "1.14.8-dev.5" : "dev";
 var Logger = class {
   logDir;
   enabled;