claude-git-hooks 2.30.2 → 2.33.0

package/CHANGELOG.md

@@ -5,48 +5,119 @@ Todos los cambios notables en este proyecto se documentarán en este archivo.
 El formato está basado en [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 y este proyecto adhiere a [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.33.0] - 2026-03-20
+
+### ✨ Added
+- Always-on metrics system for code quality observability (#41) - collects structured JSONL events locally with 90-day retention for trend analysis
+- Team-based reviewer selection via GitHub Teams API (#115, #36) - automatically resolves team members and excludes PR author when selecting reviewers
+- New metrics module (`lib/utils/metrics.js`) with fire-and-forget event recording that never blocks callers
+- Metrics instrumentation for pre-commit analysis, commit message generation, PR creation, judge verdicts, and orchestration batches
+- Documented proven implementation patterns in CLAUDE.md covering testability, git operations, and architecture best practices
+
+### 🔧 Changed
+- Telemetry system now always enabled - removed opt-out toggle for consistent observability
+- Existing telemetry events dual-write to unified metrics system for consolidated analysis
+- PR statistics module now records to both legacy JSONL and new metrics system
+- Judge module switched from telemetry to metrics recording with richer event data including false positives and unresolved issues
+
+### 🗑️ Removed
+- Removed `system.telemetry` configuration option - metrics are now always collected locally
+- Removed telemetry disabled warnings from `batch-info` and `telemetry-cmd` commands
+
+
+## [2.32.0] - 2026-03-19
+
+### ✨ Added
+- Team-based reviewer selection using GitHub Teams API for Pull Requests (#36)
+- New `reviewer-selector.js` module for intelligent team member resolution with PR author exclusion
+- Support for `teamSlug` configuration in `config.github.pr` (defaults to 'automation')
+- Support for `excludeReviewers` configuration with remote and local config merging
+- New GitHub API methods: `listRepoTeams()` and `listTeamMembers()` for team resolution
+
+### 🔧 Changed
+- PR reviewer selection now prioritizes GitHub Teams API over CODEOWNERS file
+- Updated `createPullRequest()` to accept `teamReviewers` parameter for team-based review requests
+- Refactored `github-client.js` to focus on config-based fallback reviewers only
+- Enhanced reviewer exclusion logic to merge remote general, remote repo-specific, and local config sources
+- Updated documentation to reflect team-based reviewer workflow in CLAUDE.md and README files
+
+### 🗑️ Removed
+- CODEOWNERS file parsing and resolution logic from reviewer selection workflow
+- Methods `readCodeowners()` and `parseCodeownersReviewers()` from `github-client.js`
+
+
+## [2.31.1] - 2026-03-19
+
+### 🔧 Changed
+- Migrated authorization config repository from `claude-hooks-config` to `git-hooks-config` as the definitive source for permissions and labels
+- Centralized existing permissions and labels configuration in the definitive repository
+- Updated documentation in CLAUDE.md to reference the new `git-hooks-config` repository and document team-wide remote config pattern
+
+
+## [2.31.0] - 2026-03-19
+
+### ✨ Added
+
+- Remote config fetcher (`remote-config.js`) for centralized configuration from `git-hooks-config` repository with in-memory caching and graceful degradation
+- Label resolver (`label-resolver.js`) with 5-rule engine for automatic PR label resolution: preset, size (`size:S/M/L/XL`), quality (`breaking-change`, `security`, `performance`), merge strategy, and default labels
+- Automatic label resolution in `create-pr` command with remote config priority and local fallback support
+- Configurable size thresholds for PR size labels via remote config
+
+### 🔧 Changed
+
+- Updated `close-release` command to use the new label resolver instead of hardcoded merge strategy label
+- Refactored `create-pr` label handling to use dependency injection pattern for local fallback rules
+- Documentation updates in CLAUDE.md, README.md, and README-NPM.md describing the new label resolution system
+
+### 🐛 Fixed
+
+- Removed duplicate `authorization.js` entry in CLAUDE.md directory structure (#112)
+
 ## [2.30.2] - 2026-03-18
 
 ### 🔧 Changed
+
 - Authorization now uses GitHub's `role_name` field instead of legacy `permission` field for more accurate role mapping
 - Improved authorization error messages to show the actual GitHub permission that failed to map
 
 ### 🐛 Fixed
-- Fixed role mapping to use `write` instead of `push` to match GitHub's current API role names
 
+- Fixed role mapping to use `write` instead of `push` to match GitHub's current API role names
 
 ## [2.30.1] - 2026-03-17
 
 ### ✨ Added
+
 - Comprehensive Release Workflow Guide in CLAUDE.md documenting all workflow automation commands (check-coupling, create-release, shadow, revert-feature, close-release, back-merge) with step-by-step lifecycle, command details, and authorization model
 
 ### 🔧 Changed
-- Increased timeout for AI help commands from 30s to 60s to improve reliability of claude-hooks help queries and issue reporting
 
+- Increased timeout for AI help commands from 30s to 60s to improve reliability of claude-hooks help queries and issue reporting
 
 ## [2.30.0] - 2026-03-17
 
 ### ✨ Added
+
 - New `close-release` command for release-candidate finalization (#ISSUE-97) — soft-resets RC onto main, creates a single clean commit with feature list, force-pushes with lease, and creates PR to main with merge-commit strategy label
 - Support for `--auto-describe` flag to generate release description using Claude AI
 - Support for `--dry-run` flag to preview close-release actions without executing
 - Support for `--no-pr` flag to skip PR creation during release closure
 - New `back-merge` command for post-deploy branch synchronization (#105)
 
-
 ## [2.29.0] - 2026-03-17
 
 ### ✨ Added
+
 - Added `back-merge` command for post-deploy branch synchronization (#96) - automates the release close workflow: tags release, resets shadow to main, merges main into develop, deletes RC branches, and offers to restore reverted features for the next sprint
 - Added automatic conflict resolution for version files during back-merge (accepts source/main version)
 - Added CHANGELOG conflict handling during back-merge - stages with conflict markers and prompts user to continue or abort
 - Added revert follow-up feature that reads revert-log.json and offers to apply revert-the-revert for features removed from the closed RC
 - Added branch protection detection during back-merge push with helpful PR creation advice
 
-
 ## [2.28.0] - 2026-03-17
 
 ### ✨ Added
+
 - New `revert-feature` command to revert squash-merged features by task ID in release-candidate branches (#95)
 - Coupling detection when reverting features - warns if other RC commits share modified files
 - Revert log tracking at `.claude/revert-log.json` for back-merge workflows
@@ -55,12 +126,13 @@ y este proyecto adhiere a [Semantic Versioning](https://semver.org/spec/v2.0.0.h
 - New `getCommitFiles()` utility in git-operations for retrieving files changed in a specific commit
 
 ### 🐛 Fixed
-- Added debug logging for git log failures in revert-feature command to aid troubleshooting
 
+- Added debug logging for git log failures in revert-feature command to aid troubleshooting
 
 ## [2.27.0] - 2026-03-17
 
 ### ✨ Added
+
 - New `create-release` command to automate release-candidate branch creation from develop (#94)
 - Automatic version file discovery and bump during release creation
 - Git tag creation with skip logic if tag already exists
@@ -71,23 +143,22 @@ y este proyecto adhiere a [Semantic Versioning](https://semver.org/spec/v2.0.0.h
 - Support for `--update-changelog` flag to generate CHANGELOG entry during release
 - Comprehensive precondition validation: clean working directory, develop branch check, remote sync verification, existing RC detection
 
-
 ## [2.26.0] - 2026-03-16
 
 ### ✨ Added
-- Merge strategy auto-detection in `create-pr` command - automatically detects required merge strategy (squash vs merge commit) from branch naming conventions (feature/* → squash, release-candidate/* → merge-commit, hotfix/* → merge-commit, any → main → merge-commit)
+
+- Merge strategy auto-detection in `create-pr` command - automatically detects required merge strategy (squash vs merge commit) from branch naming conventions (feature/_ → squash, release-candidate/_ → merge-commit, hotfix/\* → merge-commit, any → main → merge-commit)
 - Merge strategy labels (`merge-strategy:squash` or `merge-strategy:merge-commit`) automatically added to created PRs
 - Merge strategy display in PR preview showing detected strategy before creation
 - Body reminder prepended to PR description for merge-commit PRs warning about required merge method
 - Interactive merge strategy selection prompt when branch pattern is unknown or ambiguous
 - Shadow branch lifecycle management command (`claude-hooks shadow <analyze|reset|sync>`) for managing shadow branches - analyze divergence vs main and active RC, reset shadow to clean copy of main, or sync shadow with source branch (#101)
 
-
 ## [2.25.0] - 2026-03-16
 
 ### ✨ Added
-- New `shadow` command to manage the shadow branch lifecycle — analyze divergence vs main and active RC, reset shadow to a clean copy of main, or sync shadow with a source branch (RC, develop, feature)
 
+- New `shadow` command to manage the shadow branch lifecycle — analyze divergence vs main and active RC, reset shadow to a clean copy of main, or sync shadow with a source branch (RC, develop, feature)
 
 ## [2.24.0] - 2026-03-16