Repository navigation
fix: pin acp-kernel 0.0.86 — count-triggered distillation default-off (#379) - #1260
Merged
Merged
Conversation
…#379) Bundles kernel #379/#380: tiers.tier2Trigger 5->1000 / tier3Trigger 10->2000 and the #238 usage gate deleted. Count-triggered distillations reclaimed almost nothing while rewriting the wire from the fold anchor onward — the prefix-cache sawtooth root cause of #1249. Growth (>=growthFloor) and token-mass (>=1.5x) paths unchanged and ungated. Adds tests/kernel-tier-defaults.test.ts pinning the contract into bili's suite (kernel defaults 1000/2000; applyCompressSettings never overrides triggers — boolean tiers toggle only flips enabled). Fixes #1249 (with acp-kernel#379)
Contributor
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)npm install -g billion-context@pr-1260Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf billion-context-pr1260.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Owner
Author
This was referenced Sep 24, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1249
What
Pins
acp-kernel0.0.85 → 0.0.86, bundling acp-kernel#379/#380:tiers.tier2Trigger5→1000,tier3Trigger10→2000 — the count path ("满5个块就蒸馏") is default-off. Block count is not a need signal: count-triggered distillations reclaimed ~nothing while rewriting the wire from the fold anchor onward → prefix-cache invalidation far beyond the reclaimed tokens — the sawtooth root cause of [Bug] oh-my-pi 长会话缓存命中率波动:相邻请求 99%→4%,125 folds 估算净收益为负 #1249.tierActionHintnow agrees withdecideNudge(pure count, default-off).bili-side surface
CompressSettings.tiersremains a boolean (enabledtoggle only); triggers are kernel-owned. Users who explicitly want count-driven distillation can no longer get it via bili config (never could) — kernel config is the escape hatch.tests/kernel-tier-defaults.test.tspins the contract into bili's suite: kernel defaults 1000/2000, andapplyCompressSettingsnever overrides triggers — so a future kernel bump that silently reverts fix: merge all system/developer messages into one leading message (SGLang #377) #379 fails CI here instead of re-opening [Bug] oh-my-pi 长会话缓存命中率波动:相邻请求 99%→4%,125 folds 估算净收益为负 #1249.Verification
npm run typecheckcleannpm run build✓ —dist/index.jsbundles the 1000/2000 defaults (tsup inlines the kernel)Sequence
acp-kernel 0.0.86 is already live on npm (
latest, tagv0.0.86) — this PR only needs to merge and ride the next bili release.