Skip to content

release v0.1.158 - #1427

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-26_release-v0.1.158
Sep 26, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-26_release-v0.1.158

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Auto-fallback from the one-click release workflow: direct push to master was blocked by branch protection. Merging this PR publishes via the standard release.yml flow.

Changes since v0.1.157

@github-actions

Copy link
Copy Markdown
Contributor Author

📦 Built Package Artifact

Branch: 2026-09-26_release-v0.1.158 (9483874)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-1427

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

Option B — Download artifact

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

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner

审核

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

Release audit — v0.1.157 → v0.1.158 (15 commits)

PR shape: single commit release v0.1.158 (9483874) on top of current master; diff is exactly package.json + package-lock.json version lines. No content bundled into the release commit. ✅

CI: all green on head 9483874 — test matrix (ubuntu/windows × 22/24), e2e, real-client lanes (pi/codex/opencode/dsh), hermetic registry e2e, build-artifact, version-guard. mergeable_state: clean. ✅

Version-range regression audit (per release-PR policy, audited every commit since v0.1.157, not just the two version lines):

Intended behavior changes (all disclosed in their commits)

  1. bug(chain): ACP tag literals in normal history can permanently force fresh proxy sessions into passthrough #1357 advisory downgrade (40409f3b) — fresh session whose history carries ACP-shaped content (render tags / ACP tool names) with no local state: old = byte-identical passthrough, no session record, permanent lock-in (compression never engaged — the bug); new = one advisory warn + processed normally so the session establishes ownership. x-bili-hop remains authoritative verbatim passthrough (unchanged). Disclosed tradeoff: a header-stripping bili→bili relay may now double-process until signed chain proof ships (bug(chain): ACP tag literals in normal history can permanently force fresh proxy sessions into passthrough #1357 Phase 2/3). Note: /acp diagnostics phase value changed "chain-passthrough" → "chain-advisory" for programmatic consumers.
  2. compress 成功输出缺剩余范围快照与停止提示(pi 侧 #420/#521 对齐) #1387 compress receipt (f1e8fa18) — success receipt (model-visible tool result) gains an additive tail: live-recomputed remaining compressible ranges, or an explicit "no ranges remain, continue without compressing" stop signal. Silent on partial failure and tier-distillation nudges (correct — those still owe work). Fixes ghost-endId retry rounds (pi-side fix: /bili/ tunnel destination admission + management-plane tunnel block (#409) #420/feat: dsh 进 PLUGIN_AGENTS——native 插件部署 + 拦截层(native 模式 D) #521 alignment).
  3. rules 默认打开 + /acp-rule 命令补 remove/clear 转发(人类侧删除权) #1399/feat: acp_rule on by default + /acp-rule remove/clear forwarding (#1399) #1402 acp_rule — net vs v0.1.157: default unchanged (opt-in). The intermediate "on by default" flip was fully reverted per owner decision feat: acp_rule on by default + /acp-rule remove/clear forwarding (#1399) #1402: rulesEnabled back to === true, golden manifest regenerated without acp_rule, every default-on assertion flipped back. New surface when enabled: delete/clear ops + /acp-rule remove <id> / bare clear forwarding with typo guard (clear <text> records, never wipes).
  4. [enhancement] opencode zen 网关 (opencode.ai) 应进 omp/opencode lane 的默认 MITM 白名单 — 现状是静默盲隧、零压缩 #1405/[enhancement] opencode/omp 显式声明的 provider baseURL 从未被 extractHttpsHosts 自动发现(与 #1405 前提不符) #1411 MITM/discovery — purely additive coverage: opencode.ai seeded into omp/opencode lane whitelists (zen gateway has no local config file to discover), opencode/omp declared provider hosts now extracted, and the discovery mtime cache now watches exactly the file set loadClientConfig reads (fixes stale-cache; readAiderConfUrls refactor is behavior-neutral).
  5. feat: chain checkpoint step 2 — shadow recognition (parser, JCS digest, carrier contract) #1397 chain checkpoint step 2 — shadow recognition only: log verdicts, zero forwarding change, gated by the existing chainContentDetection kill-switch, skipped under x-bili-hop, wrapped in try/catch. Enforcement explicitly deferred to step 3 as a separate human-reviewed PR.

Verified non-changes

  • x-bili-hop verbatim passthrough path untouched.
  • No dependency drift: zero package.json dep changes since v0.1.157 (acp-kernel pin identical — the new kernel exports used by stream.ts/chain-checkpoint.ts exist in the pinned version, confirmed by green typecheck/build/test).
  • src/update.ts, release workflow, CI publish, message-ref/id logic: untouched.
  • Test commits (b3d211f4, ecd496a5) restore/repair harnesses only; docs commits are en/zh-synced wording.

Conclusion: 本版本引入回归:0 处。 All five behavior deltas are intended and disclosed (old→new above); defaults that mattered (acp_rule opt-in, x-bili-hop authority) verified byte-equivalent to v0.1.157 semantics. 可以合并。

@ranxianglei
ranxianglei merged commit 825f152 into master Sep 26, 2026
13 checks passed
@ranxianglei
ranxianglei deleted the 2026-09-26_release-v0.1.158 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.

1 participant