Repository navigation
chore: pin acp-kernel 0.0.96 — reid (#1476), strict placeholder parser (#1456), raw re-projection (#1460) - #1488
ranxianglei wants to merge 1 commit into
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.1413-pr.1488.686862dThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr1488.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 Verdict: HOLD — do not merge. The pin head is red on CI where master is green, and I've root-caused it to a pipeline-contract break in kernel 0.0.96's new Checks that pass
Checks that fail: CI on head e84a743 is red
Root cause (A/B verified against both published tarballs)
The new node (
Where the fix belongs I've filed the kernel-side finding as ranxianglei/acp-kernel#461 (来源 marker included) with the minimal repro. Side note: the #1456 thread promised a host-side follow-up — tighten Per policy this is a cross-repo dependency bump — human-gated regardless; I won't merge. 中文摘要:0.0.96 新增的 remintCoveredLiveIds 把「客户端重放已被折叠的原始消息」误判为「新重复消息」,导致折叠后每轮原始内容重回线上(压缩失效)、摘要载体(锚点与 compress tool call)双双丢失、preflight 引用失配触发 502 死循环——master 全绿而本 PR 红(56 个单测 + codex e2e),根因在 kernel 侧,建议先在 acp-kernel 修出 0.0.97(已立 acp-kernel#461)再重新 pin,本 PR 先挂起、不要合并。 |
|
Superseded by #1505 (pin 0.0.97 = 0.0.96 payload + the kernel #463 fix for the #459 post-fold echo regression that this PR's CI caught). Do not merge this — 0.0.96 pins the regression in. Closing in favor of #1505, which is verified green (CI 13/13; locally: typecheck 0, ccr-plugin 12/12 with the post-#458 resend assertions, wire-contract/cache-ledger/issue1307 31/31, and the e2e-codex-fake overflow sentinel — the test that caught the regression — passes on published npm 0.0.97). |
Bumps the pinned
acp-kernelfrom 0.0.95 to 0.0.96 (npm latest, published 2026-09-27T10:46Z), picking up the three kernel fixes that landed since 0.0.95:What rides in 0.0.96
remintCoveredLiveIds— live resend of already-covered content gets deterministic_Ninstance suffixes instead of colliding with the folded copy's ref (assignRefsfirst-wins starved the new instance)parseStoredPlaceholder()strict whole-body parser — ordinary text merely mentioning[acp-storedis no longer misclassified as a canonical placeholder; all three call sites (storeLargeResults,storeCoveredOriginals, absorb candidates) now require the exact two-line canonical shape citing the message's own refcommand) instead of leaking multi-MB raw back to the wireThe two fixes interlock at
storeLargeResults: placeholder echo → 457's own-ref gate returns it unchanged; raw replay → falls through to 458's re-projection.Validation
tsconfig.build.jsontypecheck: 0 errors against the real 0.0.96 npm tarballnode --import tsx scripts/update-wire-contract-goldens.ts: byte-identical (no schema drift — the new kernel exports are not on bili's contract surfaces)Fixes #1456
Refs #1460 (design issue — the working-set half remains open), refs #1476 (closed at kernel merge; this pin delivers the fix to bili users)