fix(release): chore/docs-only ranges yield none (revert #38 patch floor)

[AndreJorgeLopes]

What

Fixes two failing tests in tests/unit/release.bats on the v0.3.0 baseline.

Test 5 — _parse_conventional_commits (the real bug)

A chore-only commit range was classified as a patch bump instead of none, so chore/docs/refactor-only merges cut a release. Root cause: the "patch floor" added in #38 (2b693ab) flipped any none bump to patch to keep "merge = release". That contradicts conventional-commit rules, the documented release process, and the test at release.bats:66 (present since the parser's first commit 81558d2, never updated → started failing).

Fix: removed the patch floor. Only feat/fix/breaking cut a release now; a chore/docs-only range returns none.

Test 14 — bump_all_versions (stale fixture, same #38 cause)

Not a harness quirk. #38 changed the command badge format from [devflow vX.Y.Z] to bare [X.Y.Z], but test 14's fixture (description: "[devflow v0.1.0]...") and grep ([devflow v0.2.0]) were left stale, so the sed never matched and the badge assertion failed under bats. Aligned the fixture + grep to the bare [X.Y.Z] format the real devflow-plugin/commands/*.md files use.

Behavior change

Removing the patch floor reverts #38's "merge = release": a docs/chore-only merge to main no longer auto-releases (matches conventional rules + the documented process). To force a release for such a range, dispatch release.yml with bump_override — the escape hatch #38 was working around.

Verification

bats tests/unit/release.bats   → 16/16 green
make test-unit                 → 57/57 green
repro: chore-only → none · feat → minor · fix → patch

Follow-up (not in this PR)

CLAUDE.md still documents the old [devflow v0.1.0] badge format — stale from #38. Tracked separately to keep this diff scoped to the test failures.

🤖 Generated with Claude Code