Skip to content

fix: pin acp-kernel 0.0.80 (protectedLatestTools + acp_rule rules API) - #1030

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-20_kernel-0.0.80
Sep 20, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-20_kernel-0.0.80

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Bumps the exact acp-kernel pin 0.0.79 → 0.0.80 (released just now). Two kernel features landed after the 0.0.79 tag:

Verified against the installed 0.0.80 dist: every symbol #750 imports is exported; both #223 primitives are exported.

Pre-flight: typecheck PASS · tests 2003/2003 (2 gated E2E skips) · build PASS. Diff is exactly package.json + package-lock.json.

Follow-ups after this merges: rebase #750 and #637 onto this master (their kernel imports then resolve as-is).

- #223 protectedLatestTools: collectLatestProtected / isMessageLatestProtected — kernel primitive for 'protect only the latest instance of a tool'
- #332 acp_rule rules API: RULE_TOOL_NAME, DEFAULT_RULE_LIMITS, addRule/listRules/removeRule/clearRules, resolveRuleLimits, formatRulesForPrompt/formatRulesList, CompressionState.rules?/nextRuleId?, Config.rules?

Unblocks #750 (acp_rule feature) and #637 (todo/capsule continuity) for rebase.
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-20_kernel-0.0.80 (9c1c953)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-1030

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

Option B — Download artifact

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

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Reviewing this PR now: pulling the branch, verifying the diff is exactly package.json + package-lock.json, confirming acp-kernel 0.0.80 is live on npm with all claimed exports, and re-running pre-flight (typecheck / test / build) on the rebased head. Will report back shortly.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Review complete — verified, ready to merge (merge stays human-only per AGENTS.md; also cross-repo dependency bumps are never auto-merged).

What I checked on branch 2026-09-20_kernel-0.0.80 (head 9c1c953):

  1. Diff hygiene — exactly package.json + package-lock.json, one commit over master, zero behind. Change is strictly the exact pin acp-kernel: 0.0.79 → 0.0.80 (no caret — complies with the exact-pin rule); lockfile version/resolved/integrity all consistent. No version field touched.
  2. Cross-repo ordering (§5) — npm view acp-kernel version returns 0.0.80, i.e. the kernel release is live on npm before this bump, exactly as required. npm ci verified the lockfile integrity hash against the registry.
  3. Claimed exports — installed the pinned 0.0.80 and probed its dist directly. All 11 symbols export: collectLatestProtected, isMessageLatestProtected (kernel feat(launcher): add hermes to the bili launcher (/bili/ rewrite, no MITM) #223), and RULE_TOOL_NAME (string), DEFAULT_RULE_LIMITS (object), addRule, listRules, removeRule, clearRules, resolveRuleLimits, formatRulesForPrompt, formatRulesList (kernel preflight fail-fast × soft-protection livelock: over-window payload never recovers, permanent 502 loop #332). Matches the issue description.
  4. Local pre-flight on the rebased head — typecheck PASS · build PASS · tests 2001 pass / 0 fail / 2 skipped (the 2 gated E2E skips, matching the stated 2003/2003).
  5. GitHub CI — all check runs green: test ubuntu-latest 22+24, windows-latest 22+24, build-artifact. PR state: open, not draft, mergeable: true, mergeable_state: clean.

No issues found while working this — nothing to report separately. After this merges, #750 and #637 can rebase onto master and their kernel imports resolve as-is.

中文摘要:已核对 diff(仅 package.json + lockfile,精确 pin 0.0.79→0.0.80)、确认 acp-kernel 0.0.80 已在 npm 发布且全部 11 个声称的导出符号真实存在、本地 typecheck/build/测试全绿、GitHub CI 全绿且分支可干净合并——可以合并。

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.

1 participant