Repository navigation
Conversation
…v1.6.0 v1.5.0 carried 11 artifacts: 3 verified, 8 draft. Two of the drafts (slice 5 symbolic memory, slice 6 floats) are not implemented at all, and EXIT-Z3-REMOVED is gated on slices 2-6 by its own text. Release readiness is the rivet query, and that query said v1.5.0 was not cuttable. Scope decision: v1.5.0 = what is verified (Tier-2 slices 1, 3, 4). The eight drafts move to v1.6.0 by an explicit release: bump, not silently: slices 2, 5, 6, EXIT-Z3-REMOVED, musl, VEX, compliance report, aarch64. Also drops the stale "PLANNED — not yet implemented." lead from slice 2's description, which contradicted its own STATUS sentence one line later. The `v150` tags are left as-is; `release:` is the planning field. Refs: #313 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RZof1M5HMBSYVZPeoT4MEn
Rivet verification gate✅ 30/38 passed
Filter: Failed artifacts(none) Updated automatically by |
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.
Why
The
rivetquery forrelease: v1.5.0returned 11 artifacts, 3 verified and 8 draft. Two of the drafts aren't implemented at all: slice 5 (symbolic-index memory) and slice 6 (floats).TEST-313-EXIT-Z3-REMOVEDsays in its own text that it is not startable until slices 2–6 are verified. Under the release-planning rule, readiness is that query, so v1.5.0 could not be cut.Scope decision
v1.5.0 keeps what is verified. The drafts move by an explicit
release:bump rather than silently.After this change,
release: v1.5.0holds 3 artifacts, allverified.Also in this PR
Slice 2's description opened with
PLANNED — not yet implemented.One sentence later it saidSTATUS: the relation is implemented and five of seven criteria below are proven. This PR removes the stale lead. I checked the other drafts and none of them has the same contradiction.Diff shape
9 lines: 8
release:bumps and 1 description line.rivet modify --set-descriptionrewrites a folded>block as a single escaped line, which turned a one-sentence fix into a 50-line diff. So I applied the description change to the original block directly and checked it withrivet validate, which givesPASS (60 warnings), the same as onmain.The
v150tags are left alone becauserelease:is the planning field.Refs: #313
🤖 Generated with Claude Code
https://claude.ai/code/session_01RZof1M5HMBSYVZPeoT4MEn