docs: align the release claim's tag-basis provenance with the measured delta - #3502
Open
alonf wants to merge 1 commit into
Open
docs: align the release claim's tag-basis provenance with the measured delta#3502alonf wants to merge 1 commit into
alonf wants to merge 1 commit into
Conversation
…d delta The pre-merge phrasing predicted the merge would add no tree changes; the measurement says otherwise: 15 files between the certified head 0fa2627 and tag commit 67a5d7b — the documentation-only closure plus main-side records from the merge target's own reviewed history — zero code files. The claim's Provenance now carries the measured statement, with the note that the tag-pinned copies predate the correction. Records-only; one file. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J9aRRQJe5ENmn3kkfQoJ33
There was a problem hiding this comment.
Pull request overview
Updates the beta2 release-claim provenance record to replace an earlier pre-merge prediction with a measured statement about the certified head vs. tag-commit delta for v0.40.0-beta2.
Changes:
- Adds a provenance bullet documenting the beta2 tag certification run and adjudication date.
- Records a measured tag-basis delta statement (15 files changed, zero code files) and notes tag-pinned copies predate the correction.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+288
to
+290
| 2026-08-09 under the maintainer's trajectory ruling. **Measured tag-basis statement, correcting | ||
| the pre-merge phrasing**: `git diff 0fa26271..67a5d7bc` (certified head → tag commit | ||
| `v0.40.0-beta2`) is 15 files — the three documentation-only closure commits plus proposals, |
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
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.
One-file records-only correction, maintainer-approved (post-release interim item 1): the release claim's Provenance gains the measured tag-basis statement — 15 files between certified head
0fa26271and tag commit67a5d7bc, zero code files — replacing the pre-merge prediction, with a note that the tag-pinned copies predate the correction. The durable measurement record is on PR #3318 and in the GitHub release's tag-basis note.Goes through the normal gate — no protection changes.
🤖 Generated with Claude Code
https://claude.ai/code/session_01J9aRRQJe5ENmn3kkfQoJ33