release

The skill's footprint is coherent with a release automation purpose. It relies on standard, verifiable tooling (node/npm, GitHub via gh CLI) and uses normal project artifacts (package.json, CHANGELOG.md, route.ts) to synchronize and publish a new release. No suspicious or unnecessary credential access or data exfiltration patterns are evident. Overall risk is low to moderate, consistent with a controlled internal release workflow.