docs: add the trusted publishing recipe to the docs and the skills

[dangreen]

Summary

Documents the token-less npm publishing flow already running in nano_kit, Argue, and nanoviews, and teaches both agent skills about it.

New page: GitHub Action → Trusted Publishing

• Requirements from the npm docs: public npm registry on GitHub-hosted runners, npm CLI 11.5.1+ (Node.js 24 ships it, Node.js 22 ships npm 10), the package must already exist on npm, one registration per package and per workflow file.
• Setup: register the trusted publisher on npmjs.com or with npm trust github ... --file release.yml --allow-publish; in the release job add id-token: write, drop registry-url and npm-token, use Node.js 24. The expected publish log with the provenance lines is shown, taken from a real nano_kit release.
• Snapshots: the registration is bound to the workflow file, so the snapshot job is folded into release.yml behind a snapshot dispatch input with if: inputs.snapshot == '' on check — the layout from nano_kit and nanoviews, verified by their dispatch runs. The separate snapshot.yml remains possible with a second registration (npm allows up to ten per package).
• Provenance: automatic for public repositories, opt-out via publishConfig.provenance.
• ENEEDAUTH causes.

Existing pages — release automation, snapshot release, action inputs, and agent skills link to the new page.

Skills

• setup-simple-release-action: the token-or-trusted-publishing choice joins the single add-ons question; detection from existing workflows (id-token: write, no token); prerequisites including the npm view <name> version existence check; the trusted publishing workflow variation; the folded snapshot layout; the registration steps in the final checklist.
• simple-release-action: recognizes the layout when reading the setup, dispatches snapshots through release.yml, and diagnoses ENEEDAUTH.

Test plan

• Docs build (pnpm docs:build) with the lockfile from build(website): update astro and @astrojs/markdown-remark to satisfy Starlight 0.42 peers #197: 23 pages, the new page and its sidebar entry render
• Frontmatter, fences, internal links, and anchors validated
• Merge build(website): update astro and @astrojs/markdown-remark to satisfy Starlight 0.42 peers #197 first so the Website workflow can deploy this

🤖 Generated with Claude Code

[coveralls]

Coverage Report for CI Build 33973681226

Coverage remained the same at 69.769%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	1046
Covered Lines:	725
Line Coverage:	69.31%
Relevant Branches:	211
Covered Branches:	152
Branch Coverage:	72.04%
Branches in Coverage %:	Yes
Coverage Strength:	11.05 hits per line

---

💛 - Coveralls