Repository navigation
[PR] release v0.1.209 - #4838
ranxianglei wants to merge 4 commits into
Conversation
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.6251-pr.4838.2a11998This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4838.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 收到,开始按发版 PR 规程做版本区间回归审计(②b)。先报接单状态: 查重: 不重复——远端只有这一条 标签: 已完成的机械核对:
审计窗口为 f161c51..master(458 commits),将分批通读全窗 + 高危域点名精读,随后给出结构化八问结论。GitHub API 当前限流,CI 状态稍后补查。 |
(ai: vllm-qwen/qwen3.8-27b) 版本窗深审完成(f161c51..master,458 commits / 400 files / +42565 −3119)。覆盖:高危域逐行精读——kernel 全部 7 个 src(0.0.161→0.0.166)、全部 8 个 workflow、存储层(store/mysql/schema/identity,含 #4677 流式迁移)、launcher、preflight、relay/stream/server/plugin/persist/config/cache-ledger/fold-reconcile/tag-echo/egress-shed/upstream-throttle/snapshot-render、update/advisory;hermes/codex-plugin 及 PR 正文点名项(#3472/#4797/#4288/#4743/#4824/#4732/#4658/#4449)逐提交核对。其余为测试(221 文件,CI 跑)、UI(src/web/*)、文档。 本版本引入回归:未发现;发现 1 处缺口已当场修进 PR + 3 处非回归残留立项。 ① 当场修进 PR(行为变更披露):master 的 ② 非回归残留(与窗口变更无关,按政策只开一个 issue:#4842,p3/scope/ci):AGENTS.md §5 与 reference/release.md 仍宣称已删除的 bugfix 应急 workflow_dispatch 存在(操作者按文档走会找不到入口);release-bugfix.yml 留有死代码(事件名条件的不可达 else 臂 + 引用已删 input 的 fast-mode 注释/判断);release-manual.yml train mode 退役后留 ~25 行不可达 shell 体。 重大行为变更清单(均为窗口内各自 PR 有意变更,旧值→新值+原因):
高危域逐项点名核查结果:自动更新(update/advisory)逐行读,自更新路径无回归;dsh(dsh-native/dsh-ledger/plugin-install)attach/give-up/msgids/fork-verdict 变更均有门控与测试,无语义漂移;lockfile/kernel 版本 bump 与 src 变更一致,file: 链接完好,pi-subagents lockfile 新增;systemd/env 模板(launcher)变更(NO_PROXY loopback 合并、aux 代理交接、继承通道剥离)均有意且有日志;网络/代理路径(relay/stream/throttle/shed)wire 保真不变量保持(tool-call arguments 字节精确、thinking 家族块不动、SSE 结构保留);发布门禁(manifest --check 过、分支名+commit message 识别正确)。 CI 状态:master 341e76c 绿(32 runs,0 失败,skip 均为正常门控 job);PR head a8efcbe 当前 39 success + 17 合法 skip + 27 运行中,0 失败。 结构化八问:
判定:可合(人工合并)。合并后 CI 自动发布 v0.1.209 + tag + GitHub Release。 |
🔶 需要决策 (ai: vllm-qwen/qwen3.8-27b) — CI-engineer run (attempt 1/3). I stopped WITHOUT pushing anything: this is not just a merge conflict — the PR is stale, and no mechanical conflict resolution has a safe outcome. Labeled Evidence (all live-verified this run):
Why I did not rebase+push: rebasing onto master forces a choice at the version line. Keep 0.1.209 → merging fires Options:
Default if undecided: C — PR stays open, labeled, untouched; nothing ships until you decide. 结构化八问(本轮停在决策点,未推任何改动):
判定:停手等决策(选项 A/B/C 如上;默认 C = 保持冻结)。 |
(ai: vllm-qwen/qwen3.8-27b) — CI-engineer re-run (same task re-dispatched while the blocker persists). I re-verified everything against live sources this run; nothing has changed, so I am taking no action on the branch again — the decision request at floor 10 stands as-is (options A/B/C, recommendation A, default C = frozen). Live state this run:
The dirty merge state will keep re-dispatching this lane until a human decides — that is expected under default C. The only safe mechanical resolution does not exist (see floor 10 for the full reasoning: version line fork → already-published npm version or unauthorized release). Awaiting your call: A close + port the acp_retrieve test row to current master (I do the port immediately on your go), B re-target the branch, or C leave frozen. 结构化八问(本轮为重复触发,无新动作):
判定:继续停手等决策(floor 10 的 A/B/C;默认 C 保持冻结)。 |
[ework] CI fix verified green ✓ |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) — Final status for this CI-engineer run (two dispatches processed, both verified live against git + labels API). Nothing was pushed; the branch is untouched; the PR stays frozen pending your decision. What I did across this run:
Awaiting your call: A (recommended) you close #4838 as superseded by #4982 and I port the single test row to current master as a small test-only PR — I start immediately on your go; B I strip the version commits and rename the head branch off the 结构化八问(本轮最终结论):
判定:停手等决策(A/B/C,默认 C 保持冻结);阻塞器在人工决策前会持续再派发本 lane,属预期。 |
[ework] CI fix verified green ✓ |
1 similar comment
[ework] CI fix verified green ✓ |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) — CI-engineer re-dispatch (third). Re-verified live this run; the decision-relevant state is unchanged, so no action on the branch — the decision request at floor 10 (options A/B/C, recommendation A, default C = frozen) still stands. Live state this run:
Why still no rebase+push: unchanged from floor 10 — the version-line fork has no safe mechanical resolution (keep 0.1.209 ⇒ merge fires Awaiting your call: A you close #4838 (superseded by #4982) + I port the single test row to current master as a test-only PR (I start immediately on your go) · B I strip the version commits and rename the head branch off the 结构化八问(第三次派发,复核无变化,无动作):
判定:继续停手等决策(floor 10 的 A/B/C;默认 C 保持冻结)。 |
[ework] CI fix verified green ✓ |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) — CI-engineer re-dispatch (fourth). Re-verified live; decision-relevant state unchanged — no action on the branch. The decision request at floor 10 (A/B/C, recommendation A, default C = frozen) still stands and is the only thing that unblocks this lane. Live state this run:
Why still no rebase+push: unchanged from floor 10 — keeping 0.1.209 in the version line would fire Awaiting your call: A close #4838 (superseded by #4982) + I port the single test row to current master as a test-only PR (start immediately on your go) · B strip version commits + rename head branch off 结构化八问(第四次派发,复核无变化,无动作):
判定:继续停手等决策(floor 10 的 A/B/C;默认 C 保持冻结)。 |
[ework] CI fix verified green ✓ |
1 similar comment
[ework] CI fix verified green ✓ |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) — CI-engineer re-dispatch (fifth). Re-verified live; decision-relevant state unchanged — no action on the branch. The decision request at floor 10 (A/B/C, recommendation A, default C = frozen) still stands and is the only thing that unblocks this lane. Live state this run:
Why still no rebase+push: unchanged from floor 10 — keeping 0.1.209 in the version line would fire Awaiting your call: A close #4838 (superseded by #4982) + I port the single test row to current master as a test-only PR (start immediately on your go) · B strip version commits + rename head branch off 结构化八问(第五次派发,复核无变化,无动作):
判定:继续停手等决策(floor 10 的 A/B/C;默认 C 保持冻结)。 |
[ework] CI fix verified green ✓ |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) — CI-engineer re-dispatch (sixth). Re-verified live; decision-relevant state unchanged — no action on the branch. Decision request at floor 10 (A/B/C, recommendation A, default C = frozen) still stands. Live state this run:
Why still no rebase+push: unchanged from floor 10 — version-line fork has no safe mechanical resolution (keep 0.1.209 ⇒ Awaiting your call: A close #4838 (superseded by #4982) + I port the single test row to current master as a test-only PR (start immediately on your go) · B strip version commits + rename head branch off 结构化八问(第六次派发,复核无变化,无动作):
判定:继续停手等决策(floor 10 的 A/B/C;默认 C 保持冻结)。 |
[ework] CI fix verified green ✓ |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) — CI-engineer re-dispatch (seventh). Re-verified live; decision-relevant state unchanged — no action on the branch. Decision request at floor 10 (A/B/C, recommendation A, default C = frozen) still stands. Live state this run:
Why still no rebase+push: unchanged from floor 10 — version-line fork has no safe mechanical resolution (keep 0.1.209 ⇒ Awaiting your call: A close #4838 (superseded by #4982) + I port the single test row to current master as a test-only PR (start immediately on your go) · B strip version commits + rename head branch off 结构化八问(第七次派发,复核无变化,无动作):
判定:继续停手等决策(floor 10 的 A/B/C;默认 C 保持冻结)。 |
[ework] CI fix verified green ✓ |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) — CI-engineer re-dispatch (ninth). Re-verified live (git fetch worked this run — the earlier TLS error was transient); decision-relevant state unchanged — no action on the branch. Decision request at floor 10 (A/B/C, recommendation A, default C = frozen) still stands. Live state this run:
Why still no rebase+push: unchanged from floor 10 — version-line fork has no safe mechanical resolution (keep 0.1.209 ⇒ Awaiting your call: A close #4838 (superseded by #4982) + I port the single test row to current master as a test-only PR (start immediately on your go) · B strip version commits + rename head branch off release-PR 八问(第九次派发,复核无变化,零推送):
|
[ework] CI fix verified green ✓ |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) — CI-engineer re-dispatch (tenth). Re-verified live; decision-relevant state unchanged — no action on the branch. Decision request at floor 10 (A/B/C, recommendation A, default C = frozen) still stands. Live state this run:
Why still no rebase+push: unchanged from floor 10 — version-line fork has no safe mechanical resolution (keep 0.1.209 ⇒ Awaiting your call: A close #4838 (superseded by #4982) + I port the single test row to current master as a test-only PR (start immediately on your go) · B strip version commits + rename head branch off release-PR 八问(第十次派发,复核无变化,零推送):
|
[ework] CI fix verified green ✓ |
2 similar comments
[ework] CI fix verified green ✓ |
[ework] CI fix verified green ✓ |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) — CI-engineer re-dispatch (eleventh). Re-verified live; decision-relevant state unchanged — no action on the branch. Decision request at floor 10 (A/B/C, recommendation A, default C = frozen) still stands. Live state this run:
Why still no rebase+push: unchanged from floor 10 — version-line fork has no safe mechanical resolution (keep 0.1.209 ⇒ Awaiting your call: A close #4838 (superseded by #4982) + I port the single test row to current master as a test-only PR (start immediately on your go) · B strip version commits + rename head branch off release-PR 八问(第十一次派发,复核无变化,零推送):
|
[ework] CI fix verified green ✓ |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) — CI-engineer re-dispatch (twelfth). Re-verified live; decision-relevant state unchanged — no action on the branch. Decision request at floor 10 (A/B/C, recommendation A, default C = frozen) still stands. Live state this run:
Why still no rebase+push: unchanged from floor 10 — version-line fork has no safe mechanical resolution (keep 0.1.209 ⇒ Awaiting your call: A close #4838 (superseded by #4982) + I port the single test row to current master as a test-only PR (start immediately on your go) · B strip version commits + rename head branch off release-PR 八问(第十二次派发,复核无变化,零推送):
|
[ework] CI fix verified green ✓ |
1 similar comment
[ework] CI fix verified green ✓ |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) — CI-engineer re-dispatch (thirteenth). Re-verified live; decision-relevant state unchanged — no action on the branch. Decision request at floor 10 (A/B/C, recommendation A, default C = frozen) still stands. Live state this run:
Why still no rebase+push: unchanged from floor 10 — version-line fork has no safe mechanical resolution (keep 0.1.209 ⇒ Awaiting your call: A close #4838 (superseded by #4982) + I port the single test row to current master as a test-only PR (start immediately on your go) · B strip version commits + rename head branch off release-PR 八问(第十三次派发,复核无变化,零推送):
|
[ework] CI fix verified green ✓ |
First master-based release since v0.1.206 — npm latest (0.1.208) was cut from the bugfix carve-out lane and does NOT contain master's work after the fork point. This PR ships master as-is: 458 commits since f161c51 (merge-base with v0.1.208), including the fix this release exists for:
{"outcome":"success"}. A new wire row pins acp_retrieve — the acceptance-list gap reported in #3472 fix not in a published release (npm latest 0.1.208): acp_retrieve also reaches the model as bare {"outcome":"success"} | #3472 的修复尚未发版(npm 最新 0.1.208):acp_retrieve 同样只剩 {"outcome":"success"} #4836.Notable among the 458 (each documented in its own PR): #4797 storage restamp identity, #4288 preflight fit-exit order, #4743 degenerate-429 governor, #4824 oversize give-up wording, #4732 Windows EBUSY teardown, #4658 hermes registry-pid adoption, #4449 codex plugin version-sync gates, CI stabilization sweeps (#4599), kernel 0.0.166 lockfile sync.
Release-branch commits (this diff vs master): one test row + the version bump + plugin-manifest sync (#4449). No code changes, no config-surface changes, no behavior change beyond what master already carries.
Closes #4836