Skip to content

release v0.1.191 - #2630

Merged
ranxianglei merged 4 commits into
masterfrom
2026-10-10_release-v0.1.191
Oct 10, 2026
Merged

ranxianglei merged 4 commits into
masterfrom
2026-10-10_release-v0.1.191

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Release PR for v0.1.191 — hotfix release shipping #2621 (dsh compaction false-positive detector fix, PR #2629).

Merge order: merge #2629 FIRST, then this PR (this branch is stacked on the fix branch; after #2629 merges, delete its branch and this PR retargets/its diff collapses to the release commits only).

Commits on this branch beyond the fix:

  1. docs(release-notes): add 0.1.191 recommended entry (#2621) — own commit per release-notes discipline
  2. release v0.1.191 — version bump ONLY (package.json)

No entry would also be acceptable (opt-in since 2026-10-04); a recommended entry was chosen because affected users (longest dsh sessions) silently lose fold state and re-pay the whole prefix repeatedly — visible enough to warrant a surfaced note, not severe enough for critical.

Pre-flight: typecheck clean, targeted test family green (35/35 + 8/8), npm run build succeeds (ESM dist 309.51 KB). Full matrix runs in CI on this PR. Per AGENTS.md §4/§5: merge and publish are human/CI-only — merging this PR triggers release.yml → build + test + npm publish + tag + GitHub Release.

@github-actions

github-actions Bot commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-10_release-v0.1.191 (39ab668)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.2848-pr.2630.23d007d

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr2630.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

[bot] 🏷 收到,开始按 §②b 对 release v0.1.191 做版本区间回归审计(窗口 v0.1.190..HEAD)。

初步状态:

全窗约 45 commits / 64 files / +2802−197,包含 kernel 变更(#2565 lone-surrogate scrub,kernel 0.0.112)与多个 dsh/pi/codex lane 变更,我按高危域分批通读后给结构化八问结论。稍后更新。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Review complete — v0.1.190..v0.1.191 full-window regression audit finished (~45 commits / 64 files, read in batches per AGENTS.md §②b; high-risk domains line-by-line).

结论先行:产品级回归 0 处;审查中发现 1 个 CI 门禁缺陷(仅 Windows、确定性、不影响发布产物)——已由 #2631(PR #2634)修复并进入本分支(39ab668)。新 head 上 e2e 各 lane 已绿,主 CI 矩阵(含 Windows)运行中。矩阵绿即可合并。

高危域逐项点名核查:

热修本体(#2629)核对: 唯一改动是 carrier gate(user+text 才扫标记);两个调用点(prepare-openai.ts:146、prepare-responses.ts:224)传入的均为带 role/contentType 的 flattened core 消息;codex 检测器未动;阈值 DSH_LOCAL_COMPACTION_MIN_MISSING=8 未动;漏判退化为 #2432 unannounced-rewrite archive 路径=安全方向。单测真值表覆盖全部 5 种真实载体,e2e 负例复现原始 FP(修前红)。正向 rebase 路径测试不变。novelty gate 按 owner 在 #2621 的裁定明确排除(会永久漏掉真实 compaction)。

本版本有意行为变更清单(旧→新,均已披露):

  1. dsh compaction 检测:扫所有重发消息文本 → 只扫 user+text 载体(本热修)
  2. 出站请求体:原样 → 四个 send seam 对 lone surrogate 半截替换 U+FFFD(仅当体含 lone half 时字节变化;因 JSON.stringify 把 lone half 渲染成六字符转义文本,序列化后 code-unit 正则不可见——故文本扫描+code-unit 扫描双层)
  3. responses-wire fork adoption:transiently degraded+重试到上限 → 真实投影(identity-hash parity corpus 钉住客户端副本与服务端管线一致);google wire:重试 → 网络调用前确定性终止;pi lineage-only 子会话:尝试网络调用 → 直接跳过
  4. dsh DeepSeek 路由:无 retryPolicy → mode: normal + MALFORMED_RESPONSE(两个 patch carrier,cordis patch 整行替换故每行重述全部默认码)
  5. dsh title-gen sidecar:fork 到 |sub:<fp> ghost 会话 → raw key/verbatim(no-tool veto + dsh header 门控,evidence-permitlist 纪律)
  6. codex window 对齐:仅 bundled 表 → 本地 models_cache.json 实时元数据 + 客户端声明的 x-bili-plugin-context-window(既有 plugin wire 约定,非新配置面;bili 永不超出 codex 自认的预算)
  7. agent-providers POST:all-or-nothing 400 → 200 partial-accept {registered[], skipped[{name,reason}]}(顶层 envelope 违规仍 400/413;reason 已消毒)
  8. compress 工具回执:summary Nch → full summary Nch,且块变化时追加一句引导模型先 search_context 再 decompress(model 可见文本,proxy lane)
  9. 新增 opt-in dump GC:默认 OFF(err-*/summary-err-* 保护,删除记 WARN)
  10. 日志掩码修复:route-change demotion 行两个 origin 都过 maskUrlForLog;新增 debug-only [usage-vs-est] 行(仅 debug 开启时)
  11. kernel 0.0.111→0.0.112(scrubLoneSurrogates + ingest scrub)——human-tier,owner 已合,kernel-change: declaration 在案

结构化八问:

  1. 是什么问题:v0.1.191 是热修发布——修 [Bug] dsh 原生压缩检测误报:历史里引用过 <compacted-summary> 即判为宿主压缩落地并 rebase ACP 状态(0.1.190) #2621:dsh native-compaction 检测器把「任何消息引用了 compaction 标记文本」误判为主机侧 compaction,误重置 ACP 折叠状态;最长会话最易中招(静默丢 fold 状态、反复重付整个前缀)。
  2. 什么原因导致的:检测器扫描范围是全部重发消息的文本,而非标记合法出现的 user+text 载体;模型 prose 引用、tool result、bili 自己的压缩摘要都会携带标记文本 → 与 ordinar
    y fold 漂移叠加越过阈值即误触发。
  3. 影响范围与严重程度:dsh 插件用户中会话内容引用过标记且历史漂移达阈值的子集;可用但压缩状态被静默重置、重复支付前缀 token——成本回归,非数据丢失。
  4. 怎么修复的:收窄扫描范围到合法载体(role=user 且 contentType=text)——在决策点做根因修复而非症状过滤;miss 的方向是安全退化。
  5. 是否有回归问题:全窗既有行为逐项审过,未发现破坏;高危模式(语义漂移、fail-fast 变吞错、阈值/时序漂移、输出格式变化)逐项核过——唯一「格式变化」项即上表已披露的有意变更 7/8/10。审查发现的唯一缺陷是下述 Windows CI 门禁,属测试环境问题,非产品回归。
  6. 是否破坏缓存:prefix cache 不受影响(head system 消息保持字节稳定);热修本身消除的正是反复重付前缀的问题。
  7. 是否改了设计方向:无架构转向;fork-adopt 扩展(responses 方言投影副本、pi replay-count 播种证据)在既有机制内,drift 防护(identity-hash parity pin)已建立。
  8. 是否引入了新的配置:有,两个 opt-in key,默认关闭、无需迁移:diagnostics.maxTotalBytes / BILI_DUMP_MAX_TOTAL_BYTES(floor 1MiB)、diagnostics.maxAgeDays / BILI_DUMP_MAX_AGE_DAYS(floor 1h)——CONFIGURATION.md 中英 + website yaml seed 均已同步文档。

审查发现的问题(已有归属,无需另立):#2610 的新测试 tests/issue2605-dsh-retry-patch.test.ts 对 checkout 出的 dsh.bundle.patch.yml 做 byte-exact 多行 includes();Git-for-Windows autocrlf 将其检出为 CRLF → win22/win24 确定性失败(assertion compaction-basic auto:false row must stay intact)。与 #1305(golden JSON)同一失败类。我独立诊断并本地定向复现(LF→true / CRLF→false)确认机制;#2631(PR #2634:.gitattributes eol=lf + 测试内 CRLF 归一化双保险)已合入 master(2d31e42)并经 39ab668 带入本分支——master 自 07:30Z 起被该缺陷拖红的 Windows leg 同时解除。注意:在 39ab668 之前的旧 head(0fa7210)上 Windows 必挂,请勿基于旧 head 判定 CI。

合并判定:代码层面可合并;等 39ab668 的主 CI 矩阵(含 Windows)绿后合并——合并触发 release.yml → build + test + npm publish + tag + GitHub Release。合并与发布为人工动作。

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant