[ranxianglei]

Model: glm-5.3

Version bump only (0.1.60 → 0.1.61).

Changes since v0.1.60

The complete fix chain for the #292 context-leak incident (four supervisor-reviewed PRs):

• fix: adopt complete terminal usage atomically in anthropic adapter (stitched-stream double-count) #303 (issue fix: stitched-stream usage double-count after compress re-request (adapter-anthropic >0 guard) #300): stitched-stream usage double-count — message_delta usage is adopted atomically as a complete object (zeros may overwrite stale values), partial reports keep the >0 guard so relay-echoed input_tokens: 0 can't regress to undercounting. Fixes the fake 131% EMERGENCY trigger.
• fix: detect chained bili instances via x-bili-hop marker (#300) #304 (issue fix: detect chained bili instances (hop marker) — double processing corrupts session state #299): chained-bili detection — per-server instanceId, x-bili-hop marker stamped on requests this instance actually prepares; inbound marker → [warn] + full passthrough. Prevents double-processing when two bili proxies are chained.
• fix: honor anthropic-beta context-1m to size the context window #305 (issue fix: preflight compress must fail fast on upstream 429 instead of forwarding the over-window payload as-is #302): anthropic-beta: context-1m window detection — beta header resolves to the real 1M window per request, ahead of plugin/launcher/registry/config/table.
• fix: preflight compress fails fast on upstream errors instead of forwarding over-window payloads (#301) #306 (issue fix: honor anthropic-beta context-1m to size the context window #301): preflight fail-fast — payload-own estimate (not floored on possibly-stale lastInputTokens); unfixable overflow answers a structured preflight_compress_failed error (429→503 + retry-after) instead of forwarding a guaranteed-400 payload; a fitting payload forwards as-is.

Also included: v0.1.60's #311 anonymous prefix-affinity fallback (#309).

Pre-flight

• typecheck ✓
• 727/727 tests ✓
• build ✓

[github-actions]

📦 Built Package Artifact

Branch: 2026-08-28_release-v0.1.61 (f978c32)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-313

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

Option B — Download artifact

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

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

---

This comment is automatically updated on each push.

[ranxianglei]

🤖 ework agent · vllm-qwen/qwen3.8-27b

[bot] Verified the release branch 2026-08-28_release-v0.1.61 (f978c32) and re-ran pre-flight locally:

• Branch hygiene ✓ — single commit release v0.1.61, diff vs master is only package.json version 0.1.60 → 0.1.61 (no bundled content, no lockfile drift)
• typecheck ✓
• tests ✓ — 727/727 pass
• build ✓ — tsup bundle succeeds, dist/index.js 2.52 MB

All four #292 fix-chain PRs (#303–#306) are already merged on master ahead of this branch, so the release includes the complete chain.

Ready to merge. Note: per AGENTS.md I can't merge PRs — please merge yourself: #313. After merge, CI publishes to npm automatically; verify with npm view billion-context version.