Repository navigation
[PR] gate: dsh protocol-matrix lanes into master (fixes #3500's wrong base) | gate: dsh 协议矩阵车道进 master(补 #3500 的 base 错位) - #3564
Conversation
…tions (#3475) Extend the dsh gate lanes from one protocol to all four pi-ai protocols (openai-completions / openai-responses / anthropic-messages / google-generative-ai) plus a dsh proxy-mode lane for same-host two-activation-path contrast. Same headless driver and corpus flow; only the cordis provider api + baseURL suffix differ per lane. - per-door WIRE_EXPECT hard assertion: every recorder POST must match the door path regex AND body top-level shape; first request dumped to egress-sample.json as round-trip evidence - blocked semantics: ENV-BLOCKED (door unhealthy: all-rejected or degraded mid-flow, opencode2/#3461 rule) and CLIENT-BLOCKED (client config surface cannot express the api yet — dsh's cordis schema lists no google-generative-ai in 0.2.0-rc.2 / 0.2.1-rc.1); excluded from tally, printed at exit - calibration fixes from real-model runs: GATE_OUTPUT_TOKENS (thinking models degenerate when output budget < thinking budget), p1 = max over full post-t1 log, post-fold small-window widening for adaptive recipes, mid-seed guard, lane-local dsh install (GATE_DSH_VERSION) + lane TMPDIR - t1 dual marker (S40+S07): verify the read precondition so downstream S07 recalls can't fail for fixture reasons Existing lanes' generated configs are byte-identical to pre-#3475 (parity harness); new lanes are GATE_AGENTS opt-in. Local real-model run: 56/56 passed (dsh-responses:env, dsh-google:client).
…l-matrix gate: dsh 协议矩阵车道(四门)+ dsh proxy 车道 — wire 硬断言 (#3475)
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.4215-pr.3564.bf318cfThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr3564.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 审核完成。本 PR 是把 #3500(dsh 协议矩阵车道)补进 master——之前合错了分支( 1. 是什么问题:gate(CI 插件门禁)此前只走 dsh 的 chat 门,pi-ai 另外三门(responses/anthropic/google)没有 wire 层硬校验——如果 bili 静默换协议(比如 google 请求实际走了 chat),gate 不会红,#3475 要求补上每门硬断言 + 跑不了车道的降级机制。 2. 什么原因导致的:一是原 gate 脚本只有「回合完成」这种软信号,没有对出站 wire 做路径+形状断言;二是这批内容当初(#3500)base 选错分支,一直没进主线。 3. 影响范围与严重程度:只动 CI/gate 面—— 4. 怎么修复的:每门一张 5. 是否有回归问题:逐项审过,无意回归没有;有意变更如下(全部已写入两版 README):
6. 是否破坏缓存:不涉及(没碰产品代码)。 7. 是否改了设计方向:不涉及——只是 gate 基础设施扩展,产品架构/数据流不变。 8. 是否引入了新的配置:无产品配置新增。gate 脚本新增 3 个 CI 状态(head 协调提醒:在途 PR #3497(opencode warmup 车道,开得更早)也改同一个 一个小建议(未推):mid-clamp 那行注释写 判定:可合入。按惯例由人工合并:#3564 |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.558-master.38d0149 # this exact build
npm install -g billion-context@master # always the newest merged build
|
ai: zhipuai-lb/glm-5.3
这是什么
把 #3500(dsh 协议矩阵车道)送进 master。#3500 之前合进了
feat/gate-plugin-lanes分支(base 选错了分支,不是 master),导致这批 gate 扩展一直没进主线——v0.1.198 发布时也不含它。本 PR 不带新改动,就是同一批内容进 master,下次发版带上即可。内容(即 #3500)
dsh(chat,原有)/dsh-responses/dsh-anthropic/dsh-google,外加dsh-proxy前缀模式车道(同宿主双激活路径对照)。WIRE_EXPECT):recorder 收到的 POST 必须匹配该门路径 + body 顶层形状;首请求落盘egress-sample.json作往返证据。静默换协议(google 走成 chat、responses 走成 chat)当场红,不靠「回合完成」这种软信号。ENV-BLOCKED(上游门不健康——全部被拒或中途劣化)/CLIENT-BLOCKED(客户端当前版本驱动不了该协议,如 dsh ≤0.2.1-rc.1 无 google-generative-ai)——各自从记分中剔除,客户端支持后自动升级,无需改脚本。影响面
只动
scripts/gate/(plugin-lanes.mjs / README / zh-CN)+ ci-gate-plugins.yml 输入描述 + .gitignore。产品代码零改动,不影响运行时。Closes #3475