chore(CI-CD): make version bump optional for README-only changes

[baxyz]

Description

Follow-up to a question about why dotfiles-sync went to 1.0.8 for a README-only fix: the version-bump-check job previously required a bump for any change under src/<name>/, including doc-only tweaks — every published version ended up byte-identical in actual container behavior to the previous one except for a bundled README diff.

Now the check only requires a bump when something other than README.md changed for the touched feature. A README-only change is logged as "optional" rather than failing the job. AGENTS.md updated to match, with the reasoning for why you might still want to bump a docs-only fix (it's the only way to get it onto the published website, since release.yml's version-diff gate also triggers the docs rebuild).

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Refactoring
• Test improvement

Related Issues

None.

How Has This Been Tested?

• js-yaml parse of the workflow file
• Reproduced the check's bash logic locally against 3 scenarios: README-only + no bump (passes), install.sh change + no bump (still fails), install.sh change + bump (passes)

Checklist

• My code follows the code style of this project
• I have updated the documentation accordingly
• I have added tests for my changes
• All new and existing tests passed locally
• My commits follow the conventional commit format

Screenshots (if applicable)

N/A.

Additional Context

None.

🤖 Generated with Claude Code

[github-actions]

✅ PR Validation Passed

All checks passed!

---

📋 Pipeline Status

	Job	Status
✅	🧾 Conventional Commits	passing
✅	🔖 Version Bump	passing
✅	🧪 Feature Tests	passing
✅	🐚 ShellCheck	passing

---

_{🤖 Generated by @helpers4 CI • 2026-08-08}