Release and commit guides: the merged prep's tag is the conductor's - #174
Merged
Merged
Conversation
The release and commit extensions still said the tag of a release prep was the operator's. CLAUDE.md's tagging row and its Release preps paragraph now make the tag of a merged prep the norm: once the prep is merged to origin/main, the conductor or the session that owns the release bead tags that commit. Both files now say so in their own words, and both keep the publish (mix hex.publish, a GitHub release) with the operator. No rule changes; no other file is touched. Documentation only: no code, no changelog fragment. Refs: sui-3jh1
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.
Two sentences in the release tooling guides still said that tagging a release prep was the operator's. This rewords them to match
CLAUDE.mdas it stands on main, in each file's own voice, and grants nothing the authority table does not..claude/wurk/release.md, section "What a release here still is not": the paragraph no longer says the tag, push and request are the operator's, and no longer quotes the old release row as "a release (tag,mix hex.publish, GitHub release)". It now says that the push and the request follow the table's push row, that once the prep is merged toorigin/mainthe conductor or the session that owns the release bead tags that merged commit and pushes the tag, and it quotes the current release row, "a release (mix hex.publish, GitHub release)", with triggernever..claude/wurk/commit.md, section "Version bump: none": the sentence saying the authority table holds tagging, pushing and publishing for the operator now says the merged prep's tag is the conductor's or the release-bead session's, and only the publish (mix hex.publish, a GitHub release) is the operator's.Review (own, in turn). I checked each new sentence against
CLAUDE.md's authority table (the "tagging a release prep" row and the "a release (mix hex.publish, GitHub release)" row) and against its "Release preps" paragraph. The tag sentence matches that paragraph's "the conductor or the session that owns the release bead tags that merged commit with the new version and pushes the tag". Its trigger is quoted from the tagging row. The publish stays the operator's in both files: the release row's triggernever, and the paragraph's "Publishing (mix hex.publish, a docs republish included) is the operator's one release step ... no consent or relay delegates it". No authority row, noCLAUDE.mdtext and no other file changes. I searched both files for any other sentence that puts the tag with the operator or says a prep carries no tag, and found none beyond the two above.The release-prep request contents, the recipe's steps and the file table are unchanged. There is no changelog fragment:
changelog.d/README.mdexcludes agent tooling changes. There is no gate run:.claude/is outsidebuild_pathsandalso_gated_pathsin.claude/wurk.json, so no gated path is touched.The wording change was ruled by the operator, 2026-09-26.