Conversation
…(RAN-64) Closes the "README links to it" item on RAN-64. PR #4 already added CHANGELOG.md and docs/README.md to satisfy the bestpractices.dev release_notes + documentation_basics autofill criteria; this follow-up makes the new files discoverable from the top-level README so a human reader landing on the repo finds them without spelunking the file tree. Co-Authored-By: Paperclip <noreply@paperclip.ing>
6 tasks
aksOps
added a commit
that referenced
this pull request
Apr 26, 2026
…ersioning evidence (#8) CHANGELOG.md - [Unreleased] → [v0.1.0] - 2026-04-26 with full Added / Changed / Fixed / Security subsections covering PR #1 (RAN-54 baseline + Scorecard hardening), PR #3 (RAN-59 canonical-schema rewrite), PRs #4/#5 (RAN-64 CHANGELOG + docs/ index), PR #6 (5 SUGGESTED criteria flips), PR #7 (CONTRIBUTING.md + conventional-URL retargets). - Fresh empty [Unreleased] section opened at top per Keep-a-Changelog 1.1.0. - Link refs now point at compare/v0.1.0...HEAD and releases/tag/v0.1.0. .bestpractices.json - version_unique_url + release_notes_vulns_url added (both pointing at the v0.1.0 GitHub Release) so the bestpractices.dev autofill bot has a concrete URL to verify alongside _status: Met. - 5 versioning justifications refreshed to cite the concrete v0.1.0 tag instead of forward-looking commitments: version_unique, version_semver, version_tags, release_notes, release_notes_vulns. These are the criteria the autofill bot verifies by checking actual GitHub Releases / git tags exist. Once the v0.1.0 signed tag + GitHub Release land post-merge, autofill should flip release_notes to Met (currently Unmet pending evidence) and the 4 SUGGESTED versioning criteria stay Met with concrete tag-backed URLs. Co-authored-by: Paperclip <noreply@paperclip.ing>
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
Closes the "README links to it" item on RAN-64. PR #4 already added
CHANGELOG.mdanddocs/README.mdto satisfy the bestpractices.dev autofill criteria (release_notes+documentation_basics). This follow-up makes the new files discoverable from the top-level README so a human reader landing on the repo finds them without spelunking the file tree.What changed
README.md"Project files" table extended:File→File / folder(the table now includes a folder).docs/(withdocs/README.mdas the index),CHANGELOG.md,SECURITY.md,CLAUDE.md,shared/runbooks/engineering-standards.md, and.bestpractices.json.Single-file diff:
+7 / −1.Out of scope (per RAN-64 description)
.bestpractices.jsonschema rewrites — landed separately as RAN-59 (PR RAN-59: rewrite .bestpractices.json to canonical per-criterion schema #3 onmain)Test plan
main.passing.Closes RAN-64.
🤖 Generated with Claude Code