npm CI publication of @ruvnet/[email protected] is blocked by registry authorization

The C5 release work is merged in #2382 and #2389. The provenance-enabled npm workflow completed tests, version/pack gates, tarball smoke tests and README claim checks, then the registry rejected the package PUT with E404 (missing package permission/access).

Failed run: https://github.com/ruvnet/RuView/actions/runs/40915263663
Commit: 5728b90
Package/version: @ruvnet/[email protected]
Workflow: .github/workflows/ruview-npm-release.yml
Environment: npm-release

The local npm identity/trusted-publisher read endpoints also returned E401. No workstation publish was attempted, no package permission was weakened, and no credentials are included here. The same workflow previously published 0.9.2 successfully on October 12.

Maintainer action: restore the package's existing CI publishing access (refresh the repository NPM_TOKEN secret or configure the intended npm trusted publisher for ruvnet/RuView, ruview-npm-release.yml, environment npm-release). See https://docs.npmjs.com/trusted-publishers/ . Do not post tokens in this issue.

After that external state changes: confirm 0.9.3 is still absent, dispatch the main-only workflow for harness/ruview with the intended dist-tag, and verify registry integrity/provenance plus the installed C5 plan. Do not bypass the CI-only npm publication rule.