ci(release): authenticate snapshot changelog

[RedStar071]

🔗 Linked issue

N/A — maintenance follow-up with no linked issue.

🧭 Context

The Changesets v3 snapshot workflow versions packages with a custom changelog generator that queries the GitHub GraphQL API. The snapshot job did not expose a GitHub token, so generated snapshot changelog entries could lose commit, pull request, and author metadata.

📚 Description

This exposes WOLFSTAR_TOKEN as GITHUB_TOKEN only for the snapshot publish step and documents that additional use of the repository secret.

Key changes

• provide GITHUB_TOKEN while Changesets versions snapshot releases
• document the token requirement for the v3 changelog generator
• add an empty changeset because no package release is required

Type of Change

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation change
• Workflow / CI change

Pre-flight Checklist

• I have read the Contributing Guidelines (if applicable)
• My code follows the code style of this project
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have updated the documentation accordingly
• I added a changeset with pnpm changeset (or pnpm changeset add --empty if no release is needed). See .changeset/README.md.

Note

Expose WOLFSTAR_TOKEN as GITHUB_TOKEN to snapshot publish step

The v3 snapshot changelog generator queries GitHub during versioning, so it needs an authenticated token. The release workflow now maps secrets.WOLFSTAR_TOKEN to the GITHUB_TOKEN environment variable for the 'Publish snapshot' step. The changeset README is updated to reflect this, and an empty changeset file is added.

^{Macroscope summarized 68127a2.}