Skip to content

[PR] fix(pi): inline mode now intercepts codex Responses WebSocket traffic (#4526) - #4559

Open
ranxianglei wants to merge 15 commits into
masterfrom
wt-4526-ework-daemon
Open

[PR] fix(pi): inline mode now intercepts codex Responses WebSocket traffic (#4526)#4559
ranxianglei wants to merge 15 commits into
masterfrom
wt-4526-ework-daemon

Conversation

@ranxianglei

@ranxianglei ranxianglei commented Oct 24, 2026

Copy link
Copy Markdown
Owner

Closes #4526

What & why

With BILI_PI_INLINE on, pi's HTTP model traffic correctly ran through the in-process engine — but the Codex Responses WebSocket lane was left unpatched on the false premise that "the pi lane does not use codex WS". It does: pi rides the codex provider over exactly that lane (#2073/#2111). So codex WS dialed the model directly — uncompressed, with no ACP session record. The old comment claiming otherwise is removed.

Changes

  1. Loopback WS bridge in the inline engine (src/inline-engine.ts). The engine binds one real listener: a loopback-only HTTP server on an ephemeral 127.0.0.1 port that serves WebSocket upgrades only, reusing installWebSocketBridge verbatim from the spawn-mode path (loopback-source admission, tunnel-destination SSRF guard, session lifecycle) with the codex codec and the same per-request pipeline (pipelineFor, shared with the HTTP dispatcher). Unclaimed upgrades keep the 426 contract so Codex's fast-fallback can switch to HTTP POST (which still compresses in-process). Plain HTTP on that port gets a 404. The listener is unref()'d — it never holds the host process open.
  2. Graceful degradation. If the bind fails (or engine bootstrap rejects), ONLY the WS channel degrades direct with a one-shot warn; the engine and HTTP compression stay healthy. No undialable pseudo-origin URL is ever handed to a real dialer.
  3. Client-side routing (src/agent/native-ws-intercept.ts, src/agent/pi-native.ts). Inline mode now installs the WebSocket wrapper too. In inline mode the wrapper resolves its target through state.resolveInlineWs/state.wsOrigin (the bridge origin, decided when the engine settles) instead of state.origin — which is frozen to the pseudo-origin that never listens and would short-circuit readyOrigin to an undialable URL. Connections made before the decision settle are held in the existing deferred shell. Spawn/attach lanes are byte-identical: the new branch keys on the inline-only resolver being present.
  4. Switch value table + observability (planNativePi). See Behavior changes below; arm-time info log makes the switch visible in the host log.

Behavior changes (old → new)

# Old New Why
1 BILI_PI_INLINE enabled inline only for 1/true (case-insensitive); on/yes/ON/… silently fell through to spawn mode (the reported "inline doesn't work, still starts a server" confusion) Any non-empty value other than 0/false/no/off enables inline The issue's second complaint: unrecognized values must not silently pick a different mode
2 Off values were only 0/false; no/off were unrecognized, so the config-file pi.inline: true still WON over them Off tokens expanded to 0/false/no/off; they now disable over the file value Explicit-off must mean off
3 Inline mode bound no listener at all One unref'd loopback-only upgrade listener on an ephemeral port (bind failure degrades only the WS channel direct, warned) A WebSocket needs a real dialable endpoint; loopback-only keeps the attack surface at zero
4 Inline mode skipped installNativeWebSocketIntercept entirely Installed in every non-off mode; inline routes via the bridge The actual bug fix
5 No log line saying inline took effect Arm-time info: [bili-native(pi)] inline mode active — compression runs in-process, no proxy spawned; engine log gains the bridge address Observability requested in the issue

Blank/whitespace values keep today's semantics (neutral — the config file decides). Spawn/attach lanes: no change.

Config surface

No new field/env/flag. BILI_PI_INLINE (existing, documented in CONFIGURATION.md en+zh) gets a relaxed value table — rows updated in this PR.

Tests

  • tests/pi-native.test.ts: planNativePi truth table (on/yes/ON/" True " → inline; no/off/OFF/false → spawn; no/off beat fileInline=true; blank neutral).
  • tests/native-ws-intercept.test.ts: inline seams — settled fast-path rewrite to the bridge origin (and routedOrigin deliberately NOT recorded, avoiding a The same sessionId is served by two bili processes simultaneously: interleaved logs from global + pi-native dual instanc | 同一 sessionId 被两个 bili 进程同时服务：全局 + pi-native 双实例日志交织、重复 cold-load（split-brain） #3923 split-brain false alarm against the pseudo-origin), deferred hold while booting, degrade-direct on unavailable bridge, bootstrap rejection degrades without unhandled rejection.
  • NEW tests/issue4526-pi-inline-ws.test.ts (hermetic XDG, mock codex WS upstream): real engine boot exposes a dialable wsOrigin; real ws client round trip through the bridge — probe forwarded verbatim, turn compressed (ACP tools injected), ACP session recorded (the issue's missing-record symptom); plain HTTP on the bridge port → 404; wrong-shape upgrades → 426; end-to-end client wiring with BILI_PI_INLINE=on through the patched global WebSocket (deferred shell → attach → exchange).
  • Targeted suites green locally (pi-native, native-ws-intercept, pi-inline: 48 pass; issue4526 suite: 3 pass); typecheck clean. Full suite = CI.

No kernel/, no version bump, no lockfile churn.

@ranxianglei ranxianglei changed the title fix(pi): inline mode now intercepts codex Responses WebSocket traffic (#4526) [PR] fix(pi): inline mode now intercepts codex Responses WebSocket traffic (#4526) Oct 24, 2026
This was referenced Oct 24, 2026
Closed
Closed
@ranxianglei

ranxianglei commented Oct 24, 2026

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

查重:不重复——但这是同一 issue 的第二次 PR。 前一次尝试是 PR #4527(branch 2026-10-24_pi-inline-ws-bridge),已于今日 14:10Z 被关单,关单理由即「同 issue 存在更新的 PR #4559」。#4527 当时的审核结论:代码质量达可合标准、方向正确、回归干净;挡合入的是 master 自身存量红 + 一笔与在途 #4534 撞车的 docs-sync seed 提交。本 PR 应为吸收这些反馈后的重做(单 commit 9b99c17,+602−27,10 files)。

标签:bug, pi, codex, scope/wiring, p2(pi inline 车道 codex WS 绕过压缩;inline+codex 用户丢压缩但有绕行,非数据丢失/缓存泄露类,维持 #4527 审定的 p2)

开始按 PR 规范独立审核(不复读 #4527 的结论):①原 issue 方向 → ②回归审查 → ③代码 → ④测试有效性 → ⑤diff 整洁度。另注意到 GitHub 实时状态 mergeable=false/dirty(head 落后 master 4 个提交),会先验证是真冲突还是陈旧状态,需要的话 rebase 到最新 master 再交 CI。结论稍后以结构化八问回复。

@github-actions

github-actions Bot commented Oct 24, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: wt-4526-ework-daemon (44219ec)

Latest build — install this exact version

npm install -g billion-context@0.0.5639-pr.4559.02db234

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
44219ec billion-context@0.0.5639-pr.4559.02db234 build
8042523 billion-context@0.0.5563-pr.4559.5252517 build
e82ccd7 billion-context@0.0.5559-pr.4559.1790cd4 build
6056114 billion-context@0.0.5547-pr.4559.1dcce08 build
2b8c4e9 billion-context@0.0.5544-pr.4559.eb45599 build
af6786f billion-context@0.0.5536-pr.4559.b365935 build
f90e209 billion-context@0.0.5525-pr.4559.ec43943 build
b9e666a billion-context@0.0.5520-pr.4559.50d84dc build
e44c054 billion-context@0.0.5514-pr.4559.cbdc317 build

Download artifact

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

Install instructions are refreshed on each push.

ranxianglei pushed a commit that referenced this pull request Oct 24, 2026
ci-check
docs: correct stale BILI_PI_INLINE off-token comment in config.ts (#4559
de47eae 
 small fix)

#4526 widened the explicit-off tokens from {0,false} to
{0,false,no/off}; the pi.inline doc comment in FileConfig still listed
only 0/false. Comment-only, matches planNativePi (src/agent/pi-native.ts).
ranxianglei pushed a commit that referenced this pull request Oct 24, 2026
ci-check
chore(ci): drop accidentally committed scratch file .tmpfailids.txt (#…
f90e209 
…4559 small fix)

Check-run id list left behind while debugging the CI failures; not part
of the change.
ranxianglei pushed a commit that referenced this pull request Oct 24, 2026
ci-check
docs: correct stale BILI_PI_INLINE off-token comment in config.ts (#4559
4f25af9 
 small fix)

#4526 widened the explicit-off tokens from {0,false} to
{0,false,no/off}; the pi.inline doc comment in FileConfig still listed
only 0/false. Comment-only, matches planNativePi (src/agent/pi-native.ts).
ranxianglei pushed a commit that referenced this pull request Oct 24, 2026
ci-check
chore(ci): drop accidentally committed scratch file .tmpfailids.txt (#…
37eb323 
…4559 small fix)

Check-run id list left behind while debugging the CI failures; not part
of the change.
@ranxianglei

ranxianglei commented Oct 24, 2026

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

Review 完成,结论:方向正确、代码质量达标,可合(CI 绿后由人合并)。 我独立审了全部 diff(未照抄 issue 结论),ci-worker 修的两个门禁红已逐项验证,另发现并直接修掉一个错误路径缺陷,已 rebase 到最新 master 并推送——新 head af6786f(4 commits:主修复 + 两个小修 + 我的 parity 小修)。

结构化八问:

  1. 是什么问题:pi inline 模式(BILI_PI_INLINE)下,codex 的 Responses WebSocket 车道绕过压缩直连上游(HTTP 车道正常),不压上下文也不留 ACP 会话记录;且 BILI_PI_INLINE=on/yes 等取值被静默降级成 spawn 模式。
  2. 什么原因导致的:三层——① inline 分支把 state.origin 冻死成永不监听的伪源站 http://billion-context.inline;② installNativeWebSocketIntercept 在 inline 模式被跳过(旧注释错误声称 "pi lane does not use codex WS");③ planNativePi 只认字面量 1/true,其余非空值无日志回落 spawn。
  3. 影响范围与严重程度:仅影响显式开启 inline 且客户端走 codex Responses WS 车道的用户面;后果是 WS 流量不压缩(上下文增长/成本)+ 无会话记录,HTTP 不受影响。p2:能用且有绕行(spawn 模式或写 1/true)。
  4. 怎么修复的:机制层面三件事——引擎自己绑一个回环-only 的临时端口 WS upgrade 监听,逐字复用 spawn 模式的 installWebSocketBridge(loopback 源准入、隧道目标 SSRF 守卫、会话生命周期),同一 pipelineFor 供 HTTP 与 WS;客户端拦截器按连接解析目标:settled 直接改写 URL 到桥,booting 用既有 DeferredWebSocket 挂起等待,bootstrap 失败只降级 WS 单通道直连(warn 一次);值表放宽为「任何非空非 off 值启用」。
  5. 是否有回归问题:逐项核过——spawn/attach 车道字节级不变(新分支以 inline 专属字段 resolveInlineWs 存在性为键,该字段只在 armNativePi(inline) 设置);426 契约保持(未认领 upgrade 仍 426,Codex fast-fallback 的 HTTP POST 照样压缩);桥端口上的普通 HTTP 返回 404;监听器 unref() 不拖住宿主进程;桥刻意不记 noteRoutedOrigin(避免对伪源站误触 The same sessionId is served by two bili processes simultaneously: interleaved logs from global + pi-native dual instanc | 同一 sessionId 被两个 bili 进程同时服务：全局 + pi-native 双实例日志交织、重复 cold-load（split-brain） #3923 split-brain 告警,注释已写明理由)。行为变更均为有意且已在 PR 正文披露:on/yes/ON/… 从静默 spawn 变为启用 inline;off 集扩为 0/false/no/off 且优先于文件配置;arm 时新增一行 info 日志。审核中发现的真缺陷(已修):WS 桥此前把裸 handle() 交给会话,若 handle() reject(仅限 last-resort 内部错误),会话 catch 吞掉后 codex 看到的是截断流而非结构化错误帧——spawn 模式同场景经 dispatch catch 渲染 503+Retry-After(Circuit-open 502 keeps an opaque error string, and connect-refused alerts never reach the host GUI | [Bug][dsh] 熔断/连接失败时客户端只见常量 "acp-proxy failure"：detail/upstreamFailure/alerts 全都没到用户眼前 #4254 形状)。两车道错误形状不一致正是本仓库纪律要防的类。已补 commit af6786fba:给桥的 dispatch 包上与 server.ts dispatch catch 相同的 egress(分类日志 + buildProxyFailureResponse 渲染),不改主修复语义。
  6. 是否破坏缓存:不涉及——未触碰缓存/账本/去重键;WS 与 HTTP 共用同一压缩决策路径。
  7. 是否改了设计方向:不涉及——这是补齐 移植 billion-context-pi 版本的非 server 模式 #3278 inline 车道缺失的 WS 通道,机制整体复用既有桥,无新架构。
  8. 是否引入新配置:不涉及——无新 env/config/flag;BILI_PI_INLINE 取值语义放宽属行为变更,第 5 问已披露旧值→新值。

验证状态:docs-sync 门禁本地实测通过(tools/gen-config-docs.mjs generate 零漂移,种子 yaml 已同步);unused-exports 修法核实安全(两个符号无任何模块外引用,测试只用 _closeInlineWsBridgeForTest 缝)。定向测试套件因本环境无 node_modules 未能本地跑,全量判定以远程 CI 为准——af6786fba 上正在跑(此前仅 docs-sync/unused-exports 两个门禁红,test 车道是被它们 need 掉取消的,现在会正常执行)。

收工判定:代码与行为审查通过,无拦下项;待 af6786f 的 CI 全绿即可合并(合并本人来)。标签: bug / pi / codex / scope/wiring / p2(首条回复已打,一句话理由:pi inline 车道 WS 流量漏压缩,功能性缺陷有绕行)。

ranxianglei pushed a commit that referenced this pull request Oct 24, 2026
ci-check
test: pass generationBoundaryActive correctly in #4305 injectSystem t…
2b8c4e9 
…est (born-red positional drift) (#4559 small fix)
ranxianglei pushed a commit that referenced this pull request Oct 24, 2026
ci-check
fix: drop internal-only exports flagged after #4572 train merge (#4559 …
4c93d52 
…small fix)

DecompositionSource (fold-decomposition-lookup.ts) and WatcherTickDecision
(server.ts) are referenced only inside their own files - zero external
usages across src/tests/kernel/pi-subagents. The unused-exports gate flags
both INTERNAL_ONLY once the #4572 train landed on master. Dropping the
export modifier is behavior-neutral (typecheck clean); StoredRow stays
exported (has an external consumer).
ranxianglei pushed a commit that referenced this pull request Oct 24, 2026
ci-check
chore(docs): regenerate config docs for compress.externalSummary row …
6056114 
…from #4572 train (#4559 small fix)

The train added the external-summary config surface but the committed
generated docs predate it, so docs-sync regenerated one new table row
(compress.externalSummary) in each of the four derived files. Mechanical
regeneration via tools/gen-config-docs.mjs - no hand edits.
ci-check added 5 commits October 25, 2026 01:14
ci-check
fix(pi): inline mode now intercepts codex Responses WebSocket traffic (…
e2a7066 
…#4526)

BILI_PI_INLINE left the Codex Responses WebSocket lane unpatched on the
false premise that "the pi lane does not use codex WS" (pi rides the
codex provider over that exact lane, #2073/#2111), so codex WS dialed the
model directly — uncompressed, no ACP session record.

- inline engine binds a loopback-only WS-upgrade listener (ephemeral
  127.0.0.1 port, unref'd) serving the same per-request pipeline through
  installWebSocketBridge verbatim (loopback-source admission, tunnel
  destination SSRF guard, 426 fallthrough parity with server.ts); a bind
  failure degrades ONLY the WS channel direct (warned) — HTTP compression
  and the engine stay healthy
- native-ws-intercept gains the inline lane: rewrites through
  state.resolveInlineWs/wsOrigin instead of the undialable pseudo-origin;
  defers connections until the engine decision settles; bootstrap failure
  degrades direct. Spawn/attach lanes byte-identical (branch keyed on the
  inline-only resolver being present)
- BILI_PI_INLINE value table: any non-empty value other than
  0/false/no/off now enables (on/yes/etc. used to fall through to spawn
  silently, reading as "inline does nothing"); off tokens expanded from
  0/false to 0/false/no/off — they now disable over the config-file
  pi.inline value too; arm-time info log makes the switch observable
- docs: CONFIGURATION.md/.zh-CN.md, LIFECYCLE.md
- tests: planNativePi truth table, WS-intercept inline seams
  (fast-path rewrite / deferred hold / degrade-direct / bootstrap
  rejection), new issue4526-pi-inline-ws integration suite (real engine
  boot + real ws client round trip through the bridge: probe + turn,
  ACP tools injected, session recorded; 404 plain HTTP; 426 wrong-shape
  upgrades)
ci-check
docs: correct stale BILI_PI_INLINE off-token comment in config.ts (#4559
5aa5833 
 small fix)

#4526 widened the explicit-off tokens from {0,false} to
{0,false,no/off}; the pi.inline doc comment in FileConfig still listed
only 0/false. Comment-only, matches planNativePi (src/agent/pi-native.ts).
ci-check
chore(ci): drop accidentally committed scratch file .tmpfailids.txt (#…
0cea480 
…4559 small fix)

Check-run id list left behind while debugging the CI failures; not part
of the change.
ci-check
fix(pi): render WS bridge dispatch failures into the envelope (#4526)
dc7d888 
Review finding on the new inline WS bridge: it passed the bare pipeline to
installWebSocketBridge, so if handle() rejected (last-resort internal error),
the session's own catch swallowed it (warn + bare end) and Codex saw a
truncated stream instead of an error frame. Spawn mode renders the failure
into the same envelope via its dispatch catch (informative error, 503+Retry-After
on a circuit-open fail-fast, #4254) before resolving. Wrap the bridge's
dispatch with the identical egress so both lanes report the same failure shape.
ci-check
test: pass generationBoundaryActive correctly in #4305 injectSystem t…
e82ccd7 
…est (born-red positional drift) (#4559 small fix)
@ranxianglei

ranxianglei commented Oct 24, 2026

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

状态更新(接上条八问结论):af6786fba 上又红了两个门禁(config-surface-guard、lock-sync)。查了日志与 master 历史,根因都不是本 PR 的代码问题——是我 rebase 之后 #4572 train 才落上 master(kernel 0.0.162→0.0.163 的 lockfile 同步、config-surface-guard 脚本自身的定位 bug、以及三个 internal-only export 的去导出),master 侧已在 4d34abfaf 一次修齐(其提交信息自认 "master-red too")。ci-worker 随后推的 3 笔小修里,2 笔(de-export、docs 再生成)与 master 那笔完全重复,另 1 笔(generation-boundary 测试位置漂移)是必要的——那是 master 自身 born-red 的测试:injectSystem 新增参数后测试调用没跟上,「active」用例把 true 传给了 mcpDialectNote 而不是 generationBoundaryActive,断言必挂。

当前处置:整支 rebase 到最新 master 146b34f27(git 自动丢弃 2 笔已上游化的重复提交,保留必要的测试修复),本地跑门禁验证后推送,CI 结果出来再报。

@ranxianglei ranxianglei mentioned this pull request Oct 24, 2026
Open
ci-check
fix: drop internal-only ClientBuildCheck export flagged by unused-exp…
8042523 
…orts (#4559 small fix)

The #4545 train added this type used only inside client-build-note.ts;
master's 4d34abf de-export sweep missed it, so every PR rebased onto
the tip inherits the red. Behavior-neutral (type only, zero external
usages).
ranxianglei pushed a commit that referenced this pull request Oct 24, 2026
ci-check
fix(gates): de-export internal-only ClientBuildCheck (inherited maste…
c560a2a 
…r-red #4602, same one-liner as #4603/#4559)
@ranxianglei ranxianglei mentioned this pull request Oct 24, 2026
Merged
ranxianglei pushed a commit to Zhishulo/billion-context that referenced this pull request Oct 24, 2026
ci-check
test: pass generationBoundaryActive correctly in ranxianglei#4305 inj…
389b815 
…ectSystem test (master born-red, ranxianglei#4599 sentinel)

The tier-5 train added generationBoundaryActive as injectSystem's 9th parameter
and updated every caller except this test's 'active' case: its trailing true
landed in mcpDialectNote, so the note never appeared and the assertion must fail.
Identical one-line fix already committed on PR ranxianglei#4559's branch (e82ccd7); drop
that commit when rebasing whichever way merges first.
@ranxianglei

ranxianglei commented Oct 24, 2026

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

CI 自动修复通道结论(attempt 2/2):本轮无需代码改动——点名的两个红门禁已在最新 head 变绿,剩余红为 master 继承性失败,等 #4606 合入后 rebase 即全绿。

查重: 不重复 —— 本帖是 PR #4559 自身 CI 的自动修复通道;CI 问题按 owner 政策统一归口 #4599(已评论一行状态),不另立 issue。
标签: bug / pi / codex / scope/wiring / p2(首条回复已打,复核无变化)。

事实核对(head 804252314,分支刚被 rebase 到最新 master 146b34f27):

八问:

  1. 是什么问题:转发点名的两个静态门禁在旧 head 6056114c6 上红;本质是 master 侧 train 漂移带来的继承红,不是本 PR 引入的缺陷。
  2. 什么原因导致的:[PR] merge: tier-4 train — dsh/cache domain rework (7 PRs incl. p1 #3307/#3301/#3890); kernel straggler from #3680 reverted per boundary #4572 train(kernel 版本推进 + config-surface-guard 脚本 bug)落 master 后破坏了这两个门禁,凡 rebase 到当时 tip 的 PR 都继承;master 4d34abfaf 修复,本分支 rebase 后消失。
  3. 影响范围与严重程度:波及所有 rebase 到 tip 的 PR(CI Control Center: Centralized CI Failure Handling & Status Sync (Comment all CI issues here; do not open new issues) | CI 总控: CI 失败集中处理与状态同步(所有 CI 问题在此评论, 勿开新 issue) #4599 已盘点);仅 CI 阻塞,零运行时/数据影响。
  4. 怎么修复的:本分支不做单独修复——继承红由 master 修复 PR [PR] fix(ci): clear the two master-red gates in one branch — unused-exports (#4602) + the #3890 LIVE_FILES tripwire (#4604) #4606 集中处理(单 writer 纪律,避免各 PR 重复修);rebase 到含修复的 master 后两门禁实测绿。
  5. 是否有回归问题:本轮未推任何 commit,无回归面;804252314 上全部静态门禁逐项核实为绿(清单见上)。
  6. 是否破坏缓存:不涉及。
  7. 是否改了设计方向:不涉及。
  8. 是否引入了新的配置:不涉及。

后续动作(唯一遗留):#4606 合入 master 后,把本分支 rebase 过去并丢弃与 #4606 重复的两个小修 commit(e82ccd7d6 generation-boundary 第 9 参、804252314 ClientBuildCheck 去 export,#4599 floor 9 已注明可丢),test 分片跑真套件,预期全绿即可合并。

收工判定:本通道无更多可做(第 2 次尝试,剩余红属等待外部合入,非本分支可修);PR 本身维持「可合并、待 CI 全绿」状态,合并由人工执行。

@ranxianglei ranxianglei mentioned this pull request Oct 24, 2026
Open
@ranxianglei

ranxianglei commented Oct 24, 2026

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

CI 状态更新(head 8042523,run 40117138820):

代码审核结论不变(floor 7 八问):方向正确、回归面干净、可合——待 CI 绿后由人合并。

ranxianglei pushed a commit to z0d0dOr/billion-context that referenced this pull request Oct 24, 2026
ci-check
fix(ci): drop the internal-only ClientBuildCheck export flagged by un…
e425e78 
…used-exports (ranxianglei#4599 inherited red)

Rebased head onto master 146b34f resolves config-surface-guard /
lock-sync / docs-sync (all stale-base drift fixed there by 4d34abf).
The one remaining gate red is the master-born-red ClientBuildCheck
(ranxianglei#4599 floor 8: the ranxianglei#4545 train added the type used only inside
client-build-note.ts; 4d34abf's de-export sweep missed it). Same
one-word fix as ranxianglei#45598042523, duplicated here per the few-line CI-fix
discipline so this PR is green without waiting for ranxianglei#4559 to merge.
Behavior-neutral: type-only, zero external usages (grep-verified).
This was referenced Oct 24, 2026
Open
Merged
Open
Open
Open
Open
Open
ranxianglei pushed a commit to z0d0dOr/billion-context that referenced this pull request Oct 24, 2026
ci-check
fix(test): pass mcpDialectNote positionally so ranxianglei#4305's bou…
5405b65 
…ndary flag reaches injectSystem

Born-red inherited from base cd92b0b (ranxianglei#4305 landed after ranxianglei#4344 added the 8th
param but its test only passed 8 positional args, so the 'on' case's trailing
true bound to mcpDialectNote and generationBoundaryActive stayed false).
Byte-identical to ranxianglei#4606 commit 389b815 / ranxianglei#4559 e82ccd7; drop on the
post-ranxianglei#4606 rebase.
Zhishulo and others added 4 commits October 25, 2026 09:35
@Zhishulo ci-check
fix(types): keep ClientBuildCheck module-private to clear the unused-…
6f4eb16 
…exports gate (#4602)
@Zhishulo ci-check
fix(ci): register the #3890 drain suite in LIVE_FILES (#4604)
79eedfd
ci-check
test: pass generationBoundaryActive correctly in #4305 injectSystem t…
701f149 
…est (master born-red, #4599 sentinel)

The tier-5 train added generationBoundaryActive as injectSystem's 9th parameter
and updated every caller except this test's 'active' case: its trailing true
landed in mcpDialectNote, so the note never appeared and the assertion must fail.
Identical one-line fix already committed on PR #4559's branch (e82ccd7); drop
that commit when rebasing whichever way merges first.
ci-check
fix(ci): suspend pages deploy push trigger while the repo has no Page…
945f993 
…s site (#4598, #4599 sentinel)

pages.yml has failed 75/75 runs since landing: actions/configure-pages@v5 gets
'Get Pages site failed ... Not Found' because GitHub Pages was never enabled on
this repo (the earlier enablement:true attempt was reverted without a recorded
reason — not re-applied here). Stop-the-bleed per #4598 option 1: drop the push
trigger, keep manual workflow_dispatch so the deploy path stays intact and no
website push red-lines master again. Final direction (re-enable Pages vs retire
the workflow vs in-install serving) awaits owner decision.
@ranxianglei ranxianglei mentioned this pull request Oct 25, 2026
Merged
ci-check added 5 commits October 25, 2026 09:58
ci-check
fix(web): restore the #/updates topbar anchor dropped by the #3536 li…
78046a5 
…ne-rewrite (#4599 sentinel)

The #3719 Updates tab stayed routed (PAGES/route/loadUpdates in client.ts)
but its topbar anchor was dropped when #3536 rewrote the whole topbar line,
making nav.updates a dead catalog key (web-i18n born-red on every PR head).
Restored at the original position (after logs); identical to the sibling fix
on the panel-blog branch (900c09c), adapted to master (no blog anchor yet).
ci-check
fix(log-mask): mask every home-root spelling at the publish boundary (#…
e59e020 
…4427 Windows red, #4599 sentinel)

maskPathsForPublish keyed off os.homedir() alone. On Windows that reads
%USERPROFILE% while git-bash-style tool output carries $HOME paths, so the
publish-boundary identity leak masked one spelling and leaked the other
(#4427 suite red on windows shards only). Now masks the deduped set of
os.homedir() + $HOME + %USERPROFILE%; POSIX behavior unchanged (values
dedupe to one root), anchored-flank semantics preserved.
ci-check
test(golden): regenerate storage-render goldens for the #4316 layer-3…
12e7753 
… restamp flag (#4599 sentinel)

Deliberate persisted-state change: 380ef4d (#4316 layer 3 PR3/3) added the
one-time refLedgerAligned boolean to session state. All four wire digests are
UNCHANGED; only the metadata section digest moved (+refLedgerAligned state
key). Regen per the suite's own protocol (justification recorded here and in
the ci-fixes PR body).
ci-check
test(snapshot-render): bring stale test doubles up to the #D5-5 windo…
177bbce 
…wed-load interface (#4599 sentinel)

#D5-5 changed buildView to call store.unifiedMessageIdRows() +
store.unifiedUncoveredRows(id, intervals) first; the pre-existing fake stores
(only unifiedTailSeqs/unifiedTailViewRows) threw TypeError, caught by the
by-design degrade net as transcript-error, turning every render-expecting
assertion red (chain 6/6, verif replay). Extended both real-JS fakes and the
symbolic harness portImpls (__method_unifiedMessageIdRows /
__method_unifiedUncoveredRows) to mirror SessionStore semantics.
ci-check
sentinel help-merge: bring ci-fixes (177bbce) into #4559 branch (#4599)
44219ec
@ranxianglei ranxianglei mentioned this pull request Oct 25, 2026
Merged
@ranxianglei

ranxianglei commented Oct 25, 2026

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

duplicate of #4669 —— 同一症状 + 同一机制:inline 模式下 codex Responses WS 流量绕过压缩,解法都是回环 WS 桥拦截。#4669(10-25)是 #4526/#4527/#4571 悬空工作的全套 rebase 重提,其第 1 个提交完整包含本 PR 的 WS 桥工作(另加断流根因修复、TUI 日志、bili pi-inline 命令、默认翻转、面板/Web 徽章)。

说明:严格按先来后到本 PR(10-24)更早,但 #4669 是其超集且被明确定位为合并载体,故在此打 duplicate 标签指向它。关不关、要不要把本 PR 独有的 BILI_PI_INLINE 取值表/可观测性细节先并过去再关,由你定。

@ranxianglei ranxianglei added the duplicate This issue or pull request already exists label Oct 25, 2026
@github-actions github-actions Bot mentioned this pull request Oct 27, 2026
Merged

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

Reviewers

No reviews

Assignees

No one assigned

Labels

bug Something isn't working codex duplicate This issue or pull request already exists p2 pi scope/wiring

Projects

None yet

Milestone

No milestone

2 participants

@ranxianglei @Zhishulo