ci: gate releases on CI passing

[ichoosetoaccept]

Summary

Gates releases on CI passing to prevent broken commits from being published to npm/MCP Registry.

Problem

Previously, release.yml and ci.yml both triggered on push to main in parallel. This meant a broken commit could publish to npm/MCP Registry before CI caught the failure.

Solution

Changed release.yml to use workflow_run trigger:

• Waits for CI workflow to complete on main branch
• Only proceeds if CI passed (or if manually triggered via workflow_dispatch)
• Follows the pattern documented in ci-components README

Changes

• release.yml: Changed trigger from push to workflow_run on CI completion
• Added if condition to check workflow_run.conclusion == 'success'

[ichoosetoaccept]

• ci: gate releases on CI passing #35 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[ichoosetoaccept]

Merge activity

• Dec 30, 9:17 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Dec 30, 9:18 AM UTC: @ichoosetoaccept merged this pull request with Graphite.

[github-actions]

🎉 This PR is included in version 0.3.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀