fix: use workflow_run trigger for npm-publish (GITHUB_TOKEN releases don't emit events)

[ichoosetoaccept]

Summary

Fixes NPM Publish workflow not triggering automatically after semantic-release creates a release.

Root Cause

Releases created with GITHUB_TOKEN do NOT emit release events to trigger other workflows. This is a GitHub security feature to prevent infinite loops.

From semantic-release/github docs:

"However releases done with this token will NOT trigger release events to start other workflows."

Solution

Changed NPM Publish trigger from release: published to workflow_run (triggers after Release workflow completes successfully).

Additional Fixes

• prek hooks installed - Pre-commit hooks now run on gt create
• Trailing whitespace fixed in test files
• End-of-file fixed in test files
• typos config - Exclude CHANGELOG.md (contains git hashes that look like typos)
• .typos.toml added for typos configuration

Verification

• All pre-commit hooks pass ✅
• Build passes ✅
• knip clean ✅

[ichoosetoaccept]

• fix: use workflow_run trigger for npm-publish (GITHUB_TOKEN releases don't emit events) #39 👈 (View in Graphite)
• main

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

[ichoosetoaccept]

Merge activity

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

[github-actions]

🎉 This PR is included in version 0.3.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀