Skip to content

[PR] Four-lane shared startup lifecycle wrap-up: dsh adopts lane mutual exclusion guard, thick lifecycle retained in place (# | 四车道共享启动生命周期收尾:dsh 采用车道互斥守卫,厚生命周期保留原地(#5241 阶段 1 / PR-1d) - #5248

Open
ranxianglei wants to merge 2 commits into
2026-10-30_native-attach-opencodefrom
2026-10-30_native-attach-dsh

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

(ai: zai/glm-5.3)

Refs #5241(阶段 1 / PR-1d,不 Closes)|叠在 #5247 之上(合并顺序:#5242 → #5244 → #5246 → #5247 → 本 PR)

这个 PR 做什么:阶段 1 的最后一刀,也是对方案的一处诚实修正:dsh 不迁移到共享实现,只采用共享的车道互斥守卫 armNativeLane("dsh")(挂在 apply() ——dsh 的车道归插件生命周期所有,同车道重新激活合法)。至此四条车道都被 one-lane-per-process 契约显式覆盖。

为什么 dsh 不迁(原方案说"独有差异走 spec 钩子",实施时发现钩子化不成立):

验收:issue3544(dsh 轮换全套)20/20、issue4811 9/9、issue4755 1/1、桩矩阵 3/3 一行未改、守卫单测 3/3、tsc 干净。dsh verify 逻辑体零改动(diff 只有 import + apply() 里 5 行守卫 + 注释)。

阶段 1 至此四刀齐:PR-1a pi(#5244)→ PR-1b omp(#5246)→ PR-1c opencode(#5247)→ PR-1d dsh(本 PR)。合完这批,#5241 可进阶段 2(闩锁治理:shadow 三振闩/stderr-dead 闩的可告警可恢复有 TTL 化,桩在 #5242 已冻结现状)。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

查重: 不重复。 本 PR 是 #5241 阶段 1 系列的第四刀(PR-1a #5244 / PR-1b #5246 / PR-1c #5247 / PR-1d 本 PR,GitHub 侧编号 PR #5248),按伞 issue 设计分阶段推进;检索近期 open PR,无第二个条目处理同一车道互斥机制。

标签: 建议 dsh / scope/wiring / p3(dsh 车道启动守卫、协议接线层、内部重构无用户可见变更)。说明:平台标签 API 在本环境未实现(endpoint not implemented in ework shim),无法经 API 落标,留系统/owner 补。

审核结论(独立重审,非照抄 PR 描述;先一句白话:这个 PR 让 dsh 客户端的启动流程采用共享的「一个进程只允许一条车道」互斥守卫——同一进程里想同时激活两条不同客户端车道,现在会立刻报错,而不是静默互相覆盖对方的代理配置;dsh 自己的厚生命周期逻辑保留原地不迁移)。

八问:

  1. 是什么问题:[Design] Host contract v2: pin behavior with stubs first, then unify lifecycle / capability declaration / degradation re | [Design] 宿主契约 v2:先打桩固定行为,再统一生命周期/能力声明/降级恢复/入口实测(讨论通过后才动工)| [Design] Host contract v2: pin behavior with tests first, then unify lif… #5241 阶段 1(四条客户端车道的启动生命周期统一)最后一刀。原方案四条全迁共享实现,实施中发现 dsh 的启动校验是厚状态机、钩子化不成立,本刀把范围收敛为:dsh 只采用共享的车道互斥守卫,厚生命周期原地保留。
  2. 什么原因导致的:四条车道历史上逐字复制了同一段约 90 行的启动校验代码,同类缺陷跨车道反复复发(端口钉死 plugin install opencode 把 ephemeral origin 冻结进 BILI_MCP_PROXY,短路 mcp.ts 已有的验活发现;native 用 port:0 使错配必然(#403 遗留实例) #926→[Bug][omp lane] lane port moves under live omp hosts, and the host's cached proxy hop survives re-targeting — every Anthropic turn dies (connection refused / SELF_SIGNED_CERT_IN_CHAIN) #4566→[Bug][claude] plugin install pins MCP face to base port 18787; lane drift leaves ACP tools unreachable (same class as #926) #5127;冷启动工具缺失 In each new session, the first turn carries no ACP tools: the second turn triggers a full prefix recomputation, and the | 每个新会话第 1 拍没带 ACP 工具:第二拍整前缀重算,前缀缓存每次冷启动断一次 #4134→Pi RPC native package: ACP tools absent on first request to local OpenAI-compatible provider #4998→[Bug][claude] MCP shim gives up on tools/list before a cold claude-lane proxy is listening — per-message hosts (CloudCLI) lose compress tools | 冷启动时 MCP shim 等不到 proxy,CloudCLI 这类每条消息新起 claude.exe 的宿主拿不到压缩工具 #5001→bug(hermes): /acp and plugin tools disappear entirely after cold start — register() blocks beyond the host's 10s load bu | bug(hermes): 冷启动后 /acp 与插件工具整体消失——register() 阻塞超过宿主 10s 加载预算被丢弃 #4641)。统一的前提是「一进程一车道」,而这个前提此前靠部署巧合维持——两条车道若真同进程共存,会静默互相覆盖代理环境变量与 fetch 拦截([PR] Boot contract stubbing: four-lane verifyAttachAndRecover behavior matrix + latch permanence + health glossary (#5241 Pha | 启动契约打桩:四车道 verifyAttachAndRecover 行为矩阵 + 闩锁永久性 + health 词汇表(#5241 阶段 0,只加测试) #5242 阶段 0 已观察到)。本刀把它变成显式契约。
  3. 影响范围与严重程度:内部重构,正常部署零用户可见变化(每个宿主进程只加载一条车道的 bundle,已核对 tsup 入口与 launcher 引用)。仅「双车道同进程」误配置下行为变化。严重度:内部实现,误配置时 fail-fast。
  4. 怎么修复的:dsh 的 apply() 在 off 开关之后调用共享的 armNativeLane("dsh")(同车道重新激活合法,异车道抛错);守卫本体与单测由 PR-1a([PR] Four-lane shared startup lifecycle, Step 1: migrate pi lane into native-attach (#5241 Phase 1 / PR-1a, pure relocation) | 四车道共享启动生命周期第一步:pi 车道迁入 native-attach(#5241 阶段 1 / PR-1a,纯搬运) #5244)引入,本刀只加挂钩点 + 双向交叉引用注释(两个文件都写明「勿顺手补完迁移」),并把共享实现的头注释从「四份拷贝」更正为「三份」。
  5. 是否有回归问题:逐项清点——① dsh verify 逻辑体零改动(diff 只有 import + 5 行守卫 + 注释);② off 模式在守卫前早退、不 arm,kill-switch 路径不受影响;③ 同车道重激活(issue2101)合法,绿;④ 桩矩阵(contract-v2-stake-verify-attach)一行未改,S1/S2/S3 全绿;⑤ issue3544 轮换全套、issue4811、issue4755 本地批量运行 0 失败;⑥ 跨车道测试进程(issue3304)已有测试专用复位点,不受影响;⑦ 本地在 PR 头跑了 22 个车道相关测试文件 579/579 绿 + tsc 干净;⑧ CI 在头 80418ff 上 14/14 gate 绿(real-client e2e 车道按设计 skip,受 env/文件清单门控)。一处有意语义变更见下方披露。
  6. 是否破坏缓存:不涉及(未触碰缓存/重试/增量游标/去重键)。
  7. 是否改了设计方向:有一处诚实修正——原方案说「四车道全迁、独有差异走 spec 钩子」,本刀判定 dsh 不迁:钩子化不成立(dsh attach mode test intermittently fails on Windows CI: the async recovery flow reverts the registered origin back to i | dsh attach 模式测试在 Windows CI 偶发红:异步恢复流程把注册 origin 改回旧值(测试隔离竞态) #3616 世界代数检查点每个分支不同,spawn 落地只查 gen——[dsh] native proxyEnvOrigin() 把临时 origin 冻结进 BILLION_CONTEXT_PROXY,绕过 ensureProxyRunning() 的 instance 验活;工具调用全部 fetch failed,需重启宿主 #983/release v0.1.176 #1783 自愈契约要求迟到的 spawn 落地能给已放弃的 register 重新定基;安装新版本后旧代理永远不换新:detach 代理躲过应用退出,重启只是重新挂上旧进程(「永远更新不了」) #3544 轮换在任何过期检查之前发客户端事件;dsh 发布面是 register 而非 env)。共享收敛到真正的跨车道契约(互斥守卫、bug: dsh-native — attach 目标瞬时不可达 → 回退 spawn 第二实例:routed baseURL 下工具/模型通道必然脑裂(工具 404 → preflight 502 → 会话不可自愈) #1365 优先级链、探活/等待原语);两边文件都有交叉引用注释防止后人「顺手补完」。属范围收窄,方向不变(阶段 2 闩锁治理不受影响)。
  8. 是否引入新配置:无。

行为变更披露(旧→新+原因):旧行为 = 同一进程内两条不同车道静默互相覆盖 BILLION_CONTEXT_PROXY/fetch 拦截(数据损坏级);新行为 = 第二条车道的 apply() 立刻抛出带明确信息的错误(fail-fast)。触发条件 = 仅限双车道同进程的误配置或测试中刻意共载(测试走 _resetArmedLaneForTest),正常部署不可达。原因:把隐式部署假设变成显式契约,杜绝静默损坏。

顺手小修(已推标注 commit):dsh-native.ts 拆分注释写「the armNativeLane guard above」,但实际调用点在注释下方约千行的 apply() 里——措辞与代码事实不符,已改为「(armed in apply())」。commit c429f65(纯注释,3+/2-,守卫单测复跑绿),CI 正在新头上重跑。

判定:可合。 合并顺序约束:须排在 #5242→#5244→#5246→#5247 之后(叠在 #5247 之上)。合并动作留给 owner。

ranxianglei pushed a commit that referenced this pull request Nov 9, 2026
…led (#5248)

The bundle patch's static 'compaction-basic -> auto:false' line kept
applying whenever the billion-context bundle was mounted — including
while bili-native was disabled or dead (no process verdict). Non-web
profiles therefore lost their native auto-compaction permanently after a
market disable; disabling no longer reversed to stock as documented in
#3662.

The gate transform now undoes exactly that line when no active verdict
exists: only the host-plane compaction-basic entry, only when the patch
armed it (auto === false). The declarative line stays in the patch as a
fail-safe (gate entry fails to load while bili-native loads => host
plane stays stood down). A user's own manual auto:false on that row is
indistinguishable at this layer and is restored too (documented edge);
if a dsh build never fires the internal/config hook for that entry, this
degrades to the old behavior.

Closes #5248
ranxianglei pushed a commit that referenced this pull request Nov 10, 2026
…tion

Resolve the #5994 merge conflict in docs/clients.zh-CN.md by taking the
union of both intents: keep this branch's #5248 host-plane restore clause
in the launcher bullet, and take master's #5838 Codex-Responses-WebSocket
updates (Profile-install bullet + two new bullets) verbatim. No code was
touched — the only hand-resolved file is markdown; all four PR code/test
files are byte-identical to the pre-merge head.
@ranxianglei
ranxianglei force-pushed the 2026-10-30_native-attach-opencode branch from 6052fa7 to 872e45e Compare November 12, 2026 18:09
@ranxianglei ranxianglei changed the title [PR] 四车道共享启动生命周期收尾:dsh 采用车道互斥守卫,厚生命周期保留原地(#5241 阶段 1 / PR-1d) [PR] Four-lane shared startup lifecycle wrap-up: dsh adopts lane mutual exclusion guard, thick lifecycle retained in place (# | 四车道共享启动生命周期收尾:dsh 采用车道互斥守卫,厚生命周期保留原地(#5241 阶段 1 / PR-1d) Nov 12, 2026
ranxianglei and others added 2 commits November 13, 2026 03:54
#5241 phase 1, PR-1d)

Final slice of the approved phase-1 plan. dsh does NOT migrate onto the
shared native-attach.ts lifecycle — closing the loop on the plan's "dsh's
extras go through spec hooks" with what the code actually shows: dsh's
verifyAttachAndRecover is a thicker state machine, not a parameterization
of the thin one. #3616 world-generation checks sit at different points per
branch (landings check giveUpSeq; the spawn landing checks ONLY the gen —
register), #3544 rotation emits client events before any staleness check,
and the register — not the env — is dsh's publish surface. Branch-hook
transposition would spread one coherent state machine across two files
with subtly mismatched check points.

What dsh DOES adopt from the shared module: armNativeLane("dsh") at its
arm point (apply() — the plugin lifecycle owns the lane; re-activation of
the same lane stays legal), making the one-lane-per-process contract
explicit on all four lanes. Both files now cross-reference the deliberate
thin/thick split so nobody "finishes" the migration by accident. The
divergence stays frozen by issue3544 (20/20) and the phase-0 stakes (3/3,
untouched).
@ranxianglei
ranxianglei force-pushed the 2026-10-30_native-attach-dsh branch from c429f65 to 81fb1dc Compare November 12, 2026 20:02
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

CI 工程师冲突处理完成 — PR #5248(head 分支 2026-10-30_native-attach-dsh)的 merge conflict 已解决,CI 绿,mergeable 由 dirty 转 clean。

冲突原因(先一句白话):这不是代码逻辑冲突,是堆叠 PR 的 base 漂移。base 分支(2026-10-30_native-attach-opencode,即 #5247 的分支)在 11-12 被 rebase 到了更新的 master——收编了 #6260/#5441/#6186/#5774/#6166/#6150 等一大批新提交,pi/omp/opencode 三个迁移 commit 的 SHA 全变了;而 head 分支还停在旧 master 基线上,head 里那三个 pi/omp/opencode 迁移 commit 仍是旧 SHA,与 base 的新版本逐字冲突。

怎么修的:把 head 独有的两刀 dsh commit cherry-pick 到当前 base 上,丢弃 head 里那三个已被 base 收编的旧 pi/omp/opencode commit:

  • 80418ff9d2 dsh 守卫(armNativeLane 挂钩 + 交叉引用注释)
  • c429f6541f 注释修正(「the armNativeLane guard above」→「(armed in apply())」)

唯一一处冲突在 dsh-native.ts 的 import 区:base 的 native-intercept import 行已演进(bodyProvablyOverWindow→bodyOverWindowDetail,且多了 model-endpoints / fetch-chain / ws-intercept 三个 import)。解法 = 保留 base 全部 import,在其后插入 import { armNativeLane } from "./native-attach.js";。native-attach.ts 的头注释改动无冲突直接落地。

结果:

  • head:c429f6541f → 81fb1dc910(force-with-lease,旧 head 无他人改动)
  • 相对 base 的 diff 收敛到 2 文件 / +36 -6(dsh-native.ts +24、native-attach.ts +18),正是 dsh 守卫本体
  • mergeable:clean(原 dirty)
  • CI(镜像缓存):15 项全 completed,0 failed / 0 pending(8 条 real-client e2e 车道按 env/文件清单门控 skip,其余 gate 全绿)
  • 本地定向验证:typecheck 干净 + lane-guard / issue3544 / contract-v2-stake-verify-attach / issue3304 共 49/49 绿

八问:

  1. 是什么问题:堆叠 PR 的 merge conflict——base([PR] Four-lane shared startup lifecycle Step 3: opencode lane migration (#5241 Phase 1 / PR-1c, pure move) | 四车道共享启动生命周期第三步:opencode 车道迁入(#5241 阶段 1 / PR-1c,纯搬运) #5247 分支)被 rebase 到新 master 后,head([PR] Four-lane shared startup lifecycle wrap-up: dsh adopts lane mutual exclusion guard, thick lifecycle retained in place (# | 四车道共享启动生命周期收尾:dsh 采用车道互斥守卫,厚生命周期保留原地(#5241 阶段 1 / PR-1d) #5248)没跟着 rebase,两者逐字冲突。
  2. 什么原因导致的:base 分支 11-12 前进(收编了 master 上一批 PR),head 停在旧基线;head 里的 pi/omp/opencode 迁移 commit 是旧 SHA,与 base 新版本冲突。属堆叠 PR 的常规 base 漂移,非代码缺陷。
  3. 影响范围与严重程度:仅本 PR 的合并状态(dirty→clean),不影响任何已发布行为。严重度:合并阻塞,已解除。
  4. 怎么修复的:cherry-pick head 独有的两刀 dsh commit 到当前 base,丢弃已被 base 收编的三个旧 pi/omp/opencode commit;唯一 import 冲突按「保留 base + 插入 armNativeLane 导入」解。
  5. 是否有回归问题:无。dsh 守卫逻辑体零改动(仍是 import + apply() 里 5 行 + 注释);base 的 dsh-native.ts 新特性(pf-channel / fetch-chain / [perf][dsh] 25.8-32.7 s of each step elapses before bili sees the body (bili itself: 5.5-7.2 s) | TTFT 归因:每步 25.8-32.7 s 发生在 bili 收到请求体之前 #5792 body-memo / [Bug][dsh] Model requests silently bypass the compression proxy (fail-open gate) — 927K-token prompt sent raw, 1-token reply, session bricked with 400 #5613 dual-tier / dsh Long-Session Drift Comprehensive Remediation: Sealing the Last Leak Window for Native Compression Local Deployment + | dsh 长会话漂移综合治理:堵死原生压缩本地落地的最后漏窗 + 会话身份分叉可见化与自愈 #5686 latch / [Bug][DSH] Codex auto/WebSocket bypasses native fetch interception while compaction is disabled #5838 WS)全部保留,只在其上叠加 armNativeLane 调用。typecheck + 49 定向测试绿。
  6. 是否破坏缓存:不涉及(未触碰缓存 / 重试 / 增量游标 / 去重键)。
  7. 是否改了设计方向:无。dsh 不迁移厚生命周期、只采用 armNativeLane 守卫的决策不变;两边交叉引用注释保留。
  8. 是否引入新配置:无。

判定:冲突已解,CI 绿,mergeable=clean,可合。 合并顺序约束不变(须排在 #5242 → #5244 → #5246 → #5247 之后);合并动作留给 owner。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

CI 工程师冲突处理完成 — PR #5248(head 分支 2026-10-30_native-attach-dsh)的 merge conflict 已解决,CI 绿,mergeable 由 dirty 转 clean。

冲突原因(先一句白话):这不是代码逻辑冲突,是堆叠 PR 的 base 漂移。base 分支(2026-10-30_native-attach-opencode,即 #5247 的分支)在 11-12 被 rebase 到了更新的 master——收编了 #6260/#5441/#6186/#5774/#6166/#6150 等一大批新提交,pi/omp/opencode 三个迁移 commit 的 SHA 全变了;而 head 分支还停在旧 master 基线上,head 里那三个 pi/omp/opencode 迁移 commit 仍是旧 SHA,与 base 的新版本逐字冲突。

怎么修的:把 head 独有的两刀 dsh commit cherry-pick 到当前 base 上,丢弃 head 里那三个已被 base 收编的旧 pi/omp/opencode commit:

  • 80418ff9d2 dsh 守卫(armNativeLane 挂钩 + 交叉引用注释)
  • c429f6541f 注释修正(「the armNativeLane guard above」→「(armed in apply())」)

唯一一处冲突在 dsh-native.ts 的 import 区:base 的 native-intercept import 行已演进(bodyProvablyOverWindow→bodyOverWindowDetail,且多了 model-endpoints / fetch-chain / ws-intercept 三个 import)。解法 = 保留 base 全部 import,在其后插入 import { armNativeLane } from "./native-attach.js";。native-attach.ts 的头注释改动无冲突直接落地。

结果:

  • head:c429f6541f → 81fb1dc910(force-with-lease,旧 head 无他人改动)
  • 相对 base 的 diff 收敛到 2 文件 / +36 -6(dsh-native.ts +24、native-attach.ts +18),正是 dsh 守卫本体
  • mergeable:clean(原 dirty)
  • CI(镜像缓存):15 项全 completed,0 failed / 0 pending(8 条 real-client e2e 车道按 env/文件清单门控 skip,其余 gate 全绿)
  • 本地定向验证:typecheck 干净 + lane-guard / issue3544 / contract-v2-stake-verify-attach / issue3304 共 49/49 绿

八问:

  1. 是什么问题:堆叠 PR 的 merge conflict——base([PR] Four-lane shared startup lifecycle Step 3: opencode lane migration (#5241 Phase 1 / PR-1c, pure move) | 四车道共享启动生命周期第三步:opencode 车道迁入(#5241 阶段 1 / PR-1c,纯搬运) #5247 分支)被 rebase 到新 master 后,head([PR] Four-lane shared startup lifecycle wrap-up: dsh adopts lane mutual exclusion guard, thick lifecycle retained in place (# | 四车道共享启动生命周期收尾:dsh 采用车道互斥守卫,厚生命周期保留原地(#5241 阶段 1 / PR-1d) #5248)没跟着 rebase,两者逐字冲突。
  2. 什么原因导致的:base 分支 11-12 前进(收编了 master 上一批 PR),head 停在旧基线;head 里的 pi/omp/opencode 迁移 commit 是旧 SHA,与 base 新版本冲突。属堆叠 PR 的常规 base 漂移,非代码缺陷。
  3. 影响范围与严重程度:仅本 PR 的合并状态(dirty→clean),不影响任何已发布行为。严重度:合并阻塞,已解除。
  4. 怎么修复的:cherry-pick head 独有的两刀 dsh commit 到当前 base,丢弃已被 base 收编的三个旧 pi/omp/opencode commit;唯一 import 冲突按「保留 base + 插入 armNativeLane 导入」解。
  5. 是否有回归问题:无。dsh 守卫逻辑体零改动(仍是 import + apply() 里 5 行 + 注释);base 的 dsh-native.ts 新特性(pf-channel / fetch-chain / [perf][dsh] 25.8-32.7 s of each step elapses before bili sees the body (bili itself: 5.5-7.2 s) | TTFT 归因:每步 25.8-32.7 s 发生在 bili 收到请求体之前 #5792 body-memo / [Bug][dsh] Model requests silently bypass the compression proxy (fail-open gate) — 927K-token prompt sent raw, 1-token reply, session bricked with 400 #5613 dual-tier / dsh Long-Session Drift Comprehensive Remediation: Sealing the Last Leak Window for Native Compression Local Deployment + | dsh 长会话漂移综合治理:堵死原生压缩本地落地的最后漏窗 + 会话身份分叉可见化与自愈 #5686 latch / [Bug][DSH] Codex auto/WebSocket bypasses native fetch interception while compaction is disabled #5838 WS)全部保留,只在其上叠加 armNativeLane 调用。typecheck + 49 定向测试绿。
  6. 是否破坏缓存:不涉及(未触碰缓存 / 重试 / 增量游标 / 去重键)。
  7. 是否改了设计方向:无。dsh 不迁移厚生命周期、只采用 armNativeLane 守卫的决策不变;两边交叉引用注释保留。
  8. 是否引入新配置:无。

判定:冲突已解,CI 绿,mergeable=clean,可合。 合并顺序约束不变(须排在 #5242 → #5244 → #5246 → #5247 之后);合并动作留给 owner。

ranxianglei pushed a commit to resec/billion-context that referenced this pull request Nov 18, 2026
…missed (ranxianglei#7112)

8461f55 moved the entry-like object to the first parameter in most
mock calls but left two issue3662 sites still passing it as `this`
(mw.call(PRESET_SELF, null, next)) — they only stay green because their
assertions are name-independent, so the broken binding survives exactly
where a future name-keyed branch (e.g. ranxianglei#5994's ranxianglei#5248 restore) would be
exercised. Move those two calls to the real binding and rename the
identifiers that now lie (PRESET_SELF/self/raw → the fiber they carry),
so the mocks cannot silently drift back to the pre-ranxianglei#7112 convention.
ranxianglei pushed a commit that referenced this pull request Nov 18, 2026
cordis dispatches `internal/config` with `this` bound to null and the
Fiber as the first listener argument (a string event name never becomes
a thisArg). The #5248 restore-auto check read `this?.entry?.options?.name`,
which is therefore always undefined, so the host-plane compaction-basic
`auto:false` line was never undone after a bili-native disable — #5248
was a no-op. The #4147 telemetry entry name suffered the same (always
"unnamed-entry").

Read the entry name from the first param (matching bili's own
CompactionDisableHost.on listener type `(raw, next)` and the dsh-native.ts
handler convention). The tests now dispatch the middleware the way cordis
does — `mw.call(null, fiber, next)` — so the #5248 case reproduces the
original no-op and pins the fix.
ranxianglei pushed a commit that referenced this pull request Nov 18, 2026
…ore path

Four unqualified "off everywhere" claims (README en/zh, docs/clients en/zh)
contradicted this PR's own behavior: a disabled bili-native restores stock
dsh auto-compaction (static auto:false flipped back to auto:true by the
gate). Each note now scopes the claim to "while bili-native owns the lane"
and points at the restore (#5248).
ranxianglei pushed a commit that referenced this pull request Nov 18, 2026
The PR was authored against the e-work mirror, where the user issue is
#5248; on GitHub the user issue is #5245 (GitHub #5248 is an unrelated
open PR). All 18 in-PR references (docs en/zh, code comments, patch yml
comment, test names) now use the GitHub number so they resolve to the
right thread. The PR body's 'Closes #5248' line is the author's to fix.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant