[ranxianglei]

Release v0.1.111 — version bump only.

Bumps package.json version 0.1.110 → 0.1.111 (+ the two version fields in package-lock.json). No code changes in this commit.

Changes since v0.1.110

• Auto-retry invisible degenerate terminal turns ([BUG] In some cases, with Codex's auto model + DeepSeek, it will suddenly terminate automatically. #732, fix: auto-retry invisible degenerate terminal turns (#732) #734) — detect terminal turns that end without visible output and auto-retry them instead of surfacing a dead end
• Tool-pair adjacency ([BUG] No tool output found for tool call call_xxxx #766, fix(responses): keep tool call/output pairs adjacent on the wire (#766) #768) — keep tool call / tool output pairs adjacent on the wire (Responses path), including the codex compact forge path; fixes the orphan-tool-output 400 class
• Strict-echo reasoning repair (DeepSeek thinking mode: residual "reasoning_content must be passed back" 400 on the first post-fold request (0.1.109 / acp-kernel 0.0.69) — the forwarded body is not persisted #762, fix: close the #762 strict-echo residual 400 class #763) — repair strict-echo reasoning on the compress-loop re-request path and close the residual strict-echo 400 class

New modules: src/tool-pair-order.ts, src/strict-echo.ts, src/error-dump.ts (+ their tests).

Pre-flight (local, same checks as CI)

• npm run typecheck — pass
• npm test — 1513 tests, 1511 pass / 0 fail / 2 skipped
• npm run build — success (dist/index.js ~2.8 MB, acp-kernel 0.0.69 inlined)

Merging this triggers .github/workflows/release.yml: CI runs npm ci + typecheck + test + build, then npm publish --tag latest, creates git tag v0.1.111, and creates the GitHub Release. No manual publish.

[github-actions]

📦 Built Package Artifact

Branch: 2026-09-14_release-v0.1.111 (a296768)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-777

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

Option B — Download artifact

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

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

---

This comment is automatically updated on each push.

[ranxianglei]

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Release PR verified — ready for merge.

Diff cleanliness (first gate): exactly as described — 2 files, 3 lines total, nothing else:

• package.json: "version" 0.1.110 → 0.1.111
• package-lock.json: both version fields 0.1.110 → 0.1.111

No code changes, no stray files, no whitespace churn. Every line is directly related to the release bump.

Release-flow conformance:

• Branch name 2026-09-14_release-v0.1.111 matches *_release-v* ✓
• Single commit, message exactly release v0.1.111 ✓ (CI trigger)
• Commit changes only package.json + package-lock.json ✓
• Parent commit = current master tip (9269bcc) — nothing bundled, and branch protection's strict: true up-to-date check is satisfied ✓

CI on head a296768: all required status checks green — test (ubuntu-latest, 22/24), test (windows-latest, 22/24) — plus real codex vs deterministic fake upstream (zero tokens), version-guard, build-artifact. mergeable_state is now clean (it was transiently blocked while CI was still running). No required reviews configured.

Changelog spot-check: the new modules claimed since v0.1.110 are all present on master with their tests — src/tool-pair-order.ts, src/strict-echo.ts, src/error-dump.ts (+ tests/tool-pair-order.test.ts, tests/loop-strict-echo.test.ts, tests/error-dump.test.ts).

I can't merge PRs — system rules forbid it; merging is human-only. Please merge yourself: #777 — after merge, CI will publish v0.1.111 to npm, tag it, and create the GitHub Release automatically.

中文摘要：已核对发布分支 diff 纯净（仅 3 行版本号变更）、提交信息与分支命名符合 §5 发布规范、head 基于最新 master、全部必需 CI 检查通过且可合并状态为 clean，可以合并。