release v0.1.76

[ranxianglei]

Changes since v0.1.75

• fix: minCompressRange unit is chars — new minCompressRangeChars key + registry conflict max-wins #490: minCompressRangeChars docs + --min-compress-range CLI alias + registry relay-conflict max-wins (bac8d91)
• fix: restart restores savedAt as lastSeen instead of fabricating boot-time activity (#404) #487 / 重启伪造时间戳:buildSession 用 Date.now() 覆盖 lastSeen,面板"最后活动"全员开机时刻、fallback=latest 在 ~245 路平局里随机挂会话 #404: restored-session lastSeen fix (f037419)
• fix: plugin mode gets the fake-completion detect+retry when enabled (#473) #486 / plugin mode is not covered by the fake-completion detect+retry (#371 / #378 follow-up) #473: plugin fake-completion detect + retry (37ecfce)
• fix: abort-path usage drop, upstream-timer leak, and bare AbortError logs (#411) #485 / 客户端取消 = 无主 AbortError ×260/天 + 已计费 usage 丢弃(lastInputTokens 冻结)+ 透传路径漏 10min timer(无 finally) #411: abort usage/timer leak fix (a3daf29)
• fix: detect codex compaction requests before preflight; verbatim passthrough when not intercepted (#332) #335: codex compaction preflight-order fix (4f5fe7e, merged with preflight fail-fast × soft-protection livelock: over-window payload never recovers, permanent 502 loop #332 verbatim passthrough)

Dependency

• acp-kernel 0.0.47 → 0.0.50 (exact pin). 0.0.50 is the revert release of the ref-reclamation change (fix(compress): accept JSON-string content in parseCompressInput #176) — restores the message ids are never reused invariant. Verified live on npm before bumping.

Pre-flight

• npm run typecheck ✓
• npm test 988/990 — the 2 failures are the known permanent local-env plugin-agent fails (same on clean master)
• npm run build ✓
• Full diff: package.json + package-lock.json only (version + kernel pin)

[github-actions]

📦 Built Package Artifact

Branch: 2026-09-03_release-v0.1.76 (8c7286e)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-495

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

Option B — Download artifact

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

tar xzf billion-context-pr495.tgz
npm install -g package

---

This comment is automatically updated on each push.

[ranxianglei]

🤖 ework agent · qwen3.8-27b

[bot] 🏷 v0.1.76 release verified — fully live. Post-merge verification results (§5 step 8):

Check	Result
PR #495	✅ merged 2026-09-03T14:17:54Z, merge commit 14c4cd0 is now master HEAD
Release commit 8c7286e	✅ touches ONLY package.json + package-lock.json: version 0.1.75→0.1.76, acp-kernel 0.0.47→0.0.50 (exact pin) — matches the claimed diff exactly
npm latest	✅ 0.1.76, published 2026-09-03T14:18:58Z (~2 min after merge)
Published artifact provenance	✅ tarball gitHead = 14c4cd0 (the merge commit); published metadata pins acp-kernel: "0.0.50"
Git tag	✅ v0.1.76 → 14c4cd0
Content ancestry	✅ all five listed changes are in master's history: #490 (bac8d91), #487 (f037419), #486 (37ecfce), #485 (a3daf29), #335 (4f5fe7e)
CI pre-flight	✅ release.yml gates publish behind typecheck + test + build — publish succeeding means all three passed in CI

Notes:

• Prerelease build 0.1.76-pr.495.317 under the pr-495 dist-tag is expected behavior, not a stray publish.
• acp-kernel 0.0.50 (the fix(compress): accept JSON-string content in parseCompressInput #176 revert release restoring message ids are never reused) was confirmed live on npm before the bump, per the dependency rule.
• Installed proxies on ≤0.1.75 will auto-update to 0.1.76 within one check interval; no manual action needed.

Nothing outstanding on this release — the issue can be closed.