Configure public access for scoped npm package

[randomm]

Summary

Configure the scoped npm package to be publicly accessible. While the EINVALIDNPMTOKEN CI failure is authentication-related, correctly setting the package access level is a mandatory prerequisite for successful npm package publishing.

Issue Description

The CI pipeline is failing with EINVALIDNPMTOKEN during the publish step. This error indicates authentication issues, but scoped npm packages also require explicit public access configuration to be published to the public npm registry. This issue addresses the package access configuration requirement.

Context

• CI Failure: EINVALIDNPMTOKEN during npm publish
• Root Cause: Combination of authentication and package access configuration
• Solution: Configure scoped package as public via .npmrc or package.json configuration

Quality Gates (Non-Negotiable)

• Configuration: Verify .npmrc or package.json settings for public access
• Testing: Test package.json configuration locally (npm config list)
• Documentation: Update README.md with npm publishing prerequisites
• Verification: Confirm public access configuration is correct before closing
• Local Verification: All checks pass before completion

Acceptance Criteria

• Scoped package is configured as public in appropriate config files
• npm config list shows correct access setting
• Documentation updated with public access requirement
• Ready for CI retry once authentication is also resolved