Skip to content

[PR] docs(zcode): clarify the zai-vs-bigmodel compression dead-end in CLIENTS Known limitations - #4610

Open
ranxianglei wants to merge 4 commits into
masterfrom
2026-10-25_zcode-zai-clients-docs
Open

ranxianglei wants to merge 4 commits into
masterfrom
2026-10-25_zcode-zai-clients-docs

Conversation

@ranxianglei

@ranxianglei ranxianglei commented Oct 24, 2026 •

Copy link
Copy Markdown
Owner

Refs #4593 (documentation facet only — the issue stays open for the design discussion on byte-faithful routing / ZCode-side fix).

What

The ZCode "Known limitations" block was self-contradictory for zai-series coding-plan accounts whose model endpoint is zcode.z.ai:

Change (docs only, en + zh mirror)

Clarify that #661 rejects kernel-rebuilt bodies on the zcode.z.ai model endpoint, and split the two coding-plan families by endpoint:

Behavior

None. Two .md files only (CLIENTS.md, CLIENTS.zh-CN.md). No code, config schema, wire, persistence, or version change.

@ranxianglei ranxianglei changed the title docs(zcode): clarify the zai-vs-bigmodel compression dead-end in CLIENTS Known limitations [PR] docs(zcode): clarify the zai-vs-bigmodel compression dead-end in CLIENTS Known limitations Oct 24, 2026
@github-actions

github-actions Bot commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-25_zcode-zai-clients-docs (c0b7ca7)

Latest build — install this exact version

npm install -g billion-context@0.0.9720-pr.4610.1ab76b9

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
c0b7ca7 billion-context@0.0.9720-pr.4610.1ab76b9 build
67475b4 billion-context@0.0.9696-pr.4610.b25e408 build
0fde4dd billion-context@0.0.6174-pr.4610.c8638ff build
77d039d billion-context@0.0.6089-pr.4610.66aed80 build
556fe64 billion-context@0.0.5991-pr.4610.e239905 build
62e24ad billion-context@0.0.5869-pr.4610.796d31f build
8ce6c85 billion-context@0.0.5802-pr.4610.84087ac build
fc72d81 billion-context@0.0.5643-pr.4610.d0ad59e build
0b63525 billion-context@0.0.5572-pr.4610.0d21267 build
3ed43e0 billion-context@0.0.5570-pr.4610.a7aaf8e build

Download artifact

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

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

自动修复判定(attempt 1/2):继承 master 常红,不在本分支修——等 #4606 合入后 rebase。

八问:

  1. 是什么问题:本 PR 的 CI unused-exports 静态门禁报 INTERNAL_ONLY src/agent/client-build-note.ts: ClientBuildCheck(run 40119715478 / job 120948389385);其余 12 个静态门禁全绿,test 分片因前置门失败未调度(skipped)。
  2. 什么原因导致的:不是本 PR 引入的。master head 146b34f27(合并 [PR] merge: tier-5 train — dsh prepare/streaming domain (7 PRs: bili_final terminal marker, auto-fold storm gate, wire-only guard) #4590 tier-5 train)起,src/agent/client-build-note.ts:32 导出的 ClientBuildCheck 全仓只在本文件内使用(本地已核实 origin/master:仅 32/45/81/93/115 五行),master 自身在该门禁上 born-red;前置门跑在 merge commit 上,所有在途 PR 都继承这条红。本 PR diff 只有 CLIENTS.md(+25/-16)与 CLIENTS.zh-CN.md(+1/-1),不碰任何 TS,不可能影响导出图。证据链:master head run 40111170499(job 120923016330)与本 PR run 报错行逐字节一致(CI Control Center: Centralized CI Failure Handling & Status Sync (Comment all CI issues here; do not open new issues) | CI 总控: CI 失败集中处理与状态同步(所有 CI 问题在此评论, 勿开新 issue) #4599 已有记录);根因与一行修法已立 fix(ci): master unused-exports is red — ClientBuildCheck is exported but only used inside its own file #4602。
  3. 影响范围与严重程度:当前所有并入 master 的 PR 都继承这条红(红信号失去区分度);纯静态门禁,零运行时行为影响。
  4. 怎么修复的:本轮不在本分支动手——规范修复载体是 [PR] fix(ci): clear the two master-red gates in one branch — unused-exports (#4602) + the #3890 LIVE_FILES tripwire (#4604) #4606(一条分支同时含「去 ClientBuildCheck export」fix(ci): master unused-exports is red — ClientBuildCheck is exported but only used inside its own file #4602 + 「tests/issue3890-parent-gone-confirm-drain.test.ts 补 LIVE_FILES 登记」fix(ci): every test shard is red — tests/issue3890-parent-gone-confirm-drain.test.ts spawns processes but is missing from LIVE_FILES #4604 两条 master 常红;二者互为前提,只合其一另一条仍红、拿不到全绿)。把这一行改动复制进本 docs 分支属于超范围捆绑,且修完 test 分片还会撞第二条 master 红,CI 仍不绿。[PR] fix(ci): clear the two master-red gates in one branch — unused-exports (#4602) + the #3890 LIVE_FILES tripwire (#4604) #4606 合入后 rebase 本分支重触发即可。
  5. 是否有回归问题:无——本分支零改动。
  6. 是否破坏缓存:不涉及。
  7. 是否改了设计方向:不涉及。
  8. 是否引入了新的配置:不涉及。

结论:本轮判定+停手,未向分支 push 任何提交;已在 #4599 留一行继承记录;待 #4606 合入后自动 rebase/重触发。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

查重: 不重复 —— 本 PR 是 #4593(zcode 风控死路)文档面的唯一实现(#4593 线程已记录该 PR);近期无其他 PR 触碰 CLIENTS.md 的 ZCode Known limitations 段。
标签: zcode / scope/docs / p3(已有 pr)—— 纯文档澄清,zcode 车道,无运行时影响,故 p3。

结构化八问

  1. 是什么问题:CLIENTS.md 的 ZCode「已知局限」段自相矛盾 —— 把 billion-context ACP kernel 改写 body 导致 ZCode (zcode.z.ai) 405/3012 #661 反欺诈墙的作用域写成了「登录流量」,且同段既推荐「用 GUI 证书 MITM 获得压缩」又推荐「保留 passthrough 路由」,对 zai 系账号二者互斥。
  2. 什么原因导致的:文档落后于现场证据 —— billion-context ACP kernel 改写 body 导致 ZCode (zcode.z.ai) 405/3012 #661/zcode risk control issue | zcode风控问题 #4593 的日志已钉死触发点是 zcode.z.ai 的模型端点(/api/v1/zcode-plan/anthropic/v1/messages),且一次 fold 都没发生时(nudge idle、usage 0%,纯 round-trip 重序列化)就 405/3012;旧文字仍按「login traffic」表述,并保留了一刀切的 MITM 压缩推荐。
  3. 影响范围与严重程度:仅文档面。受影响的是照旧文档操作的 zai 系用户 —— 会照「用 cert-MITM 获得压缩」去配,然后撞上必然的 405;无运行时/数据影响,p3。
  4. 怎么修复的:重写该段 —— 把 billion-context ACP kernel 改写 body 导致 ZCode (zcode.z.ai) 405/3012 #661 作用域纠正为模型端点;按端点拆分两个 coding-plan 系列(bigmodel 系 open.bigmodel.cn 可正常压缩 / zai 系 zcode.z.ai 任何 kernel 处理都 405,必须 passthrough、可用但不压缩,当前不存在两全配置);删掉与 passthrough 互斥的一刀切 MITM 推荐。
  5. 是否有回归问题:无。diff 只碰两个 .md;逐句核对了段落其余部分(v3.14+ 签名墙、route:"all"/"plans" 降级边界、pre-3.14 不受影响、attach 模式 inert、BILI_NATIVE_ZCODE=0 退出开关)在 en/zh 两侧均原样保留。唯一措辞漂移:zh「把这些账号逐条跳过」→「把改写整体跳过」,是与既有英文 "skips the rewrite entirely" 对齐,下一句仍澄清 route:"all" 下只有这些账号被跳过,无语义回归。
  6. 是否破坏缓存:不涉及(无代码)。
  7. 是否改了设计方向:不涉及。
  8. 是否引入了新的配置:不涉及。

事实核对(独立重查,非复读 issue 结论)

顺手修掉的小问题(已在 PR 分支补 commit)

引用号写错:正文与 PR 描述里的 (#4592) 指向 GitHub 上不相干的 compress 功能请求(preserveRecentTurns)—— 那是 eework 内部编号,GitHub 侧对应的是 #4593。已改:两个 .md 各一处 + PR 描述 Refs 行,commit 0b6352520(新 head),已推送。

CI

head 上仅 unused-exports 红 —— 与 master head 报错行逐字节相同(INTERNAL_ONLY src/agent/client-build-note.ts: ClientBuildCheck),是已立案的继承性 master 红(#4602,修复在 #4603,#4599 总控有记录),与本 PR 无关(docs-only diff 不可能影响导出图);其余门禁全绿或按门控 skip。

结论:可合。 内容核实通过、镜像一致、无行为变更;唯一的红是继承性 master 红,master 转绿后(或直接合入,文档不影响任何测试)即可合并。

@ranxianglei ranxianglei added p3 scope/docs zcode 改动范围:内核之外的主机侧接线(src/agent 适配器、server 路由、注入拦截)/范围兜底/客户端标签 labels Oct 24, 2026
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

自动修复判定(attempt 2/2,末轮):同一继承红,本分支不动手——自动修复通道到此结束。

新 head 0b63525 是纯 review-fix 提交(引用改 #4593、两文档文件各 1 行),不碰任何代码;base 仍是 146b34f27,根因未变。

八问(简版,完整证据链见 attempt 1 评论):

  1. 是什么问题:run 40121188430 / job 120952860885 的 unused-exports 报 INTERNAL_ONLY src/agent/client-build-note.ts: ClientBuildCheck,与 attempt 1 及 master head run 40111170499 逐字节一致;其余静态门禁全绿。
  2. 什么原因导致的:未变——master 146b34f27 起该类型导出但仅文件内使用,master 自身 born-red;本 PR 纯文档,与该门禁无关。
  3. 影响范围与严重程度:同前——所有并入 master 的在途 PR 继承此红;纯静态门禁,零运行时影响。
  4. 怎么修复的:不在本分支修(复制一行改动属超范围捆绑,且修完 test 分片还会撞 master 的第二条常红,CI 仍不绿)。规范载体仍是 [PR] fix(ci): clear the two master-red gates in one branch — unused-exports (#4602) + the #3890 LIVE_FILES tripwire (#4604) #4606,等人工合并。新观察(供 owner 决策,超出本 lane 范围):[PR] fix(ci): clear the two master-red gates in one branch — unused-exports (#4602) + the #3890 LIVE_FILES tripwire (#4604) #4606 的 head 6d6ebb7 自身 CI 也有 10 个 test 分片红(抽样一个分片 2384 pass / 20 fail,为具体断言失败而非 flake 形状)——即修复载体目前尚未全绿,合并前需要先处理这些失败。
  5. 是否有回归问题:无——本分支零改动。
  6. 是否破坏缓存:不涉及。
  7. 是否改了设计方向:不涉及。
  8. 是否引入了新的配置:不涉及。

结论:2/2 自动修复轮次用尽,未向分支 push 任何提交。解锁路径:#4606 转绿并合入后,本分支 rebase 重触发即可全绿;在此之前本 PR 的 unused-exports 会持续继承红。

ework-agent and others added 3 commits November 14, 2026 04:35
The suite baseline preload (preload-storage-baseline.mjs) pins
BILI_STORAGE_UNIFIED="legacy" for the broad corpus. After #6480 flipped the
storage default to pure-sqlite, the notice-registry suite's visibleNotices
assertions expect the pure-sqlite default notice, which is gated on
unifiedSelectionIsSqlite (unified "sqlite" or absent) — the preload's
"legacy" made the notice silent, so the suite was born-red on master. Pin
the selection explicitly (#4011 lesson: a test that depends on the production
default passes locally but fails in CI).
…n limitations (#4592)

The #661 anti-fraud wall is described as hitting 'login traffic' and the doc blanket-recommends 'use GUI cert-MITM for compression on these accounts', which contradicts the required mitm://zcode.z.ai passthrough route for zai-series accounts whose model endpoint IS zcode.z.ai (kernel -> 405/3012, passthrough -> no compression). Clarify that #661 trips the model endpoint, and split bigmodel-series (open.bigmodel.cn, compressible via cert-MITM) from zai-series (zcode.z.ai, must passthrough, no compression today).
…not #4592

compression dead-end is tracked in #4593 (mirrored from eework issue 4592,
whose internal number was cited by mistake). Docs-only.
@ranxianglei
ranxianglei force-pushed the 2026-10-25_zcode-zai-clients-docs branch from 0fde4dd to 67475b4 Compare November 13, 2026 21:56
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

Merge conflict resolved and pushed. The PR was dirty because master moved CLIENTS.md / CLIENTS.zh-CN.md into docs/ (docs-layout reorg — the root files are now one-line redirect stubs), while this PR was still editing the old root paths.

What I did this run:

  1. Diagnosed the conflict: whole-file conflicts in both root files; master's CLIENTS.md/CLIENTS.zh-CN.md are now redirect stubs pointing at docs/clients.md / docs/clients.zh-CN.md.
  2. Rebased 2026-10-25_zcode-zai-clients-docs onto current master (e1f31ad9). The branch's 6 "merge ci-fixes" sweep commits (CI Control Center: Centralized CI Failure Handling & Status Sync (Comment all CI issues here; do not open new issues) | CI 总控: CI 失败集中处理与状态同步(所有 CI 问题在此评论, 勿开新 issue) #4599 help-merge) became empty against current master and were dropped — their content is already in master.
  3. Resolved both conflicts by re-targeting the PR's two docs commits to the new locations: the zai-vs-bigmodel known-limitations rewrite now lands in docs/clients.md (41 lines) and docs/clients.zh-CN.md (1 line); the root stubs are kept untouched. Verified the pre-change text was byte-identical at the new paths, so no content was lost or altered.
  4. Verified the final tree: git diff origin/master...HEAD --stat = exactly docs/clients.md | 41 + docs/clients.zh-CN.md | 2 — identical to the original PR's content diff; the final zcode known-limitations text (en block + zh line, citing zcode risk control issue | zcode风控问题 #4593) is byte-identical to the branch's intended final state.
  5. Pushed: fetched first (remote head unchanged at 0fde4dd9, no concurrent work), then force-pushed the rebase (explicitly permitted for conflict rebases). New head: 67475b4067.

Live-verified status after push: mergeable: true, mergeable_state: blocked (no longer dirty — "blocked" is the pending-review/CI state, not a conflict). CI check runs had not yet appeared in the mirror cache at the time of this reply; the diff is docs-only (two markdown files), so no kernel/wire/config surface is touched.


八问(中文结论)

  1. 是什么问题:PR [PR] docs(zcode): clarify the zai-vs-bigmodel compression dead-end in CLIENTS Known limitations #4610 与 master 冲突(dirty)——master 已把 CLIENTS.md/CLIENTS.zh-CN.md 迁入 docs/clients.md/docs/clients.zh-CN.md(根目录只剩重定向占位),而本 PR 还在改旧路径。
  2. 什么原因导致的:PR 分支(10-25)之后 master 完成了文档目录重组;分支上的 6 个 ci-fixes 合并提交也随 master 演进而失去内容。
  3. 影响范围与严重程度:仅影响本 PR 的合并状态;docs-only,无运行时行为影响。
  4. 怎么修复的:rebase 到最新 master,把两个 docs 提交的内容重定向到新路径 docs/clients.md 与 docs/clients.zh-CN.md,根目录占位文件保持 master 原样;ci-fixes 空合并提交随 rebase 丢弃。
  5. 是否有回归问题:无。最终 diff 与原 PR 内容 diff 完全一致(2 个文件、同样的行数),最终文本与分支意图逐字节一致;未触碰任何 src/、kernel/、配置面。
  6. 是否破坏缓存:不涉及(纯文档)。
  7. 是否改了设计方向:不涉及。
  8. 是否引入了新的配置:不涉及。

判定:冲突已解除,PR 处于可合并等待状态(blocked = 等 review/CI),无遗留问题。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

CI red triaged & the inherited part fixed on the branch. Re-verified live first: both reported jobs were still completed/failure (single job-state fetch, then log download — no polling).

Failure accounting (run 43515038366, head 67475b4067):

  1. visibleNotices ×2 — inherited master red (fixed this run). Both shards fail the same two tests: visibleNotices: fresh install sees the default flip + pck + wm intro, registry order (iot absent ⇒ hidden) and visibleNotices: dismissing one hides only that one (ubu24-s1: 2/4349 fail; win22-s2: 2 of 3). Root cause: master's pure-sqlite default ([PR] storage: pure-SQLite default — JSON envelopes stop being written unless dual-write is requested (#6479) #6480) changed storage selection for the notice-registry suite; the pin fix c6369fb6a1 ("fix(tests): pin pure-sqlite selection in notice-registry suite") lives only on ci-fixes — verified via git merge-base --is-ancestor that it is NOT in master (e1f31ad9) nor in this branch. Per the CI-coordination policy, master fixes converge on ci-fixes: merged origin/ci-fixes into the PR branch (clean, no conflicts; the merge adds exactly 5 lines to tests/notice-registry.test.ts), pushed as c0b7ca73ec (regular push, no force — remote head was unchanged at fetch time).
  2. abort x proxy-openai-sse: client abort mid-stream destroys the upstream request (win22-s2 only) — documented Windows timing flake, not fixable PR-side. Assertion upstream socket(s) must be destroyed after the client abort (closed=0) at tests/wire-exit-matrix.test.ts:273, test duration 21.2s — it outlasted even the current stop-loss budget (ABORT_TEARDOWN_BUDGET_MS = win32 ? 20000 : 10000, already on this branch via master). This is the long-documented closed=0 flake family on slow Windows runners (CI Control Center: Centralized CI Failure Handling & Status Sync (Comment all CI issues here; do not open new issues) | CI 总控: CI 失败集中处理与状态同步(所有 CI 问题在此评论, 勿开新 issue) #4599 floors 475/502/521 and many more; sibling cells in the same matrix passed in 73–419ms on the same runner). This PR's diff is two docs files — zero intersection with the abort/teardown path. The budget is at its stop-loss boundary ("再红就查真 hang,不再加预算"), so no in-branch budget bump. The new push re-triggers CI; if the same signature recurs on a clean runner, it escalates per the documented criteria as a sentinel/ci-fixes item. Reported in CI Control Center: Centralized CI Failure Handling & Status Sync (Comment all CI issues here; do not open new issues) | CI 总控: CI 失败集中处理与状态同步(所有 CI 问题在此评论, 勿开新 issue) #4599.

Live status now: branch head c0b7ca73ec pushed; the new CI run is starting (mirror cache had not populated it yet at the time of this reply — I won't assert its outcome until it exists).


八问(中文结论)

  1. 是什么问题:PR [PR] docs(zcode): clarify the zai-vs-bigmodel compression dead-end in CLIENTS Known limitations #4610 的 CI 两个 test 分片红(ubu24-s1、win22-s2),共 3 个失败用例。
  2. 什么原因导致的:两个独立根因——① visibleNotices ×2 是继承性 master 红:master 的 pure-sqlite 默认([PR] storage: pure-SQLite default — JSON envelopes stop being written unless dual-write is requested (#6479) #6480)改变了 notice-registry 套件的存储选择,而修复 pin(c6369fb6a1)只在 ci-fixes 分支、未进 master;② win22-s2 的 wire-exit-matrix abort x proxy-openai-sse closed=0 是在档 Windows 慢 runner 时序 flake 族(21.2s 超出 20s 止损预算,同矩阵兄弟用例 73–419ms 全过)。
  3. 影响范围与严重程度:仅本 PR 的 CI 信号;docs-only diff,无用户侧功能影响。
  4. 怎么修复的:① 按 CI 协调政策把 origin/ci-fixes merge 进 PR 分支(无冲突,仅 +5 行 tests/notice-registry.test.ts),普通 push 到 c0b7ca73ec;② flake 不在 PR 侧修(预算已在止损边界,PR diff 与 teardown 路径零交集),新 push 重触发 CI,同签名干净 runner 复发则按在档口径升级哨兵/ci-fixes。
  5. 是否有回归问题:无。merge 只带入 ci-fixes 的一个测试 pin 提交;本 PR 内容 diff 不变(仍为 docs/clients.md + docs/clients.zh-CN.md 两个文件)。
  6. 是否破坏缓存:不涉及(纯测试 pin + 文档)。
  7. 是否改了设计方向:不涉及。
  8. 是否引入了新的配置:不涉及。

判定:继承红已按政策收敛(merge ci-fixes),flake 已分账并在 #4599 留档;等新 run 结果,若 visibleNotices 仍红或 abort 同签名干净 runner 复发,再按在档口径处置。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

Status update — full triage + 八问 already posted in the comment above; this confirms the current live state.

Work this run (detail above):

Live now (mirror cache, fetched 01:07Z, head c0b7ca73ec): new run in progress — 0 failed / 12 pending, gates green, e2e lanes skipped (as expected). The two previously-red test shards have not run yet, so I will not assert green until they complete.

判定:继承红已按政策收敛(merge ci-fixes 已 push c0b7ca73ec),flake 已分账并在 #4599 留档;新 run 进行中,待 test 分片出结果后再确认。

This branch has not been deployed

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

Labels

p3 scope/docs zcode 改动范围:内核之外的主机侧接线(src/agent 适配器、server 路由、注入拦截)/范围兜底/客户端标签

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant