chore: add standard-version for automated releases

[victorbruce]

🎯 What This PR Does

Implements automated semantic versioning, changelog generation, and simplifies Git workflow to Feature → Main.

✅ Changes

Added

• standard-version package for automated releases
• Release scripts in package.json:
  • npm run release - automatic version bump
  • npm run release:minor - minor version bump (new features)
  • npm run release:major - major version bump (breaking changes)
  • npm run release:patch - patch version bump (bug fixes)
  • npm run release:dry-run - test without changes
• .versionrc.json - standard-version configuration
• Initial CHANGELOG.md documenting v1.0.0 release
• Updated README with simplified workflow documentation

Changed

• Git workflow simplified: Feature → Main (removed dev branch)
• Branch protection now applies only to main
• All features go directly to main via PR

🚀 New Workflow

Before

main → dev → feature → dev → main
(2 PRs per feature, complex)

After

main → feature → main
(1 PR per feature, simple)

🔄 Release Process

# After PR merge to main
git checkout main
git pull origin main

# Run release (analyzes commits, bumps version, updates changelog)
npm run release

# Push with tags
git push --follow-tags origin main

📋 How It Works

Conventional commits drive everything:

feat: add Angular Material      → v1.0.0 → v1.1.0 (MINOR)
fix: resolve build issue        → v1.0.0 → v1.0.1 (PATCH)
feat!: upgrade to Angular 21    → v1.0.0 → v2.0.0 (MAJOR)

standard-version automatically:

• ✅ Analyzes commits since last tag
• ✅ Determines correct version bump
• ✅ Updates package.json versions
• ✅ Generates CHANGELOG.md entry
• ✅ Creates git commit and tag

🧪 Testing

• Dry run successful: npm run release:dry-run
• All scripts added and tested
• Configuration file validated
• Documentation comprehensive
• Conventional commit format verified
• CI pipeline passes

📚 Documentation

Added to README:

• Simplified Git Flow explanation
• Semantic versioning guide
• Release process with examples
• Conventional commit format reference
• Step-by-step feature creation guide

🗑️ Cleanup

• Branch dev removed (simplified workflow)
• Branch protection updated (only main protected)
• All future features target main directly

🔄 Next Steps After Merge

1. Remove dev branch protection (if exists)
2. First release with standard-version:

   git checkout main
   git pull origin main
   npm run release:patch  # 1.0.0 → 1.0.1
   git push --follow-tags origin main

3. Verify:
   • package.json shows v1.0.1
   • CHANGELOG.md updated
   • Git tag v1.0.1 exists on main
   • GitHub release can be created from tag

📖 Resources

• Standard-Version
• Conventional Commits
• Semantic Versioning

---

Type: Tooling & Workflow improvement
Breaking Changes: None (infrastructure only)
Version: No bump (will be v1.0.1 after merge)