release v0.1.67

[ranxianglei]

内容

• feat(acp): scope nudge + compress-outcome bookkeeping per session (#317) #327(nudge/压缩失败记账按 sessionId 隔离,Prime Agent integration: session-scoped ACP state and isolated inline RLM runners #317 接缝 3)— 首次进入发布线,v0.1.66 发版晚于其合并

发布物

• package.json + package-lock.json:0.1.66 → 0.1.67(acp-kernel pin 不变,仍 0.0.63)

验证

• 699 tests / 0 fail / 3 skip(feat(acp): scope nudge + compress-outcome bookkeeping per session (#317) #327 合并后全量)
• typecheck ✓ / build ✓

[github-actions]

📦 Built Extension Artifact

Branch: 2026-09-11_release-v0.1.67 (451d3ee)

Option A — Install from npm PR tag (recommended)

pi install npm:billion-context-pi@pr-365

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

Option B — Download artifact

1. Download the artifact from the Actions run
2. Extract the tarball and install:

tar xzf billion-context-pi-pr365.tgz
pi install ./package

---

This comment is automatically updated on each push.

[ranxianglei]

🤖 Powered by ework · qwen3.8-27b

Reviewed release v0.1.67 (branch 2026-09-11_release-v0.1.67 @ 451d3ee).

Verified (static, from git objects)

• Release commit is clean: 451d3ee touches exactly package.json + package-lock.json, message release v0.1.67 — matches the two-file release-commit convention.
• Version bump correct: 0.1.66 → 0.1.67 in both files (package.json version + lockfile top-level and packages[""], lockfileVersion 3, no stray changes).
• acp-kernel pin unchanged: still exact "0.0.63" in package.json and the lockfile's node_modules/acp-kernel entry (resolved URL matches acp-kernel-0.0.63.tgz) — no drift risk.
• feat(acp): scope nudge + compress-outcome bookkeeping per session (#317) #327 content reviewed (4 files: src/runtime.ts, src/index.ts, src/compress-tool.ts, tests/compress-retry.test.ts):
  • Nudge ledger: nudgeShownTurns Set<turnKey> → Map<sid, Set<turnKey>>; nudgeShownTokens → Map<sid, Map<turnKey, number>>. Root cause addressed correctly — the old global structures let one session's reset wipe another session's dedup/cap state, and turnKey alone isn't guaranteed unique across sessions.
  • Compress-outcome tracker: global compressOutcomeSeen/compressFailTurnKey/compressFailCount → per-session Map<sid, CompressOutcomeTracker>; semantics (idempotency per toolCallId, success reset, neutral freeze, one-shot cappedNow) preserved.
  • session_shutdown now also calls clearNudgeTracking(sid) + clearCompressRetryTracking(sid) — good, prevents unbounded growth of the new maps across long-lived processes.
  • All call sites updated consistently; 3 new tests cover concurrent-session counters, per-session clear, and nudge-ledger isolation. No as any/@ts-ignore.
• feat(acp): scope nudge + compress-outcome bookkeeping per session (#317) #327 landing path confirmed: PR feat(acp): scope nudge + compress-outcome bookkeeping per session (#317) #327 is closed/merged, but its merge commit 4f1ae66 exists only on this branch (head 1f4576d is NOT an ancestor of master) — so feat(acp): scope nudge + compress-outcome bookkeeping per session (#317) #327 lands in master via this release PR, exactly as the issue states.

Not verified locally — blocker reported

My sandbox is out of disk: every tool (bash, read, URL fetch) fails with ENOSPC: no space left on device, write, so I could not run typecheck / the 699-test suite / build here. Ops may need to free space on the daemon host. Indirect evidence: the github-actions artifact comment was generated for exactly this commit (451d3ee), so the CI build step succeeded on it.

Minor notes (no action needed)

• Timeline nit for the record: v0.1.66 shipped 15:26 UTC, feat(acp): scope nudge + compress-outcome bookkeeping per session (#317) #327 merged 15:46 UTC — i.e. v0.1.66 actually preceded the merge; the issue's "v0.1.66 发版晚于其合并" reads backwards (likely a typo). Conclusion unaffected: feat(acp): scope nudge + compress-outcome bookkeeping per session (#317) #327 first ships in v0.1.67.
• feat(acp): scope nudge + compress-outcome bookkeeping per session (#317) #327 was merged into the release branch rather than master-first. End state is identical and its PR is already closed, so nothing to redo — just flagging the deviation from the usual feature→master→release flow.

Verdict

Diff is clean — every line serves either the version bump or #327, no unrelated changes. Version bump and kernel pin check out; #327's code and tests review OK. Mergeable (CI build artifact already produced for this commit; I recommend merging).

---

中文摘要:本次为发布 PR 审查 —— 版本 0.1.66→0.1.67 与 acp-kernel pin(仍 0.0.63)逐项核对无误,#327(sessionId 隔离 nudge/压缩失败记账)代码与新增测试审查通过、diff 干净无跑题改动,且确认 #327 将随本 PR 首次进入 master;因沙箱磁盘写满(ENOSPC)本地无法复跑 typecheck/测试/build,已上报运维,CI 已对该 commit 生成构建产物,可以合并。