Repository navigation
[bench] release: version 2.1.0; date the changelog; refresh the README cost figures - #65
Merged
Merged
Conversation
…E cost figures The release commit for v2.1.0. pyproject moves from 2.1.0.dev0 to 2.1.0 and the changelog's 2.1.0 entry is dated 2026-09-06, matching git's local-date convention the other entries follow. The README's What It Costs section is refreshed from the operational chain as of 2026-09-07 UTC. It now quotes both measured weeks: the v2.1 roadmap week (1,797 governed edits, median 34,747 tokens, 33,451 at cached rates, 63.5 seconds) and the release week so far (80 edits, median 19,483 tokens, 18,124 cached, 22.0 seconds), with the caveat stated in the section: the release-week row is a small sample of light edits, mostly docstring changes the Challenger clears in seconds and the Defender then skips, it is not a settled reduction, the roadmap-week row is the number to plan on, and the target of a median under 20,000 tokens stays a target. The wall-time table now covers all 1,635 timed entries rather than the first 78. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0122bFBUvdtXT245QFoYDkMf
Contributor
Author
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d751167608
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Codex review on #65: the README claimed the per-week token rows could be reproduced through cli stats and the viewer, and neither exposes tokens by week; cli stats prints the all-entries rows and the dashboard plots verdicts and latency by week. The section now says which interface shows which rows and gives the reproduction for the weekly ones: the same utils.stats helpers over one week's entries, in a snippet that runs as written and reproduces the roadmap-week row exactly. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0122bFBUvdtXT245QFoYDkMf
|
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.
The release commit for v2.1.0. Merging this is release check R5's last step; tagging the merge commit
v2.1.0is R6.What
pyproject.toml: version 2.1.0.dev0 becomes 2.1.0.CHANGELOG.md: the 2.1.0 entry is dated 2026-09-06, matching git's local-date convention the other entries follow.README.md, What It Costs: refreshed from the operational chain as of 2026-09-07 UTC, quoting both measured weeks with the caveat stated in the section, and the wall-time table over all 1,635 timed entries rather than the first 78.Release checks
python -m cli constitutionprints bench-v1 v7 with rule, rationale, and commentary lines (checklist text corrected from v6 to v7)cli statsshow the weekly figures below; the release notes quote themtests/test_ledger_hygiene.pyOK; every PR 43 through 64 carries ledger receiptsv2.1.0on this PR's merge commit (owner)Figures, from the live chain
The release-week row is a small sample of light edits, mostly docstring changes the Challenger clears in seconds and the Defender then skips. It is not a settled reduction; the roadmap-week row is the number to plan on, and the under-20,000 target stays a target. The README says exactly that.
Receipts
ruff check .and strict mypy clean; full suite 1027 OK, 20 skipped, on the same tree before the README refresh (prose only since).Not in this PR