docs: remove phases from release titles

Author: bradpotts

CHANGELOG.md

@@ -64,7 +64,7 @@ Contract change type: semantic change
 
 ## [0.4.0] - 2024-11-17
 
-**Release Title:** Phase 0 - Improvements and Fixes
+**Release Title:** Improvements and Fixes
 
 Contract change type: additive
 
@@ -86,7 +86,7 @@ Contract change type: additive
 
 ## [0.3.0] - 2024-11-01
 
-**Release Title:** Phase 0 - Implemented Cloudways List API Endpoints
+**Release Title:** Implemented Cloudways List API Endpoints
 
 Contract change type: additive
 
@@ -105,7 +105,7 @@ Contract change type: additive
 
 ## [0.2.0] - 2024-10-30
 
-**Release Title:** Phase 0 - Implemented Cloudways Server API Endpoints
+**Release Title:** Implemented Cloudways Server API Endpoints
 
 Contract change type: additive
 
@@ -120,7 +120,7 @@ Contract change type: additive
 
 ## [0.1.0] - 2024-09-25
 
-**Release Title:** Phase 0 - Official Stable Release
+**Release Title:** Official Stable Release
 
 Contract change type: additive
 

CODEX.md

@@ -58,18 +58,18 @@ gem build ruby_api_pack_cloudways.gemspec
 1. Update `lib/ruby_api_pack_cloudways/version.rb` to the new version.
 2. Move `[Unreleased]` notes in `CHANGELOG.md` into a new versioned entry:
    `## [<version>] - <YYYY-MM-DD>`, with a release title line in the format
-   `**Release Title:** Phase <N> - <short title>`, where `Phase <N>` is the
-   active phase name from this repo's own `ROADMAP.md` and `<short title>`
-   is a concise summary of what shipped. If the release spans no single
-   ROADMAP phase, state that explicitly instead of inventing one.
+   `**Release Title:** <short title>`, where `<short title>` is a concise
+   summary of what shipped. Do not include roadmap phase numbers, names, or
+   version numbers in release titles.
 3. Run the validation gate described in [AGENTS.md](AGENTS.md) plus
    `gem build ruby_api_pack_cloudways.gemspec` — must pass clean.
 4. Stage and commit the version bump and changelog update.
 5. Create the git tag: `git tag v<version>` (matching `version.rb` exactly),
    then push the commit and tag.
 6. Publish the GitHub Release from that tag: `gh release create v<version>
-   --title "v<version>: Phase <N> - <short title>" --notes-file` (extract the
-   new version's changelog section, or `--notes` inline for a short release).
+   --title "<short title>" --notes-file` (extract the new version's changelog
+   section, or `--notes` inline for a short release). The GitHub Release title
+   must match the changelog release title exactly.
 7. `gem push` is **not** run by Codex — that stays with Bradley Potts.
 
 ## Hard Limits