Repository navigation
[PR] Every surface self-identifies its lane: origin on status/overview, web sys.lane row, /acp via <origin> - #4698
Conversation
… field, web sys.lane row, /acp panels via <origin> Multi-lane machines (proxy lane + per-agent test lanes) made version-only surfaces ambiguous: three lanes can share 0.1.206 while only one carries the commit under test. Now /__bili/status and /__bili/overview expose origin (the host:port this lane was addressed by), the web Overview card shows a running-lane row, the /acp panel version line appends '· via <origin>', and the pi / dsh / dsh-native / opencode armed-idle notices say 'via <lane>' (armedIdleNotice grows an optional base argument).
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5741-pr.4698.399867bThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4698.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复。 本 PR 是「多 lane 自报身份」的新实现;相关但不同的既有工作:
标签: pi dsh opencode scope/ui p3 —— 功能类改动,横跨 pi/dsh/opencode 三车道 idle 通知与 web/status 展示面;纯可观测性增强、无功能缺陷,不打 bug。 审查进行中:分支已拉取、diff 已通读(11 文件 +23/−16,单 commit),正在做回归清点与定向测试,CI 状态确认后按八问给完整结论。 |
…, opencode-v2) Review of PR #4698 found its "every surface self-identifies its lane" goal missed two surfaces that carry their own idle notices instead of routing through armedIdleNotice(): - hermes-plugin /acp + /acp-cache idle lines now say "proxy connected via <origin>, compression armed" (origin was already in scope at both sites, guarded by the existing !origin early-return) - opencode-v2 /acp idle lines now say "proxy connected via <base>, no ACP session yet" (base = state.proxyBase ?? proxyBaseFromEnv(), guarded by the existing !base early-error) Test pins updated to assert the via clause against the real fake-proxy origin (http://127.0.0.1:<port>). Targeted verification: hermes-native + opencode-v2 + dsh-acp + opencode-acp-command + plugin-agent + acp-panel + web-sessions + advisory-endpoint-parity + storage-mode-label + dsh-native + build-info = 297 pass / 0 fail / 1 skip; tsc clean; unused-export gate clean.
(ai: vllm-qwen/qwen3.8-27b) Review 完成:方向正确、实现干净;发现并当场补齐 PR 漏掉的 2 个面(hermes、opencode-v2),已推修复 commit 审核过程(独立重做,非复读 issue):
八问:
判定:可合——代码与测试质量达标,方向无误;等 |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.836-master.16ecf9f # this exact build
npm install -g billion-context@master # always the newest merged build
|
问题
多 lane 并存(生产 lane + per-agent 测试 lane)时,各面板只报 version,而不同 lane 常常同版本号(如三条 lane 都叫 0.1.206,只有一条带被测 commit)——用户分不清流量落在谁家(#4323 拓扑排查时靠日志归属,面板不自报)。
改动
/__bili/status与/__bili/overview新增origin字段 = 本 lane 被客户端实际寻址的 host:port(req.headers.host,relay 后面也对)。sys.lane),zh/en i18n。/acp面板(plugin status panel)版本行追加· via <webOrigin>(deps.webOrigin 既有字段)。proxy connected via <lane>, compression armed(armedIdleNotice(version, base?)共享单源,`billion-context@${version} — proxy connected, no ACP session yet. Send a model request 被到处复制无统一实现 #883 纪律)。验证
dsh-acp11/11(正则随 via 更新)、hermes-native38/38、opencode-acp-command+web-sessions+web-admin-api38/38;tsc 0;unused-export gate clean。"origin": "127.0.0.1:18890";renderPage 快照含sys-lane行;header 已带v0.1.207 (commit)。kernel-change: none