release v0.1.104

[ranxianglei]

release v0.1.104

Version bump only — package.json plus the two root-version fields in package-lock.json. Ships everything merged to master since v0.1.103.

Changes since v0.1.103

• pi.dev listing (feat: add pi.dev preview image and improve package description #699 / pi dev首页优化 #698): added pi.image so billion-context gets a preview/avatar card on pi.dev/packages/billion-context, plus a value-first rewrite of the package description. Logo committed to docs/logo.svg (+ raster docs/logo.png).
• obs plugin (obs: per-request [acp-usage] on the plugin path + fold-materialization anchor ceiling #696 / Plugin path has no per-request cache usage log — post-fold 'cache drops to 0' cannot be attributed #695): per-request [acp-usage] on the plugin path + fold-materialization anchor ceiling.

Pre-flight (local, same checks CI runs)

• typecheck: clean
• test: 1367 pass / 0 fail (2 skipped, e2e-gated)
• build: success

No dependency changes; the lockfile diff is limited to the two root-version fields. CI publishes to npm on merge and creates tag v0.1.104.

[github-actions]

📦 Built Package Artifact

Branch: 2026-09-11_release-v0.1.104 (a1150dd)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-700

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

Option B — Download artifact

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

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

---

This comment is automatically updated on each push.

[ranxianglei]

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Reviewed release v0.1.104 (#700). Clean — ready for a human to merge.

Diff cleanliness (first gate) ✅ — version-only, nothing bundled:

• package.json: only the "version" field 0.1.103 → 0.1.104 (description untouched)
• package-lock.json: exactly the two root-version fields (version + packages[""].version) bumped
• No unrelated files, no whitespace/reorder churn, no content mixed into the release commit. Every line relates to the release.

Release-workflow compliance ✅

• Branch 2026-09-11_release-v0.1.104 matches YYYY-MM-DD_release-v{VERSION}
• Single commit, message release v0.1.104, changing only package.json + the lockfile's two root fields
• Correct increment from master's current 0.1.103

Up-to-date & referenced work landed ✅

• PR base SHA 92dac35 == origin/master HEAD — cut from the current master tip, no drift
• Referenced feature PRs are merged: obs: per-request [acp-usage] on the plugin path + fold-materialization anchor ceiling #696 (obs [acp-usage] + anchor ceiling) ✅, feat: add pi.dev preview image and improve package description #699 (pi.dev preview image + description) ✅ (Plugin path has no per-request cache usage log — post-fold 'cache drops to 0' cannot be attributed #695/pi dev首页优化 #698 are their companion issues)

CI ✅ — all 6 checks pass on head a1150dd: version-guard, build-artifact, and the full test matrix (ubuntu/windows × node 22/24). mergeable: true, no conflicts. mergeable_state was only blocked while the windows/node-22 test was still running; it has since passed.

No dependency changes, matching the stated scope. Nothing to fix on my side.

Per repo rules I can't merge PRs myself — please merge when you're ready: #700

---

中文摘要：这是一个纯版本号发布的 PR（v0.1.103→v0.1.104），diff 干净、只改了 package.json 与 lockfile 的两处根版本字段，分支命名/提交信息符合发布规范，基于最新 master、无冲突，6 项 CI 全部通过，可以合并。