Skip to content

[PR] docs(clients): add Command Code BYOK entry point to verified-entry-points table (#5995) - #5997

Merged
ranxianglei merged 4 commits into
masterfrom
2026-11-09_command-code-byok-doc-row
Nov 10, 2026
Merged

ranxianglei merged 4 commits into
masterfrom
2026-11-09_command-code-byok-doc-row

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Part of #5995 — adds Command Code (the cmd CLI from commandcode.ai) to the #2340 verified-entry-points table so its working BYOK path is discoverable.

Changes (docs only, en + zh-CN):

Verification: provider-store schema cross-checked against Command Code's public BYOK docs (providers.json shape, three wires, keys stored separately in auth.json). End-to-end /bili/ behavior on real cmd traffic was verified by the reporter (#5995).

No behavior change; no config surface touched; no version bump.

The remaining asks of #5995 (native lane posture; gateway-wire question) are outside this PR: the wire question is already covered by #1295 / PR #1444, and the native lane is pending an owner decision in the issue thread.

ework-agent and others added 2 commits November 9, 2026 10:49
…n LIVE_FILES

Converged master-red fix (sentinel ci-fixes lane): #5989 merged the
spawning suite without registering it, so the #1248 SPAWN_RE tripwire
kills all 11 core-matrix test shards before any test runs on every PR
head. Hunk is byte-identical to open PR #5990 (which carries the same
registration plus a test-tolerance change to master).
@ranxianglei ranxianglei added documentation Improvements or additions to documentation p3 scope/docs labels Nov 9, 2026
@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-11-09_command-code-byok-doc-row (7d7e264)

Latest build — install this exact version

npm install -g billion-context@0.0.8740-pr.5997.1280cc8

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

Recent builds (commit → version)

commit version build
7d7e264 billion-context@0.0.8740-pr.5997.1280cc8 build
47fa17f billion-context@0.0.8739-pr.5997.24447f8 build
f81a4a3 billion-context@0.0.8738-pr.5997.b4bc551 build

Download artifact

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

Install instructions are refreshed on each push.

@ranxianglei ranxianglei changed the title docs(clients): add Command Code BYOK entry point to verified-entry-points table (#5995) [PR] docs(clients): add Command Code BYOK entry point to verified-entry-points table (#5995) Nov 9, 2026
en/zh markup parity: the English bullet links to the unrecognized-endpoint
section via an anchor; the Chinese bullet referenced the same heading as
plain text. The file already uses CJK anchors (MITM section), so the
derived slug follows the established pattern.
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

查重:不重复。 Open-PR 检索:#1444(declarable custom-wire 特性,网关 wire 的代码侧修复)是互补不是重复——本 PR 只记录今天就能用的 BYOK 路径,#1444 改的是尚不可用的路径的代码;#5128 同属 #1295 家族但是另一个客户端。两者都被本 PR 明确划在范围外,切分正确。

标签: PR 自带 documentation/p3/scope/docs(按自身 diff 判定:纯文档、低危);镜像线程已补 command-code/scope/docs/p3(文档类不打 bug)。

Review(PR #5997,分支 2026-11-09_command-code-byok-doc-row):

方向:#5995 的短期诉求就是「把 Command Code 加进 #2340 verified-entry-points 表」,本 PR 恰好做这一件事、不多做。native lane 姿态留在 #5995 线程等 owner 决策、网关 wire 问题归 #1295/#1444——范围切分正确。

声明逐条对源码核验过(不只信 PR 文本):

  • 三条 BYOK 声明 wire(openai-completions/openai-responses/anthropic-messages)分别落在 /chat/completions、/responses、/v1/messages——全部被 src/server/handle.ts:408-412 识别(与 src/server/observability.ts:41 列出的已知协议集合一致),「今天就能压缩」在 bili 侧成立;
  • 目录/网关 wire POST /alpha/generate 不在该集合内 → 按 dsh使用插件dsh-commandcode-provider反代go套餐的话,不进billion-context压缩 #1290 一节逐字节中继,锚点目标存在(docs/clients.md:852),en 链接 slug 与标题完全吻合;
  • zh-CN 注释原本用纯文字引用该节而 en 用锚点链接,已对齐为真实锚点链接(沿用本文件既有的 CJK 锚点模式,见下方 MITM 节链接),独立小修 commit 7d7e264;
  • 表格行与注释项格式与上下文一致,en/zh 内容逐条对齐确认。

CI(实时核实,非记忆):

Diff(vs master):docs/clients.md +2、docs/clients.zh-CN.md +2(精修后 +1/-1)、scripts/live-files.mjs +7(ci-fixes 合并带入)。每一行都与本 PR 目的相关,无噪音。

结构化八问:

  1. 是什么问题:Command Code(cmd,commandcode.ai)缺席客户端文档的「Adopting unlisted clients」表,其可用的 BYOK 压缩路径不可发现;其目录模型静默不压缩(dsh使用插件dsh-commandcode-provider反代go套餐的话,不进billion-context压缩 #1290 行为)也没有指引。
  2. 什么原因导致的:非缺陷,是文档缺口——客户端收养:剩余低成本可接入客户端(Crush / Zed / Continue / Cline 家族等) #2340 通用机制本来就支持该客户端,只是没人记录它的入口(~/.commandcode/providers.json 的 baseURL)。
  3. 影响范围与严重程度:仅文档可发现性,零行为影响;p3。
  4. 怎么修复的:一张表加一行(base URL 在哪)+ 一条注释(BYOK 与目录模型的区分,指向 dsh使用插件dsh-commandcode-provider反代go套餐的话,不进billion-context压缩 #1290 节与 [Feature] Declarable custom-wire model endpoints — route providers like commandcode's Go plan (/alpha/generate) into compression #1295),中英双语同步。
  5. 是否有回归问题:触碰路径的既有行为逐项清点——表内容(行追加、既有行未动)、注释列表(项插入、其余未动)、锚点完整性(两个链接目标均验证存在);无语义/阈值/时序/输出格式漂移。无回归。
  6. 是否破坏缓存:不涉及(未触运行时代码)。
  7. 是否改了设计方向:无。遗留的设计问题(native lane 姿态、可声明网关 wire)仍归 Support Command Code (commandcode.ai CLI) — BYOK /bili/ works today; gateway wire + native seams for a fuller lane #5995/[Feature] Declarable custom-wire model endpoints — route providers like commandcode's Go plan (/alpha/generate) into compression #1295,未被本 PR 挪用。
  8. 是否引入了新的配置:无。

判定: 内容正确、最小、范围干净;继承性 CI 红已按政策结构性解决(ci-fixes 合并 + tripwire 本地复验)。待新 head 7d7e264 远程 CI 转绿即可合并——合并按钮归你。

@ranxianglei
ranxianglei merged commit 541cf26 into master Nov 10, 2026
48 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.1159-master.541cf26 (rolling master tag).

npm install -g billion-context@0.0.1159-master.541cf26  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

command-code documentation Improvements or additions to documentation p3 scope/docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant