fix(ci): pin npm@11 for publish + add workflow_dispatch

[lukemacauley]

Follow-up to #59. With Node 20→24 fixed, the publish then failed at the actual publish step: npm install -g npm@latest now installs npm@12, whose provenance code fails with Cannot find module 'sigstore' (run).

• Pin npm@11 — the version that published every release through 0.13.0 (npm@12 provenance is broken).
• Add workflow_dispatch — v0.14.1's release already fired and failed, and immutable releases burn that tag, so this lets us publish the 0.14.1 already on main by manually running the workflow — no new version/tag needed.

After merge: run the Publish workflow on main → 0.14.1 to npm.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Added a manual publishing option for release workflows, letting maintainers publish the selected package version on demand.

• Bug Fixes

  • Improved release publishing reliability by using a pinned npm version, helping ensure provenance generation works consistently.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0bc7a40f-5321-48d7-9445-d663ed5762e5

📥 Commits

Reviewing files that changed from the base of the PR and between 4c7c648 and 2bba88a.

📒 Files selected for processing (1)

• .github/workflows/publish.yml

---

📝 Walkthrough

Walkthrough

The GitHub Actions publish workflow adds a workflow_dispatch trigger for manual publishing and pins the npm upgrade step to npm@11 instead of npm@latest, updating accompanying comments about Node/npm version compatibility.

Changes

Publish Workflow Update

Layer / File(s)	Summary
Trigger and npm pin .github/workflows/publish.yml	Adds a workflow_dispatch trigger for manual publishing and changes the npm upgrade step to install pinned npm@11 instead of npm@latest, updating related comments.

Estimated code review effort: 1 (Trivial) | ~3 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/publish-npm11-dispatch

---

_{Comment @coderabbitai help to get the list of available commands.}