ci(release): trigger the brevo-skills sync after a publish

[piyushsarin-sib]

What changed

After a release publishes @getbrevo/cli, a new step in release.yaml dispatches the sync-skill workflow in getbrevo/brevo-skills for the brevo-cli skill, at the release commit. That repo packages agent-context/SKILL.md for every agent platform. Its sync opens a PR there for review, so nothing reaches users without a merge on that side.

Safety

• It can't fail a release. The step uses continue-on-error. Without BREVO_SKILLS_SYNC_TOKEN it logs a warning and exits 0.
• It runs only after a real publish, with the same condition as the smoke trigger. It also has !cancelled(), like the Homebrew bump.
• The token comes from env, not ~/.netrc, so the step sits before the Homebrew bump, which must stay last because it deletes ~/.netrc.
• No untrusted input reaches the shell. The only values used are GITHUB_SHA and fixed strings.

Before merging (why this is a draft)

• Add the BREVO_SKILLS_SYNC_TOKEN secret to the npm-publish environment: a fine-grained token, or a GitHub App token, with actions: write on getbrevo/brevo-skills only
• sync-skill.yml must be on getbrevo/brevo-skills' default branch, because workflow_dispatch only finds workflows there

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[piyushsarin-sib]

Folded into #138 (commit a75ace2), so the skill install feature and the sync trigger ship together.