fix: usage-gate count-triggered tier nudges - #238
Merged
Conversation
Count-based tier distillation (tier2Trigger/tier3Trigger) fired at any usage once enough blocks accumulated. Below the nudge usage band there is no need yet, and the injected suggestion made repetition-prone models flail against the tier3-rewrite guard. Gate the count paths behind nudge.minContextLimitPct (the same band the first-sight bypass uses); token-mass paths (>= 1.5x threshold) stay ungated. The idle reason now labels gated tiers as 'usage-gated' so acp_status explains the silence.
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)In your adapter project: npm install acp-kernel@pr-238Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf acp-kernel-pr238.tgz
npm install ./packageThis comment is automatically updated on each push. |
This was referenced Sep 9, 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 #237
nudge.minContextLimitPct— count-triggered T2/T3 distillation no longer fires below the usage band (was: any usage once 5 blocks exist).t2Pen >= tier2Threshold, 1.5× threshold) stay ungated — crossing them is need by itself.reasonnow labels count-ready-but-gated tiers:ready: T2 8 blocks (count, usage-gated)— acp_status explains why nothing injected.Production repro (session 01a07b3c, 2026-09-09 14:41): T2 nudge injected at 43% usage / 5872 pending tokens → model flailed → user saw repeated injections. With this gate the injection is suppressed; the mass still shows as
usage-gatedin status.Tests: 2 new (#237) + full suite 631 pass; typecheck clean.