When a stable release is cut via workflow_dispatch with channel=latest,
@latest can leapfrog the current @next head. Without a corresponding
prerelease publish, the @next dist-tag is left pointing at an older
version, which turns `npx bmad-method@next install` into a downgrade.
This is the root cause of #2317: @latest=6.5.0 but @next=6.4.1-next.0,
so users running `npx bmad-method@next install` get the older code
written over the newer.
Add a final step in the latest-channel branch that derives the next
prerelease (max(@next-stripped, @latest) bumped to -next.0) and
publishes it with --tag next, reusing the proven `npm publish
--provenance` flow rather than mutating dist-tags directly. Runs after
the GitHub Release and Discord notify steps so they still see the
stable version in package.json.
Refs #2317
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
cb95eb5a07