bump-versionlisted

<!-- managed-by: harness-setup --> # Bump Version Bumps the version field in the one file that actually carries it for this project's stack. Detection and the semver arithmetic are deterministic (delegated to the engine, not re-derived here); the only judgment call this skill makes is *which* bump type to suggest, and that suggestion always needs your confirmation before anything is written. ## Workflow ### 1 — Determine the bump type Find the last version tag: ``` git describe --tags --abbrev=0 ``` If a tag exists, read commits since it (`git log <tag>..HEAD --oneline`). Classify by Conventional Commits prefix: - `feat:` → **minor** - `fix:`, `perf:`, `refactor:`, `chore:`, `docs:`, etc. → **patch** - Any commit with `!` after the type (`feat!:`) or a `BREAKING CHANGE:` footer → **major** The suggested bump type is the highest-severity one found (major > minor > patch). If there's no tag, or commits don't follow Conventional Commits, say so plainly and ask the user for the bump type instead of guessing. **Always state the suggested type and why (which commits drove it), and get explicit confirmation before proceeding.** Never apply a bump the user hasn't confirmed. ### 2 — Apply the bump Once confirmed, call the engine — it detects the version file for this project's stack, computes the next semver, and rewrites it in place: ``` node ~/.harness-setup/engine/cli.js --root . --bump <patch|minor|major> ``` Two outcomes need to be handled explicitly, not worked aro