Repository navigation
Draft: what ships in v2026.43 - #6
bong-water-water-bong wants to merge 2 commits into
Conversation
The release candidate's data as a post: the pins, the week's HRX speed with the measured numbers, the 8-concurrent-chat cells (ours standard, 90 W cap, PCM pad (23 Oct)), the correctness items (strict placement, 43/43 census, #315 resolved, the ZAYA1-8B NaN close), the NPU gate at 90.33 tok/s, Lemonade's one hop with 22 proven catalog entries, and the 1bit OS image. It also says what is not in the candidate: the install step, and Windows. Every number carries its standard (lemonade bench standard or ours) and links to docs/releases.md, docs/hw-gate.md, docs/npu.md, docs/serve.md. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…4bd713d968) Keeps the post's pin table identical to the engine docs' candidate section, which is what the release run will record. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
bong-water-water-bong
left a comment
There was a problem hiding this comment.
VERDICT: CLOSE (superseded) — not READY, and not because of the diff.
Waiting 16 days for a verdict, so here is one, with the two facts that decide it.
1. Its numbers are four pin bumps old
The post says "the release candidate for v2026.43 is built from the pins below" (blog/2026-10-23-what-ships-in-v2026.43.md:22-34). Those pins against origin/main today (b970d85ba5 llama.cpp, 054433cbfa lemonade, 7f4236924a hrx-system):
| pin in the post | today |
|---|---|
llama.cpp (HRX) 851fa6c8d8f2 |
b970d85ba5 |
Lemonade 27abcc24da99 |
054433cbfa |
hrx-system 82804197bcbe |
7f4236924a |
A "what ships in this release, built from these pins" post cannot be published against pins the candidate no longer has — and docs/releases.md is the page that owns the dated pin record anyway (## v2026.43 (candidate, 23 Oct), docs/releases.md:206).
2. v2026.43 is not the release any more
docs/releases.md:26 — "The first release, v2026.44, is a draft" — and the v2026.44 section (:38) is where the candidate chain now leads: c19 pulled back to a draft, then c20…c28, with c27/c28's board rows. The v2026.44 release post already exists as site #16's blog/2026-11-02-the-first-release.md (still draft: true). Two "what ships" posts cannot both be the release post, and the v2026.44 one is the current candidate.
3. Two things that would have to be true before it could merge
- The owner's publishing hold is on: no blog post, no page publish — so no release post merges today regardless of its content.
- It is a draft PR by design ("Branch kept unmerged — the owner publishes"): the verdict convention does not apply to it, which is why nobody has posted one in 16 days.
Suggestion
Close it and keep the branch (or leave it as a draft) — docs/releases.md's ## v2026.43 (candidate, 23 Oct) section already carries the dated record of that candidate, and #16 carries the v2026.44 post that supersedes it. If the owner wants the v2026.43 week preserved as a blog post rather than a release note, the cheapest path is a re-cut with today's pins and an explicit "candidate that was replaced" framing — which would be a new draft, not this one.
Owner's call, not mine: I do not merge, and publishing is held.
|
VERDICT: CHANGES REQUESTED — as a draft it is harmless, but publishing this text would announce a release number that never shipped. Reviewed What the facts say, from the repo's own sources
So the v2026.43 candidate was superseded before it produced any artifact: the draft's entire premise ("what ships") describes a thing Why close rather than fixThe content is a week's engineering record — decode and prefill numbers, 8-concurrent-chat results, the NPU gate, the pins — and that has Everything mechanical about it is fine, for the record
|
|
VERDICT: CLOSE (superseded) at Reasons, unchanged: its pins are four bumps old (llama.cpp Owner's call; I do not merge and publishing is held. |
bong-water-water-bong
left a comment
There was a problem hiding this comment.
VERDICT: CHANGES at d7621ccc.
I can check two classes of claim in a post like this: the pins, and the internal arithmetic. The arithmetic is consistent (step 121 → 88 ms, tok/s rows moving in
the right direction together), and four of the pins are exactly the ones docs/releases.md carries — but two are not there, and the post promises that
they are:
pin quoted in the post occurrences in engine's docs/releases.md (origin/main)
851fa6c8d8f2 llama.cpp 1
82804197bcbe hrx-system 2
744bd713d968 (hrx pin) 2
27abcc24da99 Lemonade 0 <- not there
abaa6bc484d5 our HIP kernels 0 <- not there
and the post says, in as many words: "The full pin list, the artifacts and every check are in …" — so a reader who follows that link will not find the
Lemonade or HIP kernel pin they just read. Two ways to make it true, and the smaller one is in this PR:
- soften the sentence to what
releases.mdactually carries ("the artifacts and every check are in …"), leaving the pins table above as the candidate's own
list; or - add
27abcc24da99andabaa6bc484d5todocs/releases.md— but that is an engine change, in a different repo and a different release of the doc, so it
is not this PR's business unless it is done deliberately.
Everything else reads as a draft in the right register: claims scoped to "the measurement database and the proofs", each speed row carrying its number, and
the branch explicitly unmerged for the owner to publish — which is respected: this verdict is about whether the content is correct, not about publishing.
One thing I could not check from here and am not pretending to: the speed numbers themselves (27B MTP 25.9/20.5/21.9 → 36.0/26.8/29.9 tok/s, step 121 → 88
ms). They are internally consistent and phrased as measurements, but their source is the measurement database, not the engine tree, so whoever publishes should
diff them against it — the post's credibility is exactly those rows.
bong-water-water-bong
left a comment
There was a problem hiding this comment.
VERDICT at d7621cc: CHANGES
Re-stated in the form the merge script reads; the reasoning is in the review above and the head has not moved since.
VERDICT at
|
|
The CHANGES at Verified again, on this headBoth pins are still absent from the document the post tells the reader to consult, and the sentence that sends them there is unchanged. So the objection is not a matter of taste that a second reviewer can overrule — it is the same arithmetic four days later, and the smaller of the two fixes is still one clause in one sentence. Why the later READY does not close itThe Two things are wrong here and only one of them needs a lane: the post overstates what the link contains, and the record made that look resolved. The smallest fix, unchangedSoften line 36 to what Not my PR to fix (site lane), so this is a re-check and a pointer rather than a review: the CHANGES stands, and the PR should not merge until line 36 or |
Draft post for the
v2026.43release: the candidate's data, no claims beyond what the measurement database and the proofs carry. Branch kept unmerged — the owner publishes.What it says
851fa6c8d8f2, hrx-system82804197bcbe, Lemonade27abcc24da99, our HIP kernelsabaa6bc484d5, the sealed NPU kernel sets17ed5be7a28a), linking to the full list indocs/releases.md.90 W cap, PCM pad (23 Oct)): 27B 50.7, Coder-30B 138.1, Qwen3.5-4B 194.3 aggregate tok/s at N=8 — with the honest comparison that Lemonade's Vulkan build reaches 201.8 and 245.7 in the same run, so the MoE batching gap is named as the next speed row rather than hidden.Rules followed
Tone is the site's: what was built and how it measured, no comparisons framed as wins, no vendor commentary. Closed-source wording only — "our HIP kernels", "the sealed NPU kernel sets" — no kernel names, files or methods. No
image:line, so the post uses the site's own preview card instead of borrowing another post's.Verification
Front matter matches the format the other posts use (
tags,summary, then# Title); the site build happens inpages.ymlwith the engine checkout, so this branch was not built locally. Every number is traceable to the auto-opt database rows, the catalog proofs page, a closed issue, or a linked engine PR.🤖 Generated with Claude Code