Always use Craft for automated release/publish workflows in personal projects

When the user wants to release a package (e.g., fossilize), they consistently reach for Sentry's Craft tool rather than manual npm publish, semantic-release, or other alternatives. This applies even for personal/open-source projects. The pattern includes: setting up .craft.yml with npm OIDC + GitHub Release targets, adding release.yml (workflow_dispatch → craft prepare) and publish.yml (issue label → craft publish) GitHub Actions workflows, and modifying build workflows to upload artifacts. When something goes wrong with a release (wrong version, skipped version, bad commit), the user wants to fix the git state and re-trigger Craft rather than publish manually.