Add npm stable tag after refreshing npm auth

[ApolloZhangOnGithub]

Context

The installable CLI package is the unscoped npmjs package claude-nb, not a GitHub Packages package.

Observed on 2026-05-10:

• npm view claude-nb version dist-tags versions reports published versions 0.3.0, 0.4.0, and 0.5.1.
• npmjs dist-tags currently show only latest: 0.5.1; there is no stable tag yet.
• Attempting npm dist-tag add claude-nb@0.5.1 stable from the local machine failed with E401 because the npm token in ~/.npmrc is invalid.
• GitHub repo homepage has been set to https://www.npmjs.com/package/claude-nb so the real package is visible from the repository sidebar.
• README / CONTRIBUTING / docs now document that GitHub's repo Packages sidebar only shows GitHub Packages, not npmjs packages.

GitHub docs note that repository Packages lists packages published to GitHub Packages, and GitHub Packages npm publishing requires a scoped name such as @namespace/package-name. The current public install path is intentionally npm install -g claude-nb, so publishing the existing unscoped package to npm.pkg.github.com is not a safe one-line fix.

Why this matters

The repository can display "No packages published" even though claude-nb exists on npmjs.com. That is confusing for users and for future tongxue maintaining releases.

Acceptance criteria

• Refresh npm publisher authentication safely; do not commit tokens or logs.
• Add stable to the current supported npmjs release, or publish a new release first and then move both latest and stable to that release.
• Do not publish a -dev version to latest or stable.
• Verify with npm view claude-nb version dist-tags versions.
• Decide separately whether cnb needs a GitHub Packages companion package. If yes, open/attach a migration plan for a scoped package name and install-path documentation.
• Keep docs/package-publishing.md and CONTRIBUTING.md aligned with the final release workflow.

Related files

• README.md
• README_zh.md
• CONTRIBUTING.md
• docs/package-publishing.md
• package.json

[ApolloZhangOnGithub]

PR #102 has been merged, so the GitHub-visible documentation and package metadata are now on master. Reopening because the npm registry action is still blocked by publisher authentication: local npm whoami and npm dist-tag add claude-nb@0.5.1 stable returned E401. Remaining work is to refresh npm auth, then either add stable to the current supported release or publish a new non-dev release and move latest/stable there.

[ApolloZhangOnGithub]

GitHub Packages visibility is now fixed. PR #103 added the manual mirror workflow, and workflow run 25615986459 successfully published the scoped mirror package @apollozhangongithub/cnb@0.5.1 to GitHub Packages: https://github.com/ApolloZhangOnGithub/cnb/pkgs/npm/cnb

Repo About Website has also been cleared; it is no longer pointing at npm, docs, or issues.

Keeping this issue open only for the remaining npmjs registry task: refresh npm auth and add/move the stable dist-tag for the canonical claude-nb package.