From bf23551283882501eaad4d589595bbc76bbc77e4 Mon Sep 17 00:00:00 2001 From: JohnnyT Date: Sun, 11 Oct 2026 08:36:25 -0600 Subject: [PATCH] Says the release workflow publishes on the tag The version-bump paragraph of .claude/wurk/commit.md still said the publish was the operator's. Since ADR-0019 the release workflow publishes to Hex on the tag push, so the sentence now says that, that an agent or a session never runs mix hex.publish, and that a GitHub release stays the operator's, matching the CLAUDE.md release row. No other line of the file changes. Refs: sui-rxda --- .claude/wurk/commit.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.claude/wurk/commit.md b/.claude/wurk/commit.md index 8f4a467..18e9920 100644 --- a/.claude/wurk/commit.md +++ b/.claude/wurk/commit.md @@ -47,8 +47,9 @@ that is a commit-time concern: the recipe runs on a release bead the operator has named, and it still stops short of tagging, pushing and publishing. Those follow `CLAUDE.md`'s authority table: once the prep is merged to `origin/main`, the conductor or the session that owns the release bead tags -that merged commit, and only the publish (`mix hex.publish`, a GitHub -release) is the operator's, in every campaign. +that merged commit, and the release workflow publishes on the tag push +(ADR-0019): an agent or a session never runs `mix hex.publish`, and a +GitHub release stays the operator's, in every campaign. What it means for an ordinary commit is only this: if a version change turns up in the diff and you are not on a release bead, that is the finding - report it and stop, do not commit it.