Repository navigation
[PR] ci-fixes -> master: converge master CI gate fixes (#4599 #5860 golden realignment) - #5879
Conversation
…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).
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.8575-pr.5879.eef4aa9This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr5879.tgz
npm install -g packageInstall instructions are refreshed on each push. |
|
(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 ( 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. |
(ai: vllm-qwen/qwen3.8-27b) 复核完,结论不变:#5879 与 #5868 是同一份 F1+F2 golden 重对齐的两个载体,建议关掉后开的 #5879。 新增核实(不重复上一楼的本地 diff):两个 PR 改动的文件集完全一致——同样是这 5 个文件且均为 modified: 补一点上一楼没说清的:关 #5879 不会丢东西。 F3 那六个 estimate-grade nudge pin 的红属于另一条决策线,裁决之后它的机械修复落到「存活的那个载体」即可——两个载体内容相同,照样能叠到 #5868 上。所以关掉 #5879 不 strand 任何工作。 CI 现状(#5879): 请你定关哪个(建议关 #5879)。agent 无权关 PR;我这边停手,不再往这个分支叠东西,F3 裁决一出修复直接上 #5868。 |
…0.0.185, #5867 ruling) supersedes sentinel golden realigns
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.1091-master.e4a4e41 # this exact build
npm install -g billion-context@master # always the newest merged build
|
(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
e7b0cee85test(golden): realign storage-render snapshots with post-[PR] fix(nudge): no billing sample this round → hold pressure-band injection one round (phantom-pressure guard) #5860 persisted-state shape — [PR] fix(nudge): no billing sample this round → hold pressure-band injection one round (phantom-pressure guard) #5860 addedcompress.requireUsageSampleForPressure; the resolved Config snapshot persisted insession.metadata["effectiveConfig"]grew by exactly that field, so the metadata section digest drifts deterministically on all four lanes. Regenerated at5af5f9fed3viascripts/update-storage-render-goldens.ts; state/blockContents/stats sections unchanged, snapshot realignment only, no behavior change.6436b23b3test(golden): pin additiverequireUsageSampleForPressurein wire-contract kernel.json —buildKernelGolden()serializesdefaultConfig(100_000); diff is the single additive nudge field, ledger grows / nothing shrinks (Kernel Boundary rule 4).Both suites verified green locally under the CI preload env (
tests/preload-test-env.mjspinsBILI_MESSAGE_TIMESTAMPS=0):golden-storage-render+wire-contract-golden10/10.Known remaining red — DO NOT MERGE until resolved
F3 of the same wave: six estimate-grade nudge pins (
silent-backend-nudgex3,fork-nudge-triggerx2,issue4241-judge-render-baselinex1) 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.