Always reset package.json version to latest published npm version before letting Craft manage versioning

When setting up or fixing Craft-based publishing, reset package.json version to the latest version actually published on npm (not whatever is in the repo), then let Craft auto-determine the next version. Check npm view <pkg> version for the true latest. If Craft auto-versions to the already-published version (because package.json matches and no new conventional commits detected), re-run the release workflow with an explicit version (e.g. 0.6.0). Sync lockfiles after version change (npm install or pnpm install), then commit and trigger Craft.