Skip to content

fix: bump acp-kernel 0.0.74 → 0.0.77 (hold acp_cache off wire until adoption) - #915

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-17_bump-acp-kernel-0.0.77
Sep 17, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-17_bump-acp-kernel-0.0.77

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

What

Bump the acp-kernel pin 0.0.74 → 0.0.77 and keep the kernel's new acp_cache tool off every wire surface until adoption lands (#800). Part of #772 (v0.1.118 release prep).

Changelog — what ships with this bump

Kernel releases pulled in

version content
0.0.75 Cache-reconciliation core: acp_cache tool + buildCacheReport (acp-kernel#297); recommend never emits sub-threshold tail batches (acp-kernel#313); fold-economics exports for streaming hosts
0.0.76 Native Google/Gemini wire codec (acp-kernel#318); recommend range integrity (acp-kernel#320)
0.0.77 Nudge ranges ordered/merged by position, not ref number (acp-kernel#324 — fixes #887)

Host-side adaptation (this PR)

  • acp_cache suppressed on every wire surface. Kernel ≥0.0.75 advertises a fifth proxy tool, but this proxy has no execution path for it — an intercepted call fell through executeProxyTool into the unknown-tool branch, which reports SUCCESS with [Unknown proxy tool: acp_cache]: a plausible-looking result that did nothing (§7.3 honest output). Adoption is feature work under 给出缓存精确对账,增加新的命令/acp-开头 #800 (owner decision pending) and deliberately not bundled here.
  • Suppression lives at the single choke point (src/compress-tool.ts): PROXY_TOOL_NAMES and the four BILI_ACP_TOOLS_* arrays are now derived from the kernel constants minus UNADOPTED_KERNEL_TOOLS ({acp_cache}). Every serving surface consumes those derived arrays — Responses/OpenAI/Anthropic injection, plugin manifest + allowed list, absorb gate, Responses-adapter classification — so no call-site changes. MUTATING_PROXY_TOOLS/READONLY_PROXY_TOOLS stay raw re-exports (classification sets only; nothing serving reads them).
  • Plugin manifest (src/plugin.ts) now serves the BILI arrays; output stays byte-identical except acp_cache disappears (the conversation_id param normalization makes the BILI search_context schema identical to the kernel's).
  • CHANGELOG.md: Unreleased entry added.

Tests

  • feat: 支持 search_context 显式查询历史 session #841 parity test extended: the "no other tool may change" contract now compares against the FILTERED kernel side only — asymmetric on purpose, so a future BILI-side leak of an unadopted tool still fails.
  • No changes needed to plugin-protocol / launcher-plugin-mode expectations (they already hardcode the adopted tool set).
  • Local: typecheck clean; the four affected suites green (codex-official, launcher-plugin-mode, plugin-protocol, search-context-cross-session — 31/31). Full suite runs in CI.

Notes

@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-17_bump-acp-kernel-0.0.77 (cdda2ea)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-915

Each push to this PR publishes a new version under the pr-915 npm tag.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr915.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei
ranxianglei merged commit 55dbc39 into master Sep 17, 2026
8 checks passed
@ranxianglei
ranxianglei deleted the 2026-09-17_bump-acp-kernel-0.0.77 branch October 15, 2026 05:32
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.

[Bug] 消息引用编号与当前顺序不一致时,compress 范围提示会选错消息,导致“内容不足”失败

1 participant