Craft auto-version picks current package.json version — re-run with explicit version if already published

Trap: Craft's version: auto reads package.json and detects no new conventional commits → creates a publish issue for the version already on npm (e.g. 0.5.0 when 0.5.0 is already published). Looks like it should bump, but it doesn't if package.json already matches latest npm. Fix: close the stale publish issue, then re-trigger the release workflow with an explicit version string (e.g. 0.6.0). Craft will then create the correct release branch and publish issue.