@@ -18,7 +18,7 @@ bundle exec bake agent:context:install
 bundle exec bake gem:github:setup:plan
 ```
 
-Setup adds three release workflows, `config/release.yaml`, native ruleset payloads, and `.github/releasing.md`. Identical reruns do nothing; conflicting existing files stop before any file is written. Setup does not replace other publishers: remove conflicting release workflows during migration.
+Setup adds three release workflows, `config/release.yaml`, and native ruleset payloads. Identical reruns do nothing; conflicting existing files stop before any file is written. Setup does not replace other publishers: remove conflicting release workflows during migration.
 
 To adopt template fixes after upgrading the gem, start from a clean working tree, edit `config/release.yaml` as needed, and regenerate:
 
@@ -27,7 +27,7 @@ bundle exec bake gem:github:setup:update
 git diff
 ```
 
-The task updates the managed workflows, policy payloads, configuration formatting, and maintainer instructions directly in the working tree and returns the changed paths. It does not stage, commit, or change remote settings. An agent or maintainer can review the diff and selectively keep changes, restoring repository-specific customizations from Git where needed. Commit or stash existing edits first: generated files are replaced by the current templates. Repeating an update produces no further changes; intentionally retained customizations will appear in later update diffs. Apply remote rulesets after the corresponding workflows are running.
+The task updates the managed workflows, policy payloads, and configuration formatting directly in the working tree and returns the changed paths. It does not stage, commit, or change remote settings. An agent or maintainer can review the diff and selectively keep changes, restoring repository-specific customizations from Git where needed. Commit or stash existing edits first: generated files are replaced by the current templates. Repeating an update produces no further changes; intentionally retained customizations will appear in later update diffs. Apply remote rulesets after the corresponding workflows are running.
 
 Release workflows follow `bake modernize` action versions and use moving major tags where upstream provides them. These tags receive upstream updates automatically; full commit hashes select fixed revisions. The RubyGems credentials action uses its [documented `@main` reference](https://github.com/rubygems/configure-rubygems-credentials#trusted-publisher-recommended), since upstream does not provide a moving major tag. Repositories that require fixed revisions can customize these references.
 
 
@@ -18,7 +18,7 @@ bundle exec bake agent:context:install
 bundle exec bake gem:github:setup:plan
 ```
 
-Setup adds three release workflows, `config/release.yaml`, native ruleset payloads, and `.github/releasing.md`. Identical reruns do nothing; conflicting existing files stop before any file is written. Setup does not replace other publishers: remove conflicting release workflows during migration.
+Setup adds three release workflows, `config/release.yaml`, and native ruleset payloads. Identical reruns do nothing; conflicting existing files stop before any file is written. Setup does not replace other publishers: remove conflicting release workflows during migration.
 
 To adopt template fixes after upgrading the gem, start from a clean working tree, edit `config/release.yaml` as needed, and regenerate:
 
@@ -27,7 +27,7 @@ bundle exec bake gem:github:setup:update
 git diff
 ```
 
-The task updates the managed workflows, policy payloads, configuration formatting, and maintainer instructions directly in the working tree and returns the changed paths. It does not stage, commit, or change remote settings. An agent or maintainer can review the diff and selectively keep changes, restoring repository-specific customizations from Git where needed. Commit or stash existing edits first: generated files are replaced by the current templates. Repeating an update produces no further changes; intentionally retained customizations will appear in later update diffs. Apply remote rulesets after the corresponding workflows are running.
+The task updates the managed workflows, policy payloads, and configuration formatting directly in the working tree and returns the changed paths. It does not stage, commit, or change remote settings. An agent or maintainer can review the diff and selectively keep changes, restoring repository-specific customizations from Git where needed. Commit or stash existing edits first: generated files are replaced by the current templates. Repeating an update produces no further changes; intentionally retained customizations will appear in later update diffs. Apply remote rulesets after the corresponding workflows are running.
 
 Release workflows follow `bake modernize` action versions and use moving major tags where upstream provides them. These tags receive upstream updates automatically; full commit hashes select fixed revisions. The RubyGems credentials action uses its [documented `@main` reference](https://github.com/rubygems/configure-rubygems-credentials#trusted-publisher-recommended), since upstream does not provide a moving major tag. Repositories that require fixed revisions can customize these references.
 
 
@@ -18,7 +18,7 @@ def initialize(root)
 					@root = File.expand_path(root)
 				end
 
-				# Generate workflows, policy payloads, and maintainer instructions. Refuse conflicting existing files.
+				# Generate workflows, policy payloads, and configuration. Refuse conflicting existing files.
 				def generate(repository:, branch: "main", checks:, approvals: 2, signing: File.file?(File.join(@root, "release.cert")), ruby: "3.4")
 					raise "Expected owner/repository." unless repository.match?(/\A[\w.-]+\/[\w.-]+\z/)
 					raise "Unsupported branch name." unless branch.match?(/\A[\w.\/-]+\z/)
@@ -76,7 +76,6 @@ def render(config)
 					self.class.rules(config).each do |name, rule|
 						files[".github/release-rules/#{name}.json"] = JSON.pretty_generate(rule) + "\n"
 					end
-					files[".github/releasing.md"] = File.read(File.join(templates, "releasing.md"))
 					files
 				end
 			end
 
@@ -9,4 +9,12 @@ Reviewed GitHub releases for Ruby gems, using `bake-gem` for branch preparation,
 
 Read [the setup, release and recovery guide](guides/getting-started/readme.md) before enabling publishing. Context is distributed through `agent-context`. This initial implementation requires `bake-gem` 0.15 or later and a live pilot before wider rollout.
 
-For this gem's releases, follow [the maintainer instructions](.github/releasing.md). Release workflows use the source checkout through Bundler's `gemspec` dependency, so the first release does not require an already published copy of `bake-gem-github`.
+## Making Releases
+
+To prepare a release branch and open a pull request from an up-to-date `main`:
+
+``` bash
+$ bundle exec bake gem:github:release:patch # or minor or major
+```
+
+See [bake-gem-github](https://github.com/socketry/bake-gem-github) for setup, remote releases, and recovery.
@@ -1,5 +1,9 @@
 # Releases
 
+## Unreleased
+
+  - Stop generating `.github/releasing.md`; release instructions are maintained in the shared guide and agent context.
+
 ## v0.2.0
 
   - Use only the version tag for GitHub release titles.
 
@@ -32,6 +32,7 @@ def generate
 	it "generates three parseable workflows and idempotent native policy" do
 		paths = generate
 		expect(generate).to be == paths
+		expect(File).not.to be(:exist?, File.join(root, ".github/releasing.md"))
 		expect(paths.grep(/workflows/).size).to be == 3
 		paths.grep(/workflows/).each do |path|
 			workflow = YAML.safe_load_file(File.join(root, path))
 
@@ -40,12 +40,13 @@
 		end
 
 		it "restores missing generated files" do
-			path = File.join(repository, ".github/releasing.md")
+			path = File.join(repository, ".github/workflows/release-validate.yaml")
 			original = File.read(path)
 			File.unlink(path)
-			expect(setup.update).to be == [".github/releasing.md"]
+			expect(setup.update).to be == [".github/workflows/release-validate.yaml"]
 			expect(File.read(path)).to be == original
 			expect(setup.update).to be == []
+			expect(File).not.to be(:exist?, File.join(repository, ".github/releasing.md"))
 		end
 
 		it "refuses unsupported configuration schemas" do