Publish the CLI to npm so npx major works

[josegironn]

Summary

• npm/major/ is the major package: a small Node launcher that runs the binary for the user's platform. The binaries come from @major-tech/major-<os>-<arch> packages listed as optionalDependencies, so npm installs only the matching one. No install scripts, which npm 12 no longer runs by default.
• npm/publish.sh packages GoReleaser's dist/ binaries, stamps the tag version, and publishes the four platform packages and then major. Versions already on npm are skipped, so make rerelease is safe.
• release.yml publishes through npm trusted publishing (GitHub OIDC): it adds id-token: write, uses Node 24 with the latest npm, and stores no npm token. This avoids the 2FA-bypass token deprecation.
• README gets an npm install section.
• major update detects npm installs (binary under node_modules): global installs run npm install -g major@latest, npx runs just get a note, instead of re-running install.sh.

Setup already done

• major (owned by jmgironn) and the four @major-tech/major-* packages exist on npm as 0.0.0.
• All five are linked to major-technology/cli and release.yml for trusted publishing.

Test plan

• Built all four binaries locally, ran publish.sh with npm pack in place of npm publish, installed the tarballs, and npx major --version printed the stamped version
• go test ./... passes, including a new npmInstallMethod path test; major update from a simulated _npx path reports npx
• First tagged release after merge publishes all five packages, then npx major --version works

🤖 Generated with Claude Code

https://claude.ai/code/session_01LoJ5NB4XUb8U8zKQyrAeH8

Made with Orca 🐋