From 1c6340cde73adb0d812d5628a6c66b4534021519 Mon Sep 17 00:00:00 2001 From: JohnnyT Date: Sun, 27 Sep 2026 09:28:09 -0600 Subject: [PATCH] Gives the merged prep's tag its owner The release extension still said the tag and its push stayed with the operator, in the section on mix hex.publish and again under the release trigger. CLAUDE.md's release-prep row and its Release preps paragraph now give the tag of a merged release prep to the conductor or the session that owns the release bead. Both sentences now say that, in this file's own words, and the publish (mix hex.publish, a docs republish included) stays the operator's one release step. Agent tooling only: no code, and no changelog fragment (changelog.d/README.md excludes agent tooling changes). Refs: px-fgiq --- .claude/wurk/release.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/.claude/wurk/release.md b/.claude/wurk/release.md index 61bc073..d4ba9a3 100644 --- a/.claude/wurk/release.md +++ b/.claude/wurk/release.md @@ -42,7 +42,8 @@ time. That is the recipe repairing drift, not a mistake to correct back. ## `mix hex.publish` has no trigger, ever Not delegable, and no instruction in a session grants it (CLAUDE.md's -authority table; ADR-0006). Tag and push stay separately human-gated. +authority table; ADR-0006). The tag is a separate step with its own owner - +see the release trigger below. ## The release trigger @@ -51,6 +52,10 @@ operator's explicit consent; or the user asking for a release in their own words. Where the operator does not name a version, it is this recipe's SemVer call from the accumulated `changelog.d/` fragments. Never inferred from a merged PR, from accumulated fragments on their own, or from "ship -it"/"cut it" said about something else. The tag, the push and the publish -stay the operator's - see CLAUDE.md's authority table, which this section -must not outrun. +it"/"cut it" said about something else. Once the prep is merged to +`origin/main`, the conductor or the session that owns the release bead tags +that merged commit with the new version and pushes the tag (CLAUDE.md's +Release preps paragraph). The publish - `mix hex.publish`, a docs republish +included - stays the operator's one release step, and no consent or relay +delegates it - see CLAUDE.md's authority table, which this section must not +outrun.