diff --git a/.github/workflows/package-release.yaml b/.github/workflows/package-release.yaml
index e0e0900..40b0d20 100644
--- a/.github/workflows/package-release.yaml
+++ b/.github/workflows/package-release.yaml
@@ -1,12 +1,5 @@
 name: Package Release
-# Deploy repo: a manual `sol-v*` tag is the sole release trigger.
-# rainix-autopublish's merge-driven, next-version lifecycle is wrong for this
-# shape: it bumps the release version on every merge, while the frozen deploy
-# tag only advances at deploy time.
-#
-# The on-chain deploy is separate and manual, run BEFORE tagging; this never
-# broadcasts. rainix-tag-release's chain verification is the intended gate: a
-# release is declared here only once it is a deployment that already happened.
+# Deploy repo: released by a manual `sol-v*` tag via rainix-tag-release.
 on:
   push:
     tags:
diff --git a/CLAUDE.md b/CLAUDE.md
index 88d604f..476e6c4 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -76,8 +76,5 @@ Mutation and coverage campaigns: see `.claude/rules/mutation-profile.md`.
 
 Deployed via the Zoltu deployer, so the address is a pure function of the
 bytecode. A deploy is a human-dispatched run of `Manual sol artifacts`, never a
-merge, and comes BEFORE the tag. Releases are manual `sol-v*` tags:
-`package-release.yaml` runs `rainix-tag-release`, which cuts the frozen
-`src/generated/<tag>/` record via `script/Build.sol --sig "cutRelease()"` and
-publishes `rain-extrospection-deploy` to Soldeer. `releasedSuites()` is empty
-until the first release is cut. See README.md.
+merge, and comes BEFORE the tag. Releases are manual `sol-v*` tags;
+`releasedSuites()` is empty until the first release is cut. See README.md.
diff --git a/README.md b/README.md
index 704a9ba..6bde88c 100644
--- a/README.md
+++ b/README.md
@@ -44,13 +44,8 @@ that needs a network.
 
 ## Releases
 
-Releases are manual `sol-v*` tags, never merges. `package-release.yaml` runs
-`rainix-tag-release`, whose `snapshot-generate-cmd` runs
-`script/Build.sol --sig "cutRelease()"`: it regenerates the rolling candidate,
-freezes it as `src/generated/<tag>/`, regenerates the released-suites libs from
-the record that now holds the release, verifies the live chains against the
-fresh pins, publishes `rain-extrospection-deploy` to Soldeer and commits the
-frozen record back to `main`.
+Releases are manual `sol-v*` tags, never merges. Tagging runs
+`rainix-tag-release`, which never broadcasts; its mechanics live in rainix.
 
 The on-chain deploy is separate and human-dispatched, run BEFORE tagging: the
 `Manual sol artifacts` workflow runs `script/Deploy.sol` for the `extrospect`