ci: Update Discord message formatting

[EttyKitty]

Summary by cubic

Streamlined Discord release notifications: keep the role mention in content, set the embed title to the release name, move a bold “Download” link into the description with the changelog, and update the footer to a clearer stability note with a 12-hour cadence and 20-build retention. Messages are shorter and easier to scan in Discord.

^{Written for commit 5169a5c. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 1 file

Confidence score: 4/5

• In .github/workflows/create_release.yml, the embed-title change can make Discord release notifications show only a raw API URL instead of a readable release name, which reduces clarity for anyone scanning release announcements; before merging, format the embed title/body to include a human-readable release label (and keep the URL as a separate field if needed).

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

1 issue found across 1 file (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".github/workflows/create_release.yml">

<violation number="1" location=".github/workflows/create_release.yml:301">
P0: `steps.create_release.outputs.release_name` doesn't exist — the embed title will be empty. Use `needs.prepare_release.outputs.release_name` instead, which holds the release name computed in the `prepare_release` job.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 1 file (changes from recent commits).

_{Re-trigger cubic}