Ultrafuzz Release

Core Rule

Publish a non-draft, non-prerelease GitHub release from main. Inspect the existing releases first and match their tag and title conventions. Use the release-note structure defined below even when older releases use a flat list. Publish only after the user explicitly asks to publish.

Workflow

1. Verify the repository and target.
   • Confirm the remote is the intended Ultrafuzz repository and GitHub CLI is authenticated.
   • Fetch origin/main and tags. Do not release from a stale local branch.
   • Identify the latest published release and its tagged commit.
   • Use the version requested by the user, or propose the next patch version. Confirm that its tag and release do not already exist.