feat(publish): extract communique into separate enhance-release job

[jdx]

Summary

• Moves communique generate out of the release job into a dedicated enhance-release job that runs after release
• Since it's a separate job, it can be re-run independently from the GitHub Actions UI if it fails (e.g. Anthropic rate limits, transient API errors)
• Runs after gh release edit --draft=false so the release is published and visible to communique

Test plan

• Trigger a tag push and verify enhance-release appears as a separate job in the workflow run

🤖 Generated with Claude Code

---

Note

Low Risk
Only adjusts GitHub Actions job orchestration; no application/runtime code changes, with the main risk being altered release workflow timing/dependencies.

Overview
Moves release-note enhancement (communique generate ... --github-release) out of the release creation flow into a new enhance-release job that runs after release.

This makes the AI-backed release-notes step independent/re-runnable and ensures it runs against the published release (adds fetch-depth: 0 to the checkout in that job).

^{Written by Cursor Bugbot for commit 379d1d0. This will update automatically on new commits. Configure here.}

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.88%. Comparing base (d562fb5) to head (379d1d0).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #513   +/-   ##
=======================================
  Coverage   77.88%   77.88%           
=======================================
  Files          48       48           
  Lines        6660     6660           
  Branches     6660     6660           
=======================================
  Hits         5187     5187           
  Misses       1109     1109           
  Partials      364      364           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

This PR refactors the communique generate command execution by moving it from the release job into a new dedicated enhance-release job. This architectural change allows the release note enhancement step to be independently re-run from the GitHub Actions UI if it encounters failures such as API rate limits or transient errors, without requiring the entire release process to be re-executed.

Changes:

• Removed communique generate step from the create-release job (including the continue-on-error: true flag)
• Added a new enhance-release job that runs after the release job to execute communique generate
• The new job includes proper checkout, mise setup, and environment configuration for the Anthropic API

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The enhance-release job has a condition if: ${{ startsWith(github.ref, 'refs/tags/v') }}, but this is redundant since it depends on the release job which already has the same condition. If the release job doesn't run, enhance-release won't run either.

However, there's a more critical issue: when workflow_dispatch is triggered, the release job runs but skips the gh release edit --draft=false step (line 123). This means the release remains in draft state, but enhance-release will still attempt to run. According to the PR description, communique needs the release to be published and visible. The condition should be updated to match line 123's condition to ensure enhance-release only runs when the release is actually published.

Suggested change

	if: ${{ startsWith(github.ref, 'refs/tags/v') }}
	if: ${{ github.event_name != 'workflow_dispatch' }}