Skip to content

docs(#1998): default pi recommendation to billion-context in README (en/zh) - #2000

Merged
ranxianglei merged 2 commits into
masterfrom
2026-10-03_pi-default-recommend
Oct 3, 2026
Merged

ranxianglei merged 2 commits into
masterfrom
2026-10-03_pi-default-recommend

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

What & why

Issue #1998 asks to switch the default pi recommendation to this project (billion-context) instead of pointing at the standalone in-process extension billion-context-pi.

The "Which do I need?" table's pi row previously recommended only billion-context-pi (in-process extension). It now recommends billion-context first — bili pi (launcher) or bili plugin install pi (native) — mirroring how the opencode row recommends billion-context while noting the standalone extension remains usable. The standalone billion-context-pi is kept as an explicit "remains usable" note (consistent with the opencode → opencode-acp precedent and the mutual-exclusivity paragraph right below the table).

Both English (README.md) and Chinese (README.zh-CN.md) updated.

Scope

  • Docs only — 2 lines changed (the pi table row in each README).
  • No code / config / behavior change; the links reuse URLs already present in the files.

Closes #1998

@github-actions

github-actions Bot commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-03_pi-default-recommend (f74f462)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.2012-pr.2000.ff08b28

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr2000.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei
ranxianglei force-pushed the 2026-10-03_pi-default-recommend branch from 37157ee to 4fe268f Compare October 3, 2026 14:38
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 PR 已核对完毕(这是 #1998 会话产出的 PR,按 [PR] 流程做验证而非重做)。

审查结论

  • 方向(①):默认pi推荐切成本项目 #1998 要求把 README 选型表里 pi 的默认推荐从独立扩展 billion-context-pi 切到本项目——PR 正是这个最小改动,中英文各 1 行,方向正确。
  • 事实核对(③):bili pi(启动器)与 bili plugin install pi(原生)均真实存在(src/cli.ts:557、src/cli.ts:78);新行复用的是文件里已有的 URL,无新增失效链接;表下「原生模式 vs 独立扩展」互斥段落的准确性不受影响("仍可用"标注与 opencode → opencode-acp 的既有写法一致)。
  • 回归(②):纯文档,无代码 / 配置 / 行为变更。base 之后 master 上另一个 PR(建议:客户端侧连接请优雅关闭(close_notify+FIN),避免向下游客户端发出 RST #1982)在两个 README 的不同区域(~L295/~L375)加了「连接生命周期调优」段,与本改动(~L105)不交叠。
  • 时效性:分支落后 master 60 个提交——已 rebase 到当前 master(干净、无冲突,两区域共存已验证),push 了新 head 4fe268f9,CI 正在新 head 上重跑(version-guard 已过,其余 in_progress)。
  • diff 整洁度(⑤):2 文件共 2 行,无无关改动。

结构化七问

  1. 是什么问题:README「Which do I need?」表把 pi 的默认推荐指向独立进程内扩展 billion-context-pi,而不是本项目。
  2. 什么原因导致的:历史遗留——早期 pi 只有独立扩展一条路径;本项目后来补上了 bili pi 启动器和 bili plugin install pi 原生两条泳道,表格这行没跟着更新。
  3. 怎么修复的:pi 行改为优先推荐本项目(启动器 / 原生两条命令),保留一句"独立 billion-context-pi 仍可用",对齐同表 opencode 行的既有写法。
  4. 是否有回归问题:无。纯文档;与 base 之后 master 上的其他 README 变更(建议:客户端侧连接请优雅关闭(close_notify+FIN),避免向下游客户端发出 RST #1982 段)无交互,rebase 后并存。
  5. 是否破坏缓存:不涉及。
  6. 是否改了设计方向:不涉及。只调整默认推荐指向,pi 的两条泳道本身没有任何变化。
  7. 是否引入了新的配置:不涉及。

判定:rebase 后的 4fe268f9 可直接合(CI 绿即合)。合并请由人工执行:#2000

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 CI 跟进(新 head 4fe268f9)

判定:PR 内容本身已验证可合;若要求 CI 全绿,等 master 侧测试修复即可——docs-only 改动即使现在合入也不会引入任何新的失败面。合并请人工执行:#2000

@ranxianglei
ranxianglei merged commit 614df19 into master Oct 3, 2026
10 of 14 checks passed
ranxianglei pushed a commit that referenced this pull request Oct 3, 2026
Conflict resolution (union of intent):
- tsup.config.ts: noExternal gains both "ws" (master, preflight transport
  resilience) and "typebox" (this PR, inlined build-time dep).
- README.md: pi row keeps this PR's in-process-default semantics (#1988) plus
  master's #2000 entry points (bili pi launcher / bili plugin install pi).
@ranxianglei
ranxianglei deleted the 2026-10-03_pi-default-recommend branch October 15, 2026 05:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

默认pi推荐切成本项目

1 participant