[AI] Fix npm publish workflow for first public release

Author: intellectronica

.github/workflows/publish-npm.yml

@@ -41,12 +41,12 @@ jobs:
 
       - name: Publish prerelease to npm (next)
         if: github.event.release.prerelease == true
-        run: npm publish --tag next --provenance
+        run: npm publish --tag next --provenance --access public
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 
       - name: Publish release to npm (latest)
         if: github.event.release.prerelease == false
-        run: npm publish --provenance
+        run: npm publish --provenance --access public
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

AGENTS.md

@@ -142,5 +142,5 @@ When asked to create commits in this repository:
 
 - 2026-02-18 - Release-driven npm publishing
   - Context: Package publication should happen automatically when a GitHub release is published.
-  - Decision: Add a `publish-npm` GitHub Actions workflow triggered by `release.published`, using `NPM_TOKEN` and validating release tag/version alignment before `npm publish`.
-  - Consequence: Publishing is automated and guarded against accidental version/tag mismatches.
+  - Decision: Add a `publish-npm` GitHub Actions workflow triggered by `release.published`, using `NPM_TOKEN`, validating release tag/version alignment, and publishing with `--access public --provenance`.
+  - Consequence: Publishing is automated, guarded against version/tag mismatches, and works for first-time public package publication with provenance.