manual workflow run image

Signed-off-by: Scott Rigby <[email protected]>

Author: scottrigby

hips/hip-9999-01.png

@@ -52,9 +52,11 @@ flowchart TD
 
 ### User Experience
 
-The release process starts with a **manual workflow trigger** where maintainers enter the target version (e.g., `v3.20.0`) in GitHub's workflow dispatch UI. This creates a preparation branch with all necessary version updates and opens a pull request for review.
+<img src="./hip-9999-01.png" width="400" />
 
-Once the PR is **merged**, automation takes over: it creates a persistent **release branch** (like `release-3.20`) from the appropriate base branch (`main` for v4.x, `dev-v3` for v3.x), cherry-picks the version commit, creates a signed tag, and **drafts the GitHub release**. The draft sits ready for maintainer review - they can test artifacts, verify release notes, and make adjustments before publishing.
+The release process starts with a **manual workflow trigger** where maintainers enter the target version (e.g., `v4.0.0-alpha.2` or `v3.20.0`) in GitHub's workflow dispatch UI. This creates a preparation branch with all necessary version updates and opens a pull request for review.
+
+Once the PR is **merged**, automation takes over: it creates a persistent **release branch** (like `release-4.0` and `release-3.20`) from the appropriate base branch (`main` for v4.x, `dev-v3` for v3.x), cherry-picks the version commit, creates a signed tag, and **drafts the GitHub release**. The draft sits ready for maintainer review - they can test artifacts, verify release notes, and make adjustments before publishing.
 
 When the maintainer **publishes the draft release**, it automatically triggers the documentation workflow in the helm-www repository, creating a pull request with updated version information, release dates, and compatibility matrices. This ensures the website stays synchronized with each release without manual coordination.
 
@@ -108,8 +110,3 @@ helm/helm-www/
 **Backwards Compatibility**: Manual process remains fully functional as fallback. No changes to existing release artifacts or tooling.
 
 **Security**: All releases created in draft mode requiring manual publication. GPG signing and commit signing preserved. Cross-repo access via fine-grained Personal Access Token with minimal permissions.
-
-## References
-
-- [Current Release Checklist](https://github.com/helm/helm-www/blob/main/content/en/docs/community/release_checklist.md)
-- [Working Examples](https://github.com/scottrigby/example-actions-autorelease-source)