fix(ci): auto-version-bump workflow false-positive when version already manually bumped

[jack-nsheaps]

Summary

The auto-version-bump GitHub Actions workflow on nsheaps/agents fails on every push to PR #157 because it tries to bump a version that has already been bumped manually in the same PR (task-utils 0.1.5 → 0.2.0, committed in R6). The workflow's git checkout fails with a conflict, the job exits non-zero, and the failure surfaces as a red CI check. This is not transient — it repros on every push.

The workflow should detect "current version is already at or beyond the computed target" and exit cleanly (success, no commit).

Requirements

• Reproduce the failure on a branch that has a manual version bump (PR Add opt-out for require-task-in-progress gate via env var #157 is a working example).
• Modify the auto-version-bump workflow to read the current version from plugin.json (or equivalent for the package type) BEFORE attempting the bump.
• If the current version equals the computed bump target, exit 0 with a log line explaining "version already at $target, no bump needed."
• If the current version is GREATER than the computed bump target (manual minor bump when only patch was implied), still exit 0 — user-driven bumps win.
• If the current version is less than the computed target, perform the bump as today.
• Add a workflow test (or document the manual repro) confirming the new branch in PR Add opt-out for require-task-in-progress gate via env var #157 no longer turns the check red.

Source

Identified during PR #157 work — see plan §"Out of scope" and report §"Skipped Items".

Related

• Blocked by: task-utils v0.2.0 R7 — in-session validation of redesigned hooks #168 (R7 validation must complete before Add opt-out for require-task-in-progress gate via env var #157 can merge; this fix is the next CI cleanup)
• PR: nsheaps/agents#157 — repro case
• Failing run example: job 77570780360

---

Issue created by Jack Oat (AI agent) on behalf of nsheaps.