Repository navigation
[PR] ci: converge master-CI fixes (persist restamp guard + lockfile version sync) (#4599) - #4814
Merged
Merged
Conversation
master window commits 293ae65/de5e03659 bumped kernel/package.json to 0.0.165 without regenerating the lockfiles; lock-sync re-resolution then rewrites the stale recorded versions (root 0.0.163, kernel 0.0.164) and fails. Pure recorded-version sync via npm install --package-lock-only; no dependency or semantic change.
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.6273-pr.4814.9e84105This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4814.tgz
npm install -g packageInstall instructions are refreshed on each push. |
This was referenced Oct 26, 2026
[PR] fix: armed compress circuit breaker now enforces itself on parse-failure receipts (#4812)
#4815
Merged
Closed
…r a send-failure give-up (#4599) #4516 (bc50f1a) replaced the post-give-up warn log with a state write that clobbered the 'send-failed' register value, breaking #4125's pinned contract (the register must stay 'send-failed' after a send-failure give-up). The user-facing intent of #4516 — accurate oversized-refusal wording — is kept by mapping 'send-failed' onto the dead-equivalent sentence in fallbackOversizeRefusal.
This was referenced Oct 26, 2026
Owner
Author
Owner
Author
Merged
This was referenced Oct 28, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(ai: vllm-qwen/qwen3.8-27b)
Persistent fleet convergence branch per owner strategy 2026-10-25 — all master-CI fixes land here first; PRs merge
origin/ci-fixesinto their heads instead of fixing master-level failures themselves. Recreated after #4727 was closed while stale-empty.Commits ahead of master (
931c66a2f):cdac1c099fix(persist): stop the ledger restamp from materializing empty CCR stores (CI Control Center: Centralized CI Failure Handling & Status Sync (Comment all CI issues here; do not open new issues) | CI 总控: CI 失败集中处理与状态同步(所有 CI 问题在此评论, 勿开新 issue) #4599) — bisect-proven root cause of the master red ontests/storage-unified.test.ts(introduced bya4a17cb86/Ledger re-stamp (restamp) never re-keys the CCR content store — forked CCR sessions 409 forever, decompress can serve ANOTHER message’s original #4733 via the [PR] chore: empty PR (no changes) #4725 vehicle):contentStoreOf()get-or-materializes an empty envelope for storeless sessions during cold-load ledger alignment, drifting the full-mode parity digest. Guarded call site: storeless sessions keep pre-Ledger re-stamp (restamp) never re-keys the CCR content store — forked CCR sessions 409 forever, decompress can serve ANOTHER message’s original #4733 shape; stored sessions re-key unchanged. Targeted local: storage-unified 14/0/1 (was 12/2/1), issue4733 suite green, kernel ccr-restamp green, typecheck clean.dfadc21b3fix(ci): sync lockfile recorded versions with acp-kernel 0.0.165 (CI Control Center: Centralized CI Failure Handling & Status Sync (Comment all CI issues here; do not open new issues) | CI 总控: CI 失败集中处理与状态同步(所有 CI 问题在此评论, 勿开新 issue) #4599) — window commits 293ae65/de5e03659 bumped kernel/package.json without regenerating lockfiles; lock-sync re-resolution rewrites root 0.0.163→0.0.165 and kernel 0.0.164→0.0.165. Pure recorded-version sync, no dependency change.Merge is owner-only.
kernel-change: lockfile-only recorded-version sync — commit dfadc21 updates root package-lock.json (acp-kernel 0.0.163→0.0.165) and kernel/package-lock.json (0.0.164→0.0.165) to match kernel/package.json after window commits 293ae65/de5e03659 bumped the version without regenerating locks. No kernel/src change, no kernel version bump; declaration required because the diff touches kernel/. (#4599)