Skip to content

release v0.1.177 - #1805

Merged
ranxianglei merged 1 commit into
masterfrom
2026-10-01_release-v0.1.177
Oct 1, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-10-01_release-v0.1.177

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

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.176

  • fix(dsh): stale verifyAttachAndRecover landings must never clobber the self-healed register

@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor Author

📦 Built Package Artifact

Branch: 2026-10-01_release-v0.1.177 (2422103)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.1778-pr.1805.bbb26ce-a2

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-pr1805.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

Review of release v0.1.177 (PR #1805)

This is a bot-created release PR (ework-agent-pr). Per protocol I did not redo the work — I fetched the branch, verified the code, audited the full version window, confirmed CI, and ran targeted local checks. Findings below.


版本窗口审计 (v0.1.176 → v0.1.177) — verified via git log v0.1.176..release + git diff --stat:

  • Window contains exactly one content change — fix(dsh): stale verifyAttachAndRecover landings must never clobber the self-healed register (PR fix(dsh): stale verifyAttachAndRecover landings must never clobber the self-healed register (#1783) #1787, commit 8665088d, touches src/agent/dsh-native.ts + tests/dsh-native.test.ts) — plus the isolated version-bump commit release v0.1.177 (24221034, changes only package.json + package-lock.json, 0.1.176 → 0.1.177).
  • The "Changes since v0.1.176" list in the PR body is complete and accurate — nothing missing, nothing extra.
  • Release discipline holds: one version / one isolated commit / one *_release-v* branch; branch is current with master (PR base sha == master HEAD); clean diff (every line serves the release). No cross-branch interaction in the window (single cohesive change + bump), so the integrated read is trivially sound.

本版本引入回归:无。

行为变更清单(旧值 → 新值 + 原因;全部限定在被修的竞态路径上,正常无竞态操作不变):

  1. 迟到的 verifyAttachAndRecover 落地只在仍持有 register 时才写(landingOwnsRegister:base 为 undefined 或仍是本链要替换的那个旧 origin)。旧:无条件写/wipe。原因:慢环境(windows loopback 探测 + spawn)下落地解析得比启动晚很多,期间 maybeRetry 可能已把 register 自愈到新 origin,旧逻辑会把它覆盖掉。
  2. unfreeze wipe 现在同时清掉 retryAt。旧:针对旧 base 设的退避在 wipe 后残留。原因:钉死在已死 base 上的 10s 墙不该卡住下一个 base 的首次自愈。
  3. registerTools manifest 失败退避只作用于真正失败的那个 base(if (register.base === base))。旧:全局 retryAt。原因:对已移走的 base 发起的失败 fetch 会把之后所有自愈冻在 10s 墙后——正是 windows-22 CI 死锁的机制。

高危模式逐项过:无 fail-fast 变吞错、无阈值/时序/输出格式漂移(除本修复外)、无持久化/wire 形状变化、无 acp-kernel pin 变更。


结构化七问:

  1. 是什么问题:v0.1.176 在 windows-22 CI 上把 [dsh] native proxyEnvOrigin() 把临时 origin 冻结进 BILLION_CONTEXT_PROXY,绕过 ensureProxyRunning() 的 instance 验活;工具调用全部 fetch failed,需重启宿主 #983 自愈测试跑死锁——attach 恢复链落地太晚,把已被自愈到新 origin 的 register 无条件覆盖并冻结。
  2. 什么原因导致的:verifyAttachAndRecover 的异步链(loopback 探测 + evidence grace + spawn)在慢环境下解析得比启动晚很多;期间 maybeRetry 可能已把 register 自愈到新 origin。迟到的落地仍按「我启动时的旧 origin」无条件写 register(wipe base/toolsReady、置全局 10s retryAt),覆盖了更好的新状态。根因是「落地不校验自己是否还持有 register」,不是某个具体字节错。
  3. 怎么修复的:引入所有权契约——落地只有在仍持有 register 时才允许写;unfreeze wipe 连带清掉针对旧 base 的退避;registerTools 的回退退避收敛到真正失败的 base。修在决策点(疏),不是过滤/改写载荷(堵)。
  4. 是否有回归问题:无。逐条清点既有行为——[dsh] native proxyEnvOrigin() 把临时 origin 冻结进 BILLION_CONTEXT_PROXY,绕过 ensureProxyRunning() 的 instance 验活;工具调用全部 fetch failed,需重启宿主 #983 自愈、pinned-target 拒绝二次 spawn、unhealthy 回退 spawn、spawn 结果落 register、manifest 失败退避——在无并发竞态的正常路径上行为完全不变;变更只落在被修的那条竞态路径上。
  5. 是否破坏缓存:不涉及。改的是 dsh attach/recover 的进程内 register 状态,不动 prefix cache、session 持久化、压缩缓存、增量游标或去重键;唯一涉及的「重试」是内部 registerTools 退避(retryAt),且是作用域更精确的收敛,属修复而非破坏。
  6. 是否改了设计方向:不涉及。同模块同数据流,仅加所有权守卫。
  7. 是否引入了新的配置:不涉及。无新 env/config/默认值。

证据(非「应该能跑」):

  • CI 全绿(head 2422103):pull_request run success(windows-22 —— 原死锁点 —— ~5.5min 正常完成,未挂死)、workflow_dispatch run success、全部 E2E lane 绿(real codex / fake-codex / native pi / opencode / dsh headless profile / hermetic registry)、build-artifact + version-guard 绿。mergeable_state: clean。
  • 本地(release 分支)npm ci + typecheck 干净;tests/dsh-native.test.ts 41/41 通过,含两个新增确定性 #1783 回归测试(均显式 ok、非 skip);npm run build 成功。

判定:可合。 Release 形式合规,窗口内唯一内容变更是打到了根因的修复且有真实回归覆盖,整个版本窗口无回归,CI 与本地均绿。合并是人类专属操作(仓库规则禁止 Agent merge)——请自行合并:#1805 ,合并后 CI 会自动发布 v0.1.177 到 npm。

@ranxianglei
ranxianglei merged commit b785c43 into master Oct 1, 2026
18 checks passed
@ranxianglei
ranxianglei deleted the 2026-10-01_release-v0.1.177 branch October 15, 2026 05:32
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