Repository navigation
release v0.0.80 - #333
Merged
Merged
release v0.0.80#333
Conversation
Contributor
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)In your adapter project: npm install acp-kernel@pr-333Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf acp-kernel-pr333.tgz
npm install ./packageThis comment is automatically updated on each push. |
Owner
Author
[bot] 🏷 Verification complete for PR #333 (release v0.0.80) — no changes made, ready for human merge: Branch hygiene
Content check (matches issue body)
CI on head SHA
Per repo rules I can't merge PRs — please merge yourself: #333 . After the merge, CI tags 中文摘要:已核对 release 分支(单提交、仅改版本号 0.0.79→0.0.80、diff 干净)、确认 #223 与 #332 两个功能均已在 master 基线中、CI 四项检查(test×2 / pr-validation / build-artifact)全绿——可以合并。 |
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.
Changes since v0.0.79 (two features, both landed after the 0.0.79 tag):
feat: protectedLatestTools: protection primitive that shields only the latest instance of a given tool (unblocks billion-context#637 todo/capsule continuity — full-protection would let todo history grow unbounded against compression)feat(rules): acp_rule persistent rules: reconciled rules API (RULE_TOOL_NAME,DEFAULT_RULE_LIMITS {50, 300},addRule/removeRule/clearRules/listRules/allocateRuleId/resolveRuleLimits/formatRulesForPrompt/formatRulesList),CompressionState.rules?/nextRuleId?(optional, old persisted states load unchanged),Config.rules?,ALWAYS_PROTECTED_TOOLS += acp_rule, state carry through cloneState/sync/state-merge (unblocks billion-context#750; supersedes feat(rules): acp_rule persistent rules — state field, helpers, hard protection #283/feat(rules): acp_rule persistent rule records with hard compression protection #284, closed)04e97cdprettier formatting of the acp_rule filesPre-flight (this branch): typecheck PASS · 861/861 tests · build PASS.
Downstream note (cross-repo rule): after this publishes, billion-context bumps its pin to exactly 0.0.80 and rebases #750 + #637.