fix(ci): escape markdown backticks in promotion PR body

[iamfj]

Summary

• fix escaping in .github/workflows/promote-next-to-main.yml PR body generation
• prevent bash command substitution from eating next/main/version markdown snippets

Why

Promotion PR body rendered placeholders as \ because workflow used over-escaped backticks (`\``), which bash interpreted as command substitution.

Validation

• reproduced shell output before fix (next: command not found, main: command not found)
• verified corrected output now renders markdown backticks as expected

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b86a45d4c9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Publish prereleases on the next dist-tag

The release pipeline now runs from both main and next, but the configured publish command (npx clean-publish --access public -- --provenance) does not set a dist-tag, so npm will use its default latest tag. That means next branch prereleases (e.g. *-next.N) can be promoted to latest and become the default install for all users, which breaks the stable/prerelease channel separation described in this change. Use a branch-aware publish path (for example semantic-release’s npm publishing with channels, or an explicit --tag for prerelease runs).

Useful? React with 👍 / 👎.