Repository navigation
release v0.1.189 - #2451
release v0.1.189#2451
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2662-pr.2451.1d47163-a2This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2451.tgz
npm install -g packageInstall instructions are refreshed on each push. |
release v0.1.189 审查结论判定:可合(代码层面无拦截性回归)。 PR 自身 diff 干净——仅 高危域逐项点名核查
重大行为变更清单(old → new + 原因)
缓存 / 重试 / 游标影响
结构化八问
收工判定:建议合并,待 CI 转绿(当前 unstable 仅为运行中)。若 owner 想压低资源驻留,可把 |
Release review — cumulative diff v0.1.188..v0.1.189 (137 commits, 196 files, +22531/−4269)Reviewed the whole range as one diff, plus focused passes on: server extraction (handle/relay), fork adoption (#2399/#2408/#2426), dsh native-compaction rebase (#2372/#2432), kernel 0.0.107→0.0.109, and the dsh auto-update surfaces. Local verification on 64443f9: build + typecheck clean; update suites 40/40 ( Verdict: ✅ mergeable. The PR body is a version bump; everything below is a forward-fix item on new in-range features — none regress existing behavior. Fixes incoming on a follow-up branch. Major (verified in-source, follow-ups recommended)
Minor / nits
Verified clean
|
|
Forward-fix PR for the review findings above: #2460 (M1 dsh responses-lane rebase, M2 breaker-aware acp_status recovery path, M3 tool-xml gap-average corroborator, + relay URL-masking and bootSmoke windowsHide nits). All targeted suites green locally (tsc, 38/38 compaction, e2e-native-dsh 2/2, update 12/12, responses-lane neighbors 62/62). |
PR #2460 审查结论(前向修复)先说明:收到你的评审后我正在本地实现同样的修复(分支 总体:✅ 可合(待 CI 转绿)。 PR 基于最新 origin/master(无需 rebase,领先 4 commit / 8 文件 +518 −29,含 3 个测试文件)。3 个 Major + 2 个 nit 全部正确,各自只在其目标窄窗口生效,无回归。 逐条核验
结构化八问
#2460 未覆盖、建议单独跟踪(均来自你这轮评审的 Minor/nits)
这三者分属不同机制,按「一 issue 一机制」宜分开。建议:#2321 我可开一个小而独立的 follow-up PR(精确、安全相关、~3 行 header + 测试);#2394 与 fork 簇立 tracking issue 或并入后续。等你一句话,我就动手;在此之前不动它们,以免又和你在做的东西撞车。 收工判定:#2460 建议合并(待 CI 绿)。我的重复本地工作已清理,无并行 PR 冲突。 |
状态再确认(此条与你之前的发版评审同内容,已处理;同步现状)
当前工作区干净,无并行 PR。等你对这 3 项的决定。 |
#2460 CI 现已全绿(独立复核)复核你新推的 head 那个失败我本地独立复现过: → 我之前「#2460 可合(待 CI 转绿)」的保留项现已解除:代码层面 + CI 均通过,#2460 可合。 仍等你一句话的 3 项(#2460 未覆盖):
建议不变:#2321 开独立小 PR(精确、~3 行 header + 测试);后两者立 tracking item。你拍板我就动手,在此之前不擅自开工。当前工作区干净,无并行改动。 |
The armed/pre-armed suppression of the Compressible-ranges list is gone. The table is live by construction — buildCompressibleRanges (kernel/src/ recommend.ts) derives refs from the CURRENT resent view only, after screening covered/media/protected/withdrawn messages — so an advertised range always anchors, and hiding it behind failure-cause policy only produced contradictions: - armed on substrate-destruction, the receipt orders "run acp_status once, then compress ONLY a range it currently reports" — suppression made that promised recovery unreachable (#2451 review M2, the #2360 two-orders shape); - armed/pre-armed on stale-ref, the failed refs were the model's stale INPUT, not the table — suppression hid the very remedy. acp_status now reports the table unconditionally and carries no order of its own: substrate-destruction attribution keeps the receipt's recovery line; every other cause mirrors the receipt's STOP order ("do not attempt to compress now; continue the task"). Anti-loop pressure stays where it belongs — in the receipts. tests: armed (unknown cause / stale-ref / substrate) and pre-armed (n=1/2) all assert the table stays up, the matching annotation renders, and no SUPPRESSED claim appears anywhere.
fix(#2451): address review findings M1–M3 + two nits
…ses lane too The ranxianglei#2432 dsh local-compaction rebase landed on the openai lane only, while CONFIGURATION.md names responses "the lane dsh desktop's compaction actually rides" (ranxianglei#2360). A dsh-bound session replaying [checkpoint summary, retained tail…] on this wire kept the pre-ranxianglei#2432 death spiral: partially-alive blocks, self-destructing fold anchors, every later compress failing to anchor (ranxianglei#2451 review M1). prepare-responses.ts now runs the same detector as prepare-openai.ts: dsh-bound session (metadata.pluginAgent === "dsh") + checkpoint framing in a resent message (carriesDshLocalCompactionSummary) + decimated fold coverage (missing >= DSH_LOCAL_COMPACTION_MIN_MISSING and >= half the covered set) -> markNativeCompactionBoundary + reconcile back-to-back, re-seeding refs onto the compacted view in the SAME turn. The codex detector (ranxianglei#2372) is preserved verbatim on its own lane branch; decimated coverage without either producer's framing stays on the churn paths. Folds in the new e2e are driven through POST /__bili/plugin/tool — plugin mode suppresses the compress loop, so the model-fold fixture from the codex tests cannot drive a dsh-bound session. Negatives pin: intact history with framing (paste analog), a session never dsh-bound, and foreign (codex) framing on a dsh-bound session.
Auto-fallback from the one-click release workflow: direct push to master was blocked by branch protection. Merging this PR publishes via the standard release.yml flow.
Changes since v0.1.188