Standardize release tagging flow with GoReleaser

[keyskey]

Summary

• rely on GoReleaser changelog generation for release notes and filter noisy commit prefixes
• add a SemVer tag helper script plus Make targets for patch/minor/major bumps
• document the tag-driven release workflow in README for consistent OSS-style operations

Test plan

• sh -n scripts/tag-next-version.sh
• make -n tag-next TYPE=patch
• make -n tag-major
• go test ./...

Made with Cursor

---

Note

Low Risk
Low risk: changes are limited to release tooling/configuration and documentation, with no impact on runtime behavior. Main risk is accidental tagging/changelog filtering affecting release notes.

Overview
Standardizes release operations by adding make targets plus scripts/tag-next-version.sh to create the next vX.Y.Z tag for patch|minor|major bumps.

Updates GoReleaser to generate release notes from git history in ascending order while filtering out noisy commit prefixes and merge/conflict messages, and documents the versioning policy and tag-driven release flow in README.md.

^{Reviewed by Cursor Bugbot for commit 712ce08. Bugbot is set up for automated code reviews on this repo. Configure here.}