Skip to content

release v0.1.168 - #1594

Merged
ranxianglei merged 2 commits into
masterfrom
2026-09-28_release-v0.1.168
Sep 28, 2026
Merged

ranxianglei merged 2 commits into
masterfrom
2026-09-28_release-v0.1.168

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.167

@github-actions

github-actions Bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor Author

📦 Built Package Artifact

Branch: 2026-09-28_release-v0.1.168 (5cbbd19)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.1535-pr.1594.716527b

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Option B — Download artifact

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

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Release v0.1.168 audit complete — verified, no regressions found, ready for human merge.

This is an agent-created release PR (ework-agent-pr), so I did NOT redo the work — I pulled the branch, verified the code, checked CI, and ran the version-range regression audit (v0.1.167 → release head).

① PR integrity ✅

  • Head 7f3963bb == branch 2026-09-28_release-v0.1.168; single commit release v0.1.168, diff = ONLY package.json + package-lock.json version lines (0.1.167 → 0.1.168). One-version-one-commit-one-branch discipline holds.
  • npm latest = 0.1.167 = master's version field → drift-guard premise holds, 0.1.168 is the correct next patch.
  • mergeable: true (no conflicts with current master), mergeable_state: blocked = waiting on the human gate, as expected.

② CI (all green on head 7f3963b) ✅

CI · CI Windows codex overlay (#686) · E2E (real codex) · e2e-fake-codex · e2e-local-registry · e2e-native-pi/opencode/dsh · PR Build Artifact — all success.

③ Local pre-flight on the release head ✅

Checked out 7f3963bb: npm run typecheck clean · npm test 3097 pass / 0 fail / 16 skipped (skips = gated e2e suites, run separately in CI) · npm run build success.

②b Version-range audit — ⚠️ scope note for the owner

Master moved after the release branch was cut. The one-click dispatch ran at 12:57Z off af7d7407; PR #1586 then merged to master at 13:06Z. Merging this PR now publishes two content changes, not one:

Change Scope Verdict
#1542 — strip leaked chain checkpoints from incoming history at any position request pipeline (src/server.ts ×4 prepare paths, new stripEmbeddedChainCarriers) audited in depth below
#1579/#1586 — omp native identity stamp fixes (landed after the cut) agent-side only (src/agent/native-intercept.ts, src/agent/pi.ts) audited below

The issue body's "Changes since v0.1.167" lists only #1542 — stale. The auto-generated GitHub Release notes (git log since last tag) will correctly include both, so the published artifact and release notes stay consistent; only this thread's list is incomplete. No action required unless you want the body updated.

#1542 deep-dive (the pipeline change)

  • Root cause is correct: extractChainCarriers only recognizes carriers in the trailing user-run slot; a carrier that leaked into a client transcript and sank into mid-history is invisible to it, rides every resend, and stacks monotonically. The fix strips well-formed whole-part carriers from ANY position on the normal-processing path.
  • Recognition strictness matches the frozen ID contract (feat: chain checkpoint step 2 — shadow recognition (parser, JCS digest, carrier contract) #1397): whole-PART exact match via parseChainCheckpoint (all 5 attrs, strict regexes, ≤512 chars). Tag-shaped text embedded in prose is NOT stripped — the [bug] 插件透传会剥掉工具调用参数里的 render tag(arguments 流挂了 tag-echo 过滤器) #1039/design: Chain Checkpoint — first-processor-wins idempotent interop (Step 2/3) #1395 boundary is preserved (test asserts it).
  • Roles bounded: user+assistant (google: user+model). tool/system/function_call/compaction_trigger are never touched — tool-args-verbatim discipline intact.
  • Chain-verdict flow untouched: evaluateChain runs before prepare* (server.ts:1453); valid/recent-mismatch/stale-matched set chainSkip and the entire processing block is guarded by !chainSkip (server.ts:1704) → verbatim-forwarded chained-bili bodies never reach the strip. stale-unmatched/invalid/none fall through to normal processing, which now also strips mid-history carriers — the intended extension.
  • Wire invariants hold: kernel coreToAnthropic/coreToGoogle fuse same-side role runs, so removing a mid-history carrier cannot produce a non-alternating Anthropic/Google body; OpenAI/Responses have no alternation requirement. One theoretical residual (not blocking): if a leading google user-carrier entry were removed and no system injection follows, first-content could be model — practically unreachable since a stamp only ever exists after a real turn, and flagged here for completeness.
  • Both compression modes covered: the e2e test drives a real startServer + fake upstream in plugin-mode AND proxy-mode and asserts exactly ONE fresh carrier reaches the LLM (trailing slot), old digests absent, strip logged.
  • State safety: stripping happens before kernel projection, so removed carriers never enter ref assignment (no re-issue window — kernel cursor = highestUsedIndex+1); prefix-affinity matching stays consistent across resends because the strip is deterministic per version.
  • Behavior change (disclosed): incoming bodies carrying a well-formed whole-part <bili-chain> tag in user/assistant content at any position are now modified before kernel projection (previously passed through verbatim). Logged per request when >0. This is the fix itself.

#1579/#1586 (agent-side, landed after the cut)

Conclusion

本版本引入回归:无。 Both shipped changes are intentional, conservatively gated, test-pinned, and CI-green across the full gate set (incl. real-codex e2e). No config surface, persistence format, or acp-kernel pin changes. Per §7.4 the #1542 pipeline change is human-merge territory regardless — please merge yourself when ready: #1594 — CI publishes automatically on merge.

中文摘要:审核了 release v0.1.168(仅版本号 diff,CI 全绿,本地 typecheck/测试/构建复验通过);版本区间审计发现分支切出后 master 又合入了 #1586,故本次发布实际包含 #1542(链式检查点泄漏剥离,已逐路径核实无回归)与 #1579(omp 原生身份戳恢复,双重门控保守安全)两项修复,均有意变更且已披露,可以合并。

@ranxianglei
ranxianglei merged commit 839858f into master Sep 28, 2026
18 checks passed
@ranxianglei
ranxianglei deleted the 2026-09-28_release-v0.1.168 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