chore(release): bump nodeup-cli to 1.0.1 with binaryVersion sync and repo URL fix

[dipto0321]

Summary

Bump the nodeup-cli npm wrapper from 1.0.0 to 1.0.1 for the
r-publish. The original 1.0.0 (published 2026-07-01) was unpublished
earlier today after the bugs it shipped and the absence of the UI
features that landed on main after that publish came to light.
1.0.1 re-publishes the wrapper at a fresh version (npm enforces a
24h cooldown on re-publishing the same name+version) with the
package.json version, binaryVersion, and repository.url all
fixed in one commit so the wrapper, the Go binary tag, and the npm
metadata are coherent.

• version: 1.0.0 → 1.0.1
• binaryVersion: 1.0.0 → 1.0.1 (kept in lockstep with the wrapper
  version so install.js downloads v1.0.1 artifacts; git tag -a v1.0.1 on the merge commit will fire the matching Go release)
• repository.url: switched to the git+https://github.com/...
  form npm's modern metadata schema expects — silences the
  "auto-corrected" warning at publish time.

Linked issues

• Closes Release prep: publish nodeup-npm to npm registry on v1.0.0 cut #35 (the npm-publish arm of the v1.0.0 release prep)
• Builds on PR chore(release): ship npm wrapper and install-method guidance #34 (the wrapper itself) and PR docs(release): update npm publish flow for the post-Dec-2025 token model #38 (post-Dec-2025
  token model in docs/release-checklist.md)

Type of change

• feat — new feature (MINOR bump)
• fix — bug fix (PATCH bump)
• refactor — no behavior change
• perf — performance improvement
• docs — documentation only
• test — tests only
• chore — maintenance / dependency bump
• ci — CI/CD only
• build — build system only
• Breaking change (MAJOR bump) — explain below

Checklist

• Title follows Conventional Commits (chore(release): ...)
• I ran npm pack --dry-run and it produces exactly the 5 files
  the issue Release prep: publish nodeup-npm to npm registry on v1.0.0 cut #35 checklist requires (LICENSE, README.md,
  package.json, scripts/check.js, scripts/install.js), no
  warnings on the new repository.url form
• No tests to update — package.json is metadata only; the
  existing scripts/check_test.js and scripts/install_test.js
  don't pin version strings
• No docs to update — docs/release-checklist.md is
  version-agnostic
• No new linter warnings
• No breaking change

Screenshots / output

$ npm pack --dry-run
npm notice 📦  nodeup-cli@1.0.1
npm notice Tarball Contents
npm notice 1.1kB  LICENSE
npm notice 3.7kB  README.md
npm notice 993B   package.json
npm notice 3.5kB  scripts/check.js
npm notice 20.0kB scripts/install.js
npm notice Tarball Details
npm notice name: nodeup-cli
npm notice version: 1.0.1
npm notice filename: nodeup-cli-1.0.1.tgz
npm notice package size: 11.4 kB
npm notice unpacked size: 29.2 kB
npm notice shasum: 70c38ef76ff6a376fd3b9a157ad7f1b2e4747ee0
npm notice integrity: sha512-Jxx+QQBbpOBZS[...]9XqO+YwnqRQPw==
npm notice total files: 5

After this lands, the release flow is:

git checkout main
git pull
git tag -a v1.0.1 -m "Release v1.0.1"
git push origin v1.0.1
# release.yml fires → goreleaser → release + homebrew-tap + scoop-bucket
# publish-npm job → npm publish --provenance --access public (OIDC)
# nodeup-cli@1.0.1 lands on npmjs.com

🤖 Generated with puku-cli

[cocogitto-bot]

✔️ 63e14c7 - Conventional commits check succeeded.