chore(readme): fix drift (1134→1148, 82→103) + apr serve example syntax#1873
Closed
noahgift wants to merge 2 commits into
Closed
chore(readme): fix drift (1134→1148, 82→103) + apr serve example syntax#1873noahgift wants to merge 2 commits into
noahgift wants to merge 2 commits into
Conversation
3 tasks
noahgift
added a commit
that referenced
this pull request
May 22, 2026
…itstream-io) (#1878) `cargo deny check advisories` started failing on every PR (and on main) 2026-05-22 with: error[unmaintained]: core2 is unmaintained, all versions yanked ├ ID: RUSTSEC-2026-0105 ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0105 The dep is pulled in transitively via `bitstream-io` (image/media decoding stack — `cargo tree` shows `bitstream-io v4.9.0 → core2 v0.4.0`). No first-party use; no drop-in replacement until upstream `bitstream-io` migrates off core2. This commit unblocks the in-flight PR cascade (#1867 #1868 #1870 #1873 #1875 #1876) which all failed CI's `ci / lint` step on this advisory. The deny entry is structured per the existing pattern in this file (id + human reason mentioning the transitive path) so revisiting the ignore in 6-12 months is straightforward. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Surfaced by v0.35.0 release dogfood (2026-05-22): the FALSIFY-README-002
and FALSIFY-README-003 falsifiers in `contracts/readme-claims-v1.yaml`
were both failing:
FAIL FALSIFY-README-002 contract_count: README claims 1134, filesystem has 1148
FAIL FALSIFY-README-003 cli_command_count: README claims 82, apr --help lists 103
Updates:
- README "At HEAD" table: 1134→1148 contracts, 82→103 CLI commands
- README architecture diagram: "1105 provable YAML contracts"→1148,
"80 subcommands"→103
- README "Provable contracts" section: "1134 contracts across..."→1148
- CLAUDE.md project overview: 82→103 subcommands, 1134→1148 contracts,
also bumped the recent-release status line from "v0.33.0 SHIPPED
2026-05-14" to "v0.34.0 SHIPPED 2026-05-18" (the current crates.io
latest, per https://crates.io/crates/aprender).
Also fixes the README's `apr serve` example, which used a syntax that
errors out (#1864 Bug F filed inline; this is the fix):
Before:
apr serve model.gguf --port 8080
error: unrecognized subcommand '/path/to/model.gguf'
Usage: apr serve [OPTIONS] <COMMAND>
After:
apr serve run model.gguf --port 8080
apr serve plan model.gguf # pre-flight VRAM + roofline plan
`apr serve` is a subcommand group (`plan` and `run`) — the README example
predated the split and never got updated.
Verification:
$ bash scripts/check_readme_claims.sh
PASS FALSIFY-README-001 crate_count: 80
PASS FALSIFY-README-002 contract_count: 1148
PASS FALSIFY-README-003 cli_command_count: 103
PASS FALSIFY-README-004 cookbook_link: present
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
6f82028 to
3656871
Compare
5 tasks
Contributor
Author
auto-merge was automatically disabled
May 22, 2026 14:59
Pull request was closed
noahgift
added a commit
that referenced
this pull request
May 22, 2026
* chore(fmt): cargo fmt --all (release v0.35.0 baseline) * chore: README drift fix + apr serve syntax (#1873) * feat(cublas-fp8): Stage A deterministic reproducer (#1884) * feat(cublas-fp8): Stage B per-layer parity instrumentation (#1887) * fix(1864): Golden Output gate must set stop_tokens (#1890) * chore(release): bump to v0.35.0 + CHANGELOG + README contract count Workspace 0.34.0 → 0.35.0 across root Cargo.toml + all path-dep callsites + regenerate Cargo.lock. CHANGELOG v0.35.0 entry captures the 81-commit release scope: 1. Distill Phase 1-3 working end-to-end on NVIDIA GB10 Blackwell sm_121 2. MoE (Qwen3) KV cache + streaming SSE + sampling 3. 2026-05-22 dogfood pass: 8 bugs surfaced, 7 fixed. #1864 was a 5-line stop_tokens config gap, not a deep cuBLAS FP8 numerical bug — see feedback_falsify_simple_before_deep.md README contract count 1151 → 1153 (post Stage A + Stage B contracts).
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
1 participant
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.
Summary
Surfaced by v0.35.0 release dogfood (2026-05-22).
bash scripts/check_readme_claims.shonmainreported two failing falsifiers:Plus a third reproducible defect (Bug F from the dogfood session): the
apr serveexample in the CLI examples block errors out:apr serveis a subcommand group (plan/run) — the README example predated the split.Fix
apr serve model.gguf→apr serve run model.gguf+ addapr serve planlinev0.33.0 SHIPPED 2026-05-14→v0.34.0 SHIPPED 2026-05-18(the actual crates.io latest)Verification
Test plan
apr serve run model.gguf --port 8080(the new example) actually works🤖 Generated with Claude Code