release v0.1.57

[ranxianglei]

Release v0.1.57

Cuts a new release to ship the acp_delegate prompt fix from #276.

Why a new version (not reusing 0.1.56)

v0.1.56 (#282) was branched from the pre-fix base, so it does not contain the delegate fix — commit 91c0206 is not an ancestor of the v0.1.56 release commit. The fix reached master via #276 only after that cut. This release is based on current master (bcd841e), which does include the fix.

Changes

• Bump version 0.1.56 → 0.1.57 (package.json + package-lock.json)
• No dependency changes — acp-kernel stays at 0.0.50 (already shipped in v0.1.56)

Ships

• fix(delegate): gate ACP_DELEGATE prompt on resolveDelegate().enabled #276 — fix(delegate): gate ACP_DELEGATE prompt on resolveDelegate().enabled

Pre-flight

• npm run typecheck — clean
• npm test — 466 tests, 463 pass, 0 fail, 3 skipped
• npm run build — OK

[github-actions]

📦 Built Extension Artifact

Branch: 2026-09-03_release-v0.1.57 (3c8954c)

Option A — Install from npm PR tag (recommended)

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

Each push to this PR publishes a new version under the pr-284 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-pr284.tgz
pi install ./package

---

This comment is automatically updated on each push.

[ranxianglei]

🤖 ework agent · qwen3.8-27b

[bot] 🏷 Reviewed release PR #284 (v0.1.57). I verified every claim against the actual diff and re-ran the pre-flight suite locally on the release commit. Everything is consistent — ready for a human to merge.

What I checked

Lineage / ships the fix

• Release commit ca257b7 ("release v0.1.57") has parent bcd841e = current master (the merge of fix(delegate): gate ACP_DELEGATE prompt on resolveDelegate().enabled #276). ✅ matches "based on current master (bcd841e)".
• Fix 91c0206 (fix(delegate): gate ACP_DELEGATE prompt on resolveDelegate().enabled, closes [BUG] acp_delegate 禁用后ACP_DELEGATE_PROMPT提示词仍注入 #275 via fix(delegate): gate ACP_DELEGATE prompt on resolveDelegate().enabled #276) is an ancestor of ca257b7 → v0.1.57 does ship the fix. ✅
• Confirmed the premise for why a new version is needed: 91c0206 is not an ancestor of the v0.1.56 release commit a91e71b (whose parent is cbb753a, the v0.1.55 merge) — so v0.1.56 genuinely lacks the fix. ✅

Diff scope

• Exactly 2 files changed, 3 insertions / 3 deletions: package.json + package-lock.json, both bumping version 0.1.56 → 0.1.57. No source changes. ✅
• acp-kernel untouched by the diff, stays at 0.0.50 (already shipped in v0.1.56). ✅

Pre-flight (independent re-run on ca257b7 after npm ci)

• npm run typecheck — exit 0, clean. ✅
• npm test — 466 tests, 463 pass, 0 fail, 3 skipped. ✅ (exactly matches the issue)
• npm run build — dist/index.js 540.22 KB, Build success, exit 0. ✅
• Functional confirmation of the shipped fix: tests 251 & 252 ("delegate:false / delegate:{enabled:false} omits the ACP_DELEGATE NOTIFICATIONS section from the system prompt") both pass. ✅

npm state

• latest dist-tag is currently 0.1.56, so 0.1.57 is the correct next version (can't republish 0.1.56). ✅
• PR prebuild pr-284 = 0.1.57-pr.284.74 is live (per the Actions comment).

Verdict

Correctly cut release, minimal 2-file diff, all checks green, follows the release conventions (branch 2026-09-03_release-v0.1.57, commit message release v0.1.57). Nothing needs changing.

⚠️ Per system rules I can't merge PRs myself — please merge #284 when you're ready; CI will publish 0.1.57 on merge.