📝 Generate CLI release notes with Codex

[Robdel12]

Summary

This PR updates the main CLI release workflow to use openai/codex-action for GitHub release notes.

The current release notes are technically correct, but they are just commit subjects. That works when every commit is perfectly written. It falls apart when the interesting part is in the diff: docs changes, CLI behavior tweaks, test/supporting work, or a PR that bundles a few related files together.

The new flow asks Codex to inspect the actual release diff and write concise Keep a Changelog-style notes. The prompt is intentionally restrained: no invented features, no marketing polish, no raw commit dump, and no command log. Just the user-facing changes that are actually in the release.

What Changed

• Replaced the commit-list-only release note generation in .github/workflows/release.yml with openai/codex-action.
• Instructed Codex to inspect the tag-to-HEAD diff and read files when commit messages are not enough.
• Writes generated notes to RELEASE_NOTES.md, then passes that file into the GitHub Release body.
• Keeps a fallback path that generates the old commit-subject notes if Codex does not produce a file.

Why

This gives us release notes that are still simple, but much more useful. The goal is not fancy copy. The goal is grounded notes that explain what changed in a way a user can scan quickly.

Verification

Validated the workflow YAML locally and checked the diff for whitespace issues. actionlint is not installed locally, so this has not been run through actionlint.

[vizzly-testing]

Vizzly - Visual Test Results

CLI Reporter - Waiting for build

No builds received yet for this pull request.

CLI TUI - Approved

5 comparisons, no changes detected.

View build

---

_{rd/codex-release-notes · 3eaedc60}