[Pepps233]

Summary

Enable private-source npm publication with exact per-package OIDC trust and verified bootstrap tags and tarball identities.

The owner approved public bootstrap of the current 0.2.0 payloads after validation and confirmed the /cl refresh.

Reasoning

The publisher forced provenance that npm does not support for private repositories.

Bootstrap also needed explicit registry/tag verification, and publication credential boundaries needed repeatable validation.

The source repository remains private and the public cloud contract continues to describe verified npm availability.

Changes

• Pin npm publication to npmjs.org and explicitly disable unsupported private-source provenance.
• Verify all eleven exact GitHub workflow/environment/publish relationships and canonical repository metadata.
• Verify bootstrap tarball bytes and tags, reject existing latest tags, and preserve partial-publication retries without R2 announcement.
• Add independent read-only production/staging bucket-scope checks to the manual verification workflow.
• Record the configured npm-publish environment and the owner-approved ref-only fallback after GitHub rejected required reviewers.
• Fix a concurrent-session test that raced asynchronous startup against a fixed 10 ms delay.

Testing

• npm run check and the full isolated ./test.sh passed.
• Publication/trust/credential regressions passed; Actionlint and the mirrored cloud release contract passed.
• Cloud root npm run check passed, including all 546 unit and 23 integration tests and a clean dependency audit.
• Staging publication and HTTP run 34762316585 passed and confirmed fixture/lock cleanup.
• Frozen bootstrap build, final payload inspection, and registry dry run passed for candidate e3f96b95ebc7fdad96220e315ec144f74383de22.
• Current candidate native acceptance, actual bootstrap, trust inspection, and npm token restrictions are in progress; final operational evidence will be added before review.

The new credential-scope checks need execution after this workflow reaches main because publication environment restrictions do not admit pull-request refs.
The historical reference to an unnamed older R2 key is not evidence of an active credential and does not justify revocation.
No production release pointer or generally available announcement is created by bootstrap.