What problem does it solve? Publishing a TritonKit release requires keeping many package surfaces (CLI binaries, Homebrew formula, Web manifests, CocoaPods spec, public skill bundle) aligned to the same tag version, and a missed surface or moved tag breaks consumers. ## Core Features & Use Cases - Version Alignment: Defines the release boundary covering CLI assets, Web package.json/package-lock.json, TritonKit.podspec, and the public skill tarball, while noting SwiftPM has no version field. - Validation Workflow: Prescribes ordered gates including verify-release-package-versions.sh, verify-release-automation.sh, pod lib lint, npm build, and skill package verification before publishing via release.sh. - Recovery Rules: Documents how to handle wrong tags, observation races in GitHub Releases, truncated asset downloads, and Homebrew validation without moving published tags. - Use Case: A maintainer preparing v1.2.0 runs the pre-check script, updates the podspec and Web manifests, runs all validation gates, publishes through release.sh, then verifies GitHub assets, Homebrew upgrade, and a real triton web smoke test. ## Quick Start Ask the agent to prepare and publish TritonKit release v1.2.0 with all package surfaces aligned and validated.