release: investigate npm publish failure for v4.0.1 and confirm registry availability #452

Evidence

The v4.0.1 release workflow for commit 145dde10b17c078701829e6ce32218c80d5a2623 has a failed PublishNpm job, while PublishJsr succeeded. Checkout, dependency installation, and build succeeded; failure occurred at npm publish --provenance.

The npm job log reports:

npm error code E404
npm error 404 Not Found - PUT https://registry.npmjs.org/@nlib%2ftyping - Not found
npm error 404 The requested resource '@nlib/typing@4.0.1' could not be found or you do not have permission to access it.

This establishes a failure in that workflow run, not that the version is currently unavailable or that the failure's root cause is known. A fresh registry lookup from the review environment was blocked by its local network permissions, so current registry availability remains unverified.

Requested investigation

• Check whether @nlib/typing@4.0.1 is currently published on npm and whether its artifacts match the release commit.
• Identify the cause of this publishing failure, including the workflow's publishing identity and package/scope authorization as applicable.
• If the version is missing, restore the intended publication using the repository's release process.
• If it was subsequently published, record that evidence and determine whether the failed workflow needs remediation.

Acceptance criteria

• npm availability and published artifact correctness are confirmed.
• The historical failure is explained and any remaining publishing configuration problem is fixed.
• npm and JSR release status is clear to consumers.