Skip to content

chore(readme): fix drift (1134→1148, 82→103) + apr serve example syntax#1873

Open
noahgift wants to merge 6 commits into
mainfrom
chore/readme-claude-drift-1866-1865
Open

chore(readme): fix drift (1134→1148, 82→103) + apr serve example syntax#1873
noahgift wants to merge 6 commits into
mainfrom
chore/readme-claude-drift-1866-1865

Conversation

@noahgift
Copy link
Copy Markdown
Contributor

Summary

Surfaced by v0.35.0 release dogfood (2026-05-22). bash scripts/check_readme_claims.sh on main reported two failing falsifiers:

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

Plus a third reproducible defect (Bug F from the dogfood session): the apr serve example in the CLI examples block errors out:

$ apr serve model.gguf --port 8080
error: unrecognized subcommand '/path/to/model.gguf'
Usage: apr serve [OPTIONS] <COMMAND>

apr serve is a subcommand group (plan / run) — the README example predated the split.

Fix

  • README "At HEAD" table: 1134→1148 contracts, 82→103 CLI commands
  • README architecture diagram: 1105 → 1148, "80 subcommands" → 103
  • README "Provable contracts" section: 1134→1148
  • README CLI examples: apr serve model.ggufapr serve run model.gguf + add apr serve plan line
  • CLAUDE.md project overview: matching count fixes, plus bump recent-release status line v0.33.0 SHIPPED 2026-05-14v0.34.0 SHIPPED 2026-05-18 (the actual crates.io latest)

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

Test plan

  • All 4 FALSIFY-README-{001..004} now PASS
  • apr serve run model.gguf --port 8080 (the new example) actually works
  • CI: readme_contract test, workspace-test

🤖 Generated with Claude Code

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>
@noahgift noahgift enabled auto-merge (squash) May 22, 2026 07:18
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant