## Summary
Fixed bash string formatting issues in the auto-squash workflow that
were causing YAML syntax errors and incorrect newline handling in
breaking change messages.

**Issue:** #34

## Type of Change
- [x] 🐛 Bug fix (patch version bump)
- [ ] ✨ New feature (minor version bump) 
- [ ] ⚡ Performance improvement (patch version bump)
- [ ] 🔄 Refactoring (no version bump)
- [ ] 📚 Documentation update (no version bump)
- [ ] 🧪 Test improvements (no version bump)
- [ ] 🔧 Build/CI changes (no version bump)

## Breaking Changes
- [ ] ⚠️ **This PR contains breaking changes** (major version bump)

---

## Testing
- [x] Unit tests added/updated and passing
- [x] Integration tests added/updated and passing  
- [x] Manual testing completed
- [x] Cross-platform compatibility verified (if applicable)

## Additional Notes
- Resolved YAML syntax error on line 113 caused by newlines in GitHub
output variables
- Fixed literal `\n\n` characters appearing instead of actual newlines
in breaking change messages
- Used `printf` for proper newline handling while maintaining YAML
compatibility
- This ensures the auto-squash workflow can properly format conventional
commit messages with breaking changes

## Pre-merge Checklist
- [x] Branch name follows convention:
`(feature|hotfix|epic)/{issue#}-description`
- [x] PR title follows new format: `{issue#}: {type}: {description}` (or
legacy format during transition)
- [x] All CI checks are passing (branch validation, tests, linting)
- [x] Code follows project conventions and style guide
- [x] Self-review completed
- [ ] Breaking changes properly documented (if applicable)
- [x] Ready for squash merge to main