fix(release): publish calculated next snapshot versions instead of 0.0.0-next

[RedStar071]

🔗 Linked issue

🧭 Context

The snapshot publishing workflow needs to generate more unique version identifiers to avoid conflicts and improve traceability of snapshot releases.

📚 Description

Updated the Changesets configuration to use calculated snapshot versions with a datetime-based prerelease template. This change affects how snapshot versions are generated when publishing pre-release packages to the next dist-tag.

Previously, snapshots used sequential numbering (e.g., 1.2.3-next.0). With this change, snapshots now include a datetime component (e.g., 1.2.3-next-20260816123456), making each snapshot version globally unique and easier to trace back to when it was generated.

Key changes

Aspect	Before	After
Snapshot version format	1.2.3-next.0	1.2.3-next-20260816123456
Changesets config	Sequential snapshots	Calculated snapshots with datetime
Documentation	References old format	Updated to reflect new format

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 updated the documentation accordingly
• I added a changeset with pnpm changeset (or pnpm changeset add --empty if no release is needed)

https://claude.ai/code/session_01NimzbbWZvM5URWRBrYjjNJ

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}