release: ship complete W1-W13 binary matrix - #196
Merged
Conversation
mudler
force-pushed
the
row/ENG-RELEASE-BINARIES
branch
from
August 9, 2026 10:38
0394402 to
80deeca
Compare
localai-bot
marked this pull request as ready for review
August 9, 2026 10:50
localai-bot
marked this pull request as draft
August 9, 2026 14:19
mudler
force-pushed
the
row/ENG-RELEASE-BINARIES
branch
from
August 9, 2026 14:20
80deeca to
654163c
Compare
localai-bot
changed the title
mudler
force-pushed
the
row/ENG-RELEASE-BINARIES
branch
from
August 9, 2026 15:07
c4e4adb to
d693523
Compare
Record the W6 install and archive checkpoint after diagnosing the empty tagged release. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
Install a static-core vllm-server component, add deterministic stage and archive targets, and gate the extracted binary in CPU CI while preserving the library install. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
Record the developer-directed single-PR delivery topology while preserving independently verified work-unit checkpoints. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
Pin PR 196 as the single delivery surface and reconcile the live claim without advancing release evidence beyond W6. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
Split architecture-specific sm12x NVFP4 bodies from portable CUDA sources, assign exact per-source gencode intersections, and add a hosted compile/cubin audit with mutation coverage. The real NVIDIA toolkit build remains pending on PR CI. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
Use single-token nvcc -gencode options for per-source properties. This repairs the quoting failure observed in hosted CUDA run 31320289475 while retaining the exact ten-SM source matrix. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
Embed and namespace all six vendored Triton cubin trees, dispatch launchers and loaders by exact runtime SM, and preserve portable fallback on release SMs without an AOT tree. Add toolkit-free selector, namespace, ELF identity, and archive mutation gates. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
Register disabled creation mutations for the new W1 and W2 release auditors so the PR-size gate proves red-before/green-after behavior. Re-pin the byte-tight status ratchet after rebasing the release checkpoint onto current main. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
Bind the sanctioned size waiver to PR #196 only. The accepted release topology and explicit maintainer direction require W1-W13 to remain in one review and delivery PR. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
mudler
force-pushed
the
row/ENG-RELEASE-BINARIES
branch
from
August 9, 2026 15:40
d693523 to
50f8de3
Compare
FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Codex:GPT-5 [Codex]
localai-bot
marked this pull request as ready for review
August 9, 2026 18:22
mudler
added a commit
that referenced
this pull request
Aug 9, 2026
…message Main CI has been red on EVERY merged PR. Two independent defects, both landed by #178's push (run 31332846716); `cuda-fat-build` in that run was cancelled by concurrency, not failing. THE GATE REDDENED MAIN FOR OBEYING IT. `check-role-discipline.py` judges every commit in the `before..after` range on its own message. A PR landed with a REAL merge commit pushes the merge AND the branch commits under it: the merge names the PR, the branch commits were never required to, so each one read as a direct push. `6603356a` (#178), `e73cbbae` (#204) and `1a02ab4f` (#196) all failed this way, in both `documentation-checkpoint` and `agent-record`. Arrival is now judged ONCE, on the commit that lands the change: `merged_pr_content` exempts what a row/* PR merge brings in. Squash-merges are untouched -- their one commit carries "(#N)" and passes on its own message. NOT a weakening, and gated as such: only the SIDE parents count, so `--not parents[0]` keeps a commit pushed straight to main from being laundered by merging a PR on top, and a merge naming no row and no PR exempts nothing. Four unit checks build real git history for those cases, plus the exact `3bbee96e..0cf3dbb` range CI ran, pinned with `has_reached_main` forced TRUE -- from a `row/*` worktree everything reports as pending PR disposition, and the test would have passed against the defect it exists to catch. Suite 47/47, and 5/5 red without the fix. A STALE MESSAGE IN A TEST. `6603356a` taught `LoadMergedBf16RawNK` to accept F8_E4M3 shards and rewrote its rejection to name the supported dtypes; `test_qwen27_dense_forward.cpp:229` still asserted the old "expected BF16", so `build-test-cpu` and both sanitizer legs failed on it. The expectation now reads the message the loader raises, and the FP8 merge path that arrived WITHOUT a test in this file gets one: a mixed BF16+FP8 merged parameter, expectations hand- computed from E4M3 bytes and the scale (never re-derived through the same dequant helper the loader calls), plus the per-channel-scale rejection. 7/7, 333 assertions. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Claude:claude-opus-5 [ClaudeCode]
mudler
added a commit
that referenced
this pull request
Aug 9, 2026
…message (#210) Main CI has been red on EVERY merged PR. Two independent defects, both landed by #178's push (run 31332846716); `cuda-fat-build` in that run was cancelled by concurrency, not failing. THE GATE REDDENED MAIN FOR OBEYING IT. `check-role-discipline.py` judges every commit in the `before..after` range on its own message. A PR landed with a REAL merge commit pushes the merge AND the branch commits under it: the merge names the PR, the branch commits were never required to, so each one read as a direct push. `6603356a` (#178), `e73cbbae` (#204) and `1a02ab4f` (#196) all failed this way, in both `documentation-checkpoint` and `agent-record`. Arrival is now judged ONCE, on the commit that lands the change: `merged_pr_content` exempts what a row/* PR merge brings in. Squash-merges are untouched -- their one commit carries "(#N)" and passes on its own message. NOT a weakening, and gated as such: only the SIDE parents count, so `--not parents[0]` keeps a commit pushed straight to main from being laundered by merging a PR on top, and a merge naming no row and no PR exempts nothing. Four unit checks build real git history for those cases, plus the exact `3bbee96e..0cf3dbb` range CI ran, pinned with `has_reached_main` forced TRUE -- from a `row/*` worktree everything reports as pending PR disposition, and the test would have passed against the defect it exists to catch. Suite 47/47, and 5/5 red without the fix. A STALE MESSAGE IN A TEST. `6603356a` taught `LoadMergedBf16RawNK` to accept F8_E4M3 shards and rewrote its rejection to name the supported dtypes; `test_qwen27_dense_forward.cpp:229` still asserted the old "expected BF16", so `build-test-cpu` and both sanitizer legs failed on it. The expectation now reads the message the loader raises, and the FP8 merge path that arrived WITHOUT a test in this file gets one: a mixed BF16+FP8 merged parameter, expectations hand- computed from E4M3 bytes and the scale (never re-derived through the same dequant helper the loader calls), plus the per-channel-scale rejection. 7/7, 333 assertions. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Claude:claude-opus-5 [ClaudeCode] Co-authored-by: Ettore Di Giacinto <mudler@localai.io>
localai-bot
pushed a commit
that referenced
this pull request
Aug 10, 2026
Developer decision, on measured grounds rather than feel. Over the last 22 merged PRs the 900-line `product` budget was exceeded by 9 of them (41%): 71 76 78 129 178 182 237 338 340 479 596 605 895 | 1272 1306 1510 2261 2843 3224 4098 5282 6480 A gate that fires on four changes in ten is not a budget, it is noise that teaches people to waive it. Worse, tests are a third to a half of every large diff here (#211 909/2261, #197 684/1510, #240 931/2843, #196 2319/4098), so the budget charged RED-first mutation tests against the same allowance as kernel code, penalising exactly the discipline the rest of AGENTS.md demands. Size is now a review judgement: split a change when a reviewer would be better served by parts, not when a counter says so. WHAT IS NOT RETIRED, because dropping a size gate is not licence to drop the rules that shared its file: explicit path classification (no blanket directory exemptions), the fail-closed binary guard, the checker-change mutation-evidence contract, and the role check that keeps product paths on a PR. A new test pins all three so they cannot be deleted quietly alongside a constant. Evidence for this being a real checker-semantics change, per the contract this checker itself enforces: `test_no_line_budget_is_enforced_for_any_class` is RED against the pre-change checker (which exported PATH_CLASS_BUDGETS and rejected a 100k-line product change) and green after; the companion regression test is green on BOTH sides and asserts on the error, not its wording, so it is not coupled to a message the retirement reworded. Suite: 33 passed, 101 subtests. The `pr-size` CI job keeps its name because it is a required check; its comment and step name now say what it actually enforces. Re-running it over PR #211, the 2261-line change that prompted this, leaves exactly one error: the genuine missing mutation evidence for a checker edit. Following-Agents-Protocol: true AI-Assisted: true Assisted-by: Claude Code:claude-opus-5 [Claude Code]
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
2 participants
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.
Scope
Tracks #117.
This is the single delivery PR for the complete primary downloadable
vllm-serverrelease matrix. Required W1-W11/W13 are implemented here; W5 arrived through #141. W12 remains the accepted optional, non-primary single-SM diagnostic lane and is not used to bypass either fat-CUDA bundle.The pipeline now builds eight host/backend tuples, validates freshly extracted bytes, creates an immutable verified handoff, generates JSON/Markdown indexes from embedded manifests, attests the archives, and publishes every explicitly authenticated archive/checksum/provenance triplet. This fixes the test release that attached only a handoff and no binary.
Matrix
Verification
scripts/agent-preflight.sh— PASSWAIVER-PR-SIZE-003— PASSROCm remains blocked by the accepted contract; musl stays experimental preview. Build-only lanes do not acquire runtime/correctness/performance claims.