No option to automate a release

[jv-k]

Status: scheduled for 2.0.0.
Plan: docs/v2.0-release-plan.md § M5 — --github-release flag

Summary

Add --github-release so ver-bump can publish a GitHub Release right after pushing the tag, using the CHANGELOG entry it just generated as the release notes.

Scope

• New long-only flag --github-release (no short form).
• Wired into the run sequence after do-push.
• Invokes gh release create <TAG> --title <TAG> --notes-file <tempfile> where <tempfile> holds the single-version CHANGELOG fragment.
• Preflight: require gh binary + clean gh auth status + -p <remote> supplied. Missing gh → exit 3.
• Dry-run: print [dry-run] gh release create <TAG> ... without executing.
• Exit codes: gh runtime failure → 1; auth/precondition → 3.

Tests (bats)

• --github-release without -p exits 2
• --github-release --dry-run prints expected invocation
• --github-release with no gh binary exits 3
• (Integration, opt-in) Sandbox invocation produces a visible release

Docs

• PRD: add R-GHR bucket to §5, update flag inventory §14, remove from §13 future work
• README: new subsection under Options
• --help output + completion scripts for all three shells

Non-goals

• Generating notes from conventional commits (deferred)
• Uploading release artefacts (binaries, tarballs)
• GitLab/Gitea parity

[jv-k]

related #43