Repository navigation
[PR] test(ci): converge master red — realign five dsh pins to the #5656 single-shot sidecar residual (#4599) - #5718
Conversation
…ual (#4599) 01fcc5d (#5656/#5584, merged via #5687) diverts tool-less dsh single-shot requests onto the verbatim side lane (kernel no-touch); the residual for main turn 1 is documented in the commit's own comment. Five pre-existing pins assumed turn 1 rides the full pipeline and went born-red at merge (master red since; every PR head inherits it). Test-only realignment codifying the documented behavior: - issue2419/2446/2447/2481 guard-stamp subtests: two turns; the BLOCKED ref is witnessed on the first FULL-PIPELINE turn (turn 2). No fold can happen before turn 2 (nothing compressible, no action surface), so protection against every possible fold is unchanged. - issue2817: stats.requests off by one (turn 1 uncounted); the persona-fold teeth are intact, assertions shifted -1. - issue5403 A/B golden: turn 0 rides the side lane in BOTH phases (the gate ignores the rollout env), so rb[0] is unstamped by design; stamps resume at turn 1. Byte equality holds at i=0 (both phases forward verbatim). No src/, kernel/, config, or version changes. Locally green: all six files + side-lane-invariants + issue5656-single-shot-sidecar + dsh-persona-fingerprint.
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.8212-pr.5718.02d18b3This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr5718.tgz
npm install -g packageInstall instructions are refreshed on each push. |
|
(ai: vllm-qwen/qwen3.8-27b) 结论:可合(APPROVE) — test-only CI 收敛,机制经独立核验成立,teeth 保留,CI 全绿。 八问
核验:head |
[bot] 🏷 已完成对 PR #5718 的端到端审核 —— 可合(APPROVE)。
diff 干净,无小修。等你合并。 |
This reverts commit bb373ae. Address PR ranxianglei#1790 review 5782867946: remove the branch-specific main-header fixture repair before integrating the canonical ci-fixes change from ranxianglei#5718. Preserve the complete Recall contribution and existing commit history.
Merge the canonical 0470bec fix after reverting the duplicate main-header repair, addressing PR ranxianglei#1790 review 5782867946. Keep the Recall subtree byte-identical (8702851), preserve all contribution history, and leave upstream PR merging to maintainers. Validated the integrated tree: 49 targeted DSH regression tests; 162 Recall tests; 7 OpenCode adapter, 12 guard, 5 native-test-plugin, and 10 structured-checker checks; repository typecheck and build. Full repository verdict remains the remote CI on this new head.
…ual realignment, ranxianglei#5688 output_config dedupe, ranxianglei#5637 acp_delegate stand-down master advanced 6ddade1 -> 9a2d51d with 14 commits. The one that matters for this lane is 0470bec (ranxianglei#5718), which realigns five dsh regression pins to the ranxianglei#5657/ranxianglei#5656 single-shot-sidecar residual: the four durable-carrier suites now take a second turn and assert on "the first full-pipeline turn", and issue2817 re-bases stats.requests from 9 to 8. That is the opposing route to ranxianglei#5709 (which vetoes the misfire in source instead), but the two do not collide textually: ranxianglei#5718 touches only test files this lane does not carry, so the merge is clean. Verified on the merged tree that both routes' assertions now hold simultaneously.
What this converges
master has been red since
01fcc5d68("generic dsh single-shot sidecar gate", #5656/#5584, merged via #5687 at 2026-11-05 01:18Z). Every PR head inherits the same broken pins (reported independently by the #5700 / #5703 / #5708 lanes and bisected twice — this lane's and the #5703 lane's — landing on the same first-bad commit). This PR lands the convergence onci-fixesper the CI coordination policy (#4599).Root cause
isDshSingleShotSidecar()(src/server/side-request.ts) diverts any dsh-lane request with tools absent + non-empty system carrier + exactly one content-bearing non-system message onto the #388 verbatim passthrough side lane (kernel no-touch): no ref assignment, no stats.requests count, no pf-seq scan/stamp, no effective-config guard stamp. For a tool-less MAIN turn 1 this is a residual documented in the commit's own comment ("turn 2+ replays history and rejoins the full pipeline") — but five pre-existing regression pins were written assuming turn 1 rides the full pipeline, so they went born-red at merge:Why it went unprobed: ci.yml dropped
masterfrom push triggers (owner decision 2026-11-01), so there was no full-matrix master probe after Nov 1; #5687 itself merged with 5 red test shards.Fix (test-only, no product change)
Codify the documented residual in the pins themselves:
Behavior-change disclosure
No runtime behavior changes. Test-contract changes only:
Why not the alternatives
Verification
Coordination: #4599 (CI control center). Decision item B (predicate narrowing) tracked there.