docs(readme): structure the README with headings and a Reproducing section - #18
Merged
Conversation
…ction Adds ## Results / ## Reproducing / ## Repo map headings over the existing findings-first content — no wording or numbers changed. The Reproducing section documents the real entry points (uv run pytest, the committed m1-m4_verdict.py scripts against results/, and the milestone runners with --dry-run/--limit), verified to run as written. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HdvbHntpNSFw8mZ5Rv62Yk
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
## Results,## Reproducing,## Repo mapheadings over the existing README content — pure reorganization, zero numbers/claims changed, findings-first opening (incl. the honest-framing line) left untouched.## Reproducingsection documents real entry points:uv run pytest, the committedm1_verdict.py…m4_verdict.pyscripts (print gate verdicts straight from committedresults/*.json, no model/lens/GPU needed), and the milestone runners with--dry-run/--limit, plus recorded per-subject runtimes from the milestone briefs.## Repo maptable pointing atdocs/, the runners,items/,results/,lenses/.Verification
uv run pytest— 396 passedm1_verdict.py…m4_verdict.py) as documented — output matches the numbers already in the README.Review
Docs-only, non-behavioral diff (README reorg only) — trivial-diff escape hatch applies per the global git workflow; skipping the adversarial-review loop.
🤖 Generated with Claude Code
https://claude.ai/code/session_01HdvbHntpNSFw8mZ5Rv62Yk