chore(release): v0.3.0 - #26
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Brian Jin <35789537+kikashy@users.noreply.github.com>
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.
Material-decision impact: none
This PR moves the Unreleased changelog entries under
0.3.0 - 2026-07-28. It makes no new decision: everything shipping in 0.3.0 — the MCP prompts capability (#19/ADR-0008), the RFC 0008 quantifier prototype behind its opt-in flag (#25/ADR-0009, two review runs recorded there), and the total §7.4 numeric equality in the experimental evaluator (#25) — carried its own review record on the PR that made the decision.All local gates pass at this commit:
go fmtclean,git diff --check,go vet,go test(13 packages),spec test-conformance --quiet, andcheck-release --tag v0.3.0("Release inputs verified"). The bundled JPS artifacts are unchanged (a CLI release is independent of spec releases; 0.2.0-draft, in progress, ships in a later CLI version once tagged).After merge, per docs/releasing.md the annotated tag
v0.3.0on the merge commit is yours to sign and push; the tag workflow takes it from there.🤖 Generated with Claude Code