Skip to content

[PR] ci-fixes -> master: converge master CI gate fixes (#4599 #5860 golden realignment) - #5879

Merged
ranxianglei merged 4 commits into
masterfrom
ci-fixes
Nov 8, 2026
Merged

ranxianglei merged 4 commits into
masterfrom
ci-fixes

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

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

Convergence batch for the #5860 phantom-pressure-guard born-red wave — the MECHANICAL part (F1+F2); master synced through 5af5f9fed3.

Contents

Both suites verified green locally under the CI preload env (tests/preload-test-env.mjs pins BILI_MESSAGE_TIMESTAMPS=0): golden-storage-render + wire-contract-golden 10/10.

Known remaining red — DO NOT MERGE until resolved

F3 of the same wave: six estimate-grade nudge pins (silent-backend-nudge x3, fork-nudge-trigger x2, issue4241-judge-render-baseline x1) stay red until the owner adjudicates A/B/C in the decision thread (PR #5859 / mirror #5861, tagged needs-decision). Per-lane status: mirror cache. After the ruling lands, its fix rides onto this branch before merge.

ework-agent added 2 commits November 7, 2026 18:58
…ted-state shape

#5860 added compress.requireUsageSampleForPressure; the resolved Config snapshot persisted in session.metadata["effectiveConfig"] (src/session.ts cloneSafe) grew by exactly that field, so the metadata section digest drifts deterministically on every lane (F1 of the #5860 born-red wave, signatures pinned in #4599). Regenerated all four snapshots at 5af5f9f with scripts/update-storage-render-goldens.ts; state/blockContents/stats sections unchanged, no behavior change - snapshot realignment only. Verified green under the CI preload env (BILI_MESSAGE_TIMESTAMMS=0 via tests/preload-test-env.mjs).
…ract kernel.json

buildKernelGolden() serializes behavior.defaultConfig100k = defaultConfig(100_000); #5860's additive NudgeConfig field broke the canonicalized snapshot (F2 of the #5860 born-red wave). Regenerated with scripts/update-wire-contract-goldens.ts: diff is the single additive field requireUsageSampleForPressure: true in the nudge section - the ledger grows, nothing shrinks (Kernel Boundary rule 4).
@ranxianglei ranxianglei changed the title ci-fixes -> master: converge master CI gate fixes (#4599 #5860 golden realignment) [PR] ci-fixes -> master: converge master CI gate fixes (#4599 #5860 golden realignment) Nov 7, 2026
@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: ci-fixes (1f63882)

Latest build — install this exact version

npm install -g billion-context@0.0.8575-pr.5879.eef4aa9

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

Recent builds (commit → version)

commit version build
1f63882 billion-context@0.0.8575-pr.5879.eef4aa9 build
d7769ca billion-context@0.0.8536-pr.5879.82ffab5 build
6436b23 billion-context@0.0.8493-pr.5879.075083e build

Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr5879.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

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

Tree-identical duplicate of #5868 — please close this one.

This PR was cut by the #4599 sentinel as the standing ci-fixes→master convergence vehicle for the #5860 golden realignment (F1 storage-render ×4 + F2 wire-contract kernel.json). After opening it, I compared heads: #5868 (3cf33ec6c) and this branch (6436b23b3) produce byte-identical content in all five golden files, and git diff between the two full trees is empty — same master base, same regen output, different commits.

First-come order favors #5868 (opened earlier). Content-wise either merge lands exactly the same bytes; per the no-duplicate-PR discipline the later one should be retired. Agents may not close PRs — owner: please close #5879 as duplicate of #5868 (or vice versa, your call). No further work will be stacked on this branch.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

复核完,结论不变:#5879 与 #5868 是同一份 F1+F2 golden 重对齐的两个载体,建议关掉后开的 #5879。

新增核实(不重复上一楼的本地 diff):两个 PR 改动的文件集完全一致——同样是这 5 个文件且均为 modified:tests/golden/storage-render/{anthropic,chat,google,responses}.json + tests/golden/wire-contract/kernel.json,无一方独有文件;同 master 基线,#5868(3cf33ec,08:54Z 开)早于 #5879(6436b23,11:05Z 开)。先来后到 → 留 #5868。

补一点上一楼没说清的:关 #5879 不会丢东西。 F3 那六个 estimate-grade nudge pin 的红属于另一条决策线,裁决之后它的机械修复落到「存活的那个载体」即可——两个载体内容相同,照样能叠到 #5868 上。所以关掉 #5879 不 strand 任何工作。

CI 现状(#5879):mergeable_state=blocked 只是因为 test 分片还在 queued(mysql-contract 已绿、若干 skipped),不是失败;真正卡合并的还是 F3 等你 A/B/C 拍板(PR #5859)。

请你定关哪个(建议关 #5879)。agent 无权关 PR;我这边停手,不再往这个分支叠东西,F3 裁决一出修复直接上 #5868。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

#5879 处理小结(详细证据见我上一条评论):

@ranxianglei
ranxianglei merged commit e4a4e41 into master Nov 8, 2026
47 checks passed
@github-actions

github-actions Bot commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.1091-master.e4a4e41 (rolling master tag).

npm install -g billion-context@0.0.1091-master.e4a4e41  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

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