chore: Rename project from LsiGitCheckout to RepoHerd

Rename all files and update all content references across the codebase:
- Renamed LsiGitCheckout.ps1/psm1/psd1 → RepoHerd.ps1/psm1/psd1
- Renamed test files and workspace file
- Updated all internal references (module name, function Initialize-RepoHerd,
  error file path, module import calls, Get-Module calls)
- Updated docs/, examples/, README, CHANGELOG, CLAUDE.md, index.html, tasks/

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: AndreaV-Lsi

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-All notable changes to LsiGitCheckout will be documented in this file.
+All notable changes to RepoHerd will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
@@ -16,7 +16,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Changed
 
 - **BREAKING**: Requires PowerShell 7.6 LTS or later (previously 5.1). PowerShell 7.6 installs side-by-side with Windows PowerShell 5.1.
-- Refactored monolithic script into module architecture: `LsiGitCheckout.psm1` (functions) + `LsiGitCheckout.ps1` (entry point)
+- Refactored monolithic script into module architecture: `RepoHerd.psm1` (functions) + `RepoHerd.ps1` (entry point)
 - Post-checkout scripts now execute via `pwsh` instead of `powershell.exe`
 - Replaced verbose null-check patterns with `??` null-coalescing operator
 - Entry point refactored to `try/catch/finally` pattern for guaranteed output file writing
@@ -32,11 +32,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - `Set-GitSshKeyOpenSsh` for Unix: validates key format, checks permissions, sets `GIT_SSH_COMMAND`
   - `Set-GitSshKeyPlink` for Windows: existing PuTTY/Pageant logic (unchanged behavior)
   - `Read-CredentialsFile` now warns about wrong key format for the current platform
-- `LsiGitCheckout.psm1` module file containing all function definitions
-- `LsiGitCheckout.psd1` module manifest
-- `Initialize-LsiGitCheckout` function for module state initialization
-- Automated unit tests using Pester 5.x (`tests/LsiGitCheckout.Unit.Tests.ps1`)
-- Automated integration tests for all 16 test configs (`tests/LsiGitCheckout.Integration.Tests.ps1`)
+- `RepoHerd.psm1` module file containing all function definitions
+- `RepoHerd.psd1` module manifest
+- `Initialize-RepoHerd` function for module state initialization
+- Automated unit tests using Pester 5.x (`tests/RepoHerd.Unit.Tests.ps1`)
+- Automated integration tests for all 16 test configs (`tests/RepoHerd.Integration.Tests.ps1`)
 - **Structured JSON output** via `-OutputFile` parameter for CI/CD pipeline integration
   - Schema version 1.0.0 with execution metadata, per-repository results, summary counters, and error messages
   - `Export-CheckoutResults` function generates the JSON output
@@ -169,7 +169,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `LSIGIT_REPOSITORY_URL`: Empty string
 - `LSIGIT_REPOSITORY_PATH`: Input dependency file directory path
 - `LSIGIT_TAG`: Empty string  
-- `LSIGIT_SCRIPT_VERSION`: Current LsiGitCheckout version
+- `LSIGIT_SCRIPT_VERSION`: Current RepoHerd version
 
 **Working Directory:** Input dependency file directory
 
@@ -224,7 +224,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Working Directory Management**: Ensures scripts always execute from the correct repository root directory
 
 ### Benefits
-- **Multi-System Integration**: Seamlessly integrate LsiGitCheckout with existing package managers and build systems
+- **Multi-System Integration**: Seamlessly integrate RepoHerd with existing package managers and build systems
 - **Automated Setup**: Automatically configure development environments after repository checkout
 - **Flexible Extensibility**: Support for custom post-checkout workflows via PowerShell scripting
 - **Zero Breaking Changes**: All existing dependency files continue to work without modification
@@ -298,7 +298,7 @@ Write-Host "Environment setup completed for $env:LSIGIT_REPOSITORY_PATH"
 - **Build Environment Setup**: Configure development environments after checkout
 - **License and Security Scanning**: Run automated compliance checks on checked-out code
 - **Custom Initialization**: Execute project-specific setup procedures
-- **Multi-System Orchestration**: Coordinate between LsiGitCheckout and other tools
+- **Multi-System Orchestration**: Coordinate between RepoHerd and other tools
 
 ## [6.1.0] - 2025-01-24
 
@@ -444,8 +444,8 @@ Correctly resolves to: /project/libs/shared (relative to repository root)
 - Enhanced user experience with no required parameters for optimal functionality
 
 ### Migration
-- **Old**: `.\LsiGitCheckout.ps1 -Recursive -EnableTagSorting` → **New**: `.\LsiGitCheckout.ps1` (default)
-- **Old**: `.\LsiGitCheckout.ps1 -Recursive:$false -EnableTagSorting:$false` → **New**: `.\LsiGitCheckout.ps1 -DisableRecursion -DisableTagSorting`
+- **Old**: `.\RepoHerd.ps1 -Recursive -EnableTagSorting` → **New**: `.\RepoHerd.ps1` (default)
+- **Old**: `.\RepoHerd.ps1 -Recursive:$false -EnableTagSorting:$false` → **New**: `.\RepoHerd.ps1 -DisableRecursion -DisableTagSorting`
 - All JSON configuration files work without modification
 - Functionality remains identical with improved parameter usability
 

CLAUDE.md

@@ -1,17 +1,17 @@
-# CLAUDE.md — LsiGitCheckout
+# CLAUDE.md — RepoHerd
 
 ## Project Overview
 
-PowerShell-based dependency management tool that checks out multiple Git repositories to specified versions. Module architecture: `LsiGitCheckout.psm1` (functions) + `LsiGitCheckout.ps1` (entry point). Version 8.0.1, by LS Instruments AG.
+PowerShell-based dependency management tool that checks out multiple Git repositories to specified versions. Module architecture: `RepoHerd.psm1` (functions) + `RepoHerd.ps1` (entry point). Version 8.0.1, by LS Instruments AG.
 
 ## Running the Tool
 
 ```powershell
-.\LsiGitCheckout.ps1                                    # defaults to dependencies.json
-.\LsiGitCheckout.ps1 -InputFile "path/to/deps.json"     # custom config
-.\LsiGitCheckout.ps1 -DryRun                             # preview without executing
-.\LsiGitCheckout.ps1 -EnableDebug -EnableErrorContext     # full debug output
-.\LsiGitCheckout.ps1 -OutputFile result.json             # structured JSON output
+.\RepoHerd.ps1                                    # defaults to dependencies.json
+.\RepoHerd.ps1 -InputFile "path/to/deps.json"     # custom config
+.\RepoHerd.ps1 -DryRun                             # preview without executing
+.\RepoHerd.ps1 -EnableDebug -EnableErrorContext     # full debug output
+.\RepoHerd.ps1 -OutputFile result.json             # structured JSON output
 ```
 
 Key parameters: `-InputFile`, `-CredentialsFile`, `-DryRun`, `-EnableDebug`, `-DisableRecursion`, `-MaxDepth` (default 5), `-ApiCompatibility` (Strict|Permissive), `-DisablePostCheckoutScripts`, `-EnableErrorContext`, `-OutputFile` (structured JSON results)
@@ -25,20 +25,20 @@ Key parameters: `-InputFile`, `-CredentialsFile`, `-DryRun`, `-EnableDebug`, `-D
 Install-Module Pester -Force -MinimumVersion 5.0
 
 # Unit tests — fast, no network required
-Invoke-Pester ./tests/LsiGitCheckout.Unit.Tests.ps1 -Output Detailed
+Invoke-Pester ./tests/RepoHerd.Unit.Tests.ps1 -Output Detailed
 
 # Integration tests — requires network access to GitHub test repos
-Invoke-Pester ./tests/LsiGitCheckout.Integration.Tests.ps1 -Output Detailed
+Invoke-Pester ./tests/RepoHerd.Integration.Tests.ps1 -Output Detailed
 ```
 
 ### Manual Testing
 
 Test configs in `tests/` are organized in subdirectories, each containing a `dependencies.json`:
 
 ```powershell
-.\LsiGitCheckout.ps1 -InputFile tests/semver-basic/dependencies.json
-.\LsiGitCheckout.ps1 -InputFile tests/agnostic-recursive/dependencies.json
-.\LsiGitCheckout.ps1 -InputFile tests/api-incompatibility-agnostic/dependencies.json -ApiCompatibility Strict
+.\RepoHerd.ps1 -InputFile tests/semver-basic/dependencies.json
+.\RepoHerd.ps1 -InputFile tests/agnostic-recursive/dependencies.json
+.\RepoHerd.ps1 -InputFile tests/api-incompatibility-agnostic/dependencies.json -ApiCompatibility Strict
 ```
 
 There are 17 test cases across 16 test configs covering SemVer, Agnostic, API incompatibility (Permissive + Strict), custom paths, post-checkout scripts, and recursive dependencies. See `docs/testing_infrastructure.md` for the full test architecture.
@@ -47,9 +47,9 @@ There are 17 test cases across 16 test configs covering SemVer, Agnostic, API in
 
 ## Architecture
 
-- **Module**: `LsiGitCheckout.psm1` — all function definitions (~35 functions)
-- **Entry point**: `LsiGitCheckout.ps1` — param block, module import, initialization, main execution
-- **Manifest**: `LsiGitCheckout.psd1` — module metadata, exported functions
+- **Module**: `RepoHerd.psm1` — all function definitions (~35 functions)
+- **Entry point**: `RepoHerd.ps1` — param block, module import, initialization, main execution
+- **Manifest**: `RepoHerd.psd1` — module metadata, exported functions
 - **Two dependency resolution modes**: SemVer (recommended, automatic version resolution) and Agnostic (explicit tag-based)
 - **Configuration**: JSON files — `dependencies.json` for repos, `git_credentials.json` for SSH keys
 - **Recursive processing**: walks dependency trees with conflict detection, max depth configurable
@@ -71,15 +71,15 @@ There are 17 test cases across 16 test configs covering SemVer, Agnostic, API in
 - **Logging**: use `Write-Log` with levels: Info, Warning, Error, Debug, Verbose
 - **Error handling**: wrap operations in `Invoke-WithErrorContext -Context "description" -ScriptBlock { ... }`
 - **Module state**: `$script:` prefix for module-scoped variables (e.g., `$script:RepositoryDictionary`, `$script:DryRun`)
-- **Initialization**: call `Initialize-LsiGitCheckout` to set module state from entry point parameters
+- **Initialization**: call `Initialize-RepoHerd` to set module state from entry point parameters
 - **CHANGELOG**: follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) format with SemVer versioning
 
 ## Project Structure
 
 ```
-LsiGitCheckout.ps1       # Entry point script (~230 lines)
-LsiGitCheckout.psm1      # Module with all functions (~2520 lines)
-LsiGitCheckout.psd1      # Module manifest
+RepoHerd.ps1       # Entry point script (~230 lines)
+RepoHerd.psm1      # Module with all functions (~2520 lines)
+RepoHerd.psd1      # Module manifest
 CHANGELOG.md             # Version history
 README.md                # Comprehensive user documentation
 docs/
@@ -90,8 +90,8 @@ docs/
   testing_infrastructure.md      # Test architecture, constraints, and categories
 examples/                # 7 example dependency JSON configs
 tests/                   # Pester test files + 16 test config subdirectories
-  LsiGitCheckout.Unit.Tests.ps1         # 65 unit tests (no network)
-  LsiGitCheckout.Integration.Tests.ps1  # 18 integration tests (needs network)
+  RepoHerd.Unit.Tests.ps1         # 65 unit tests (no network)
+  RepoHerd.Integration.Tests.ps1  # 18 integration tests (needs network)
   semver-basic/dependencies.json        # Test configs in subdirectories
   agnostic-recursive/dependencies.json  # (16 subdirectories total)
   api-incompatibility-*/dependencies.json

README.md

@@ -1,8 +1,8 @@
-# LsiGitCheckout
+# RepoHerd
 
 A cross-platform Git dependency management tool that automates cloning, checking out, and version-pinning of multiple repositories from a single JSON configuration. Designed for multi-repo projects where teams need reproducible builds without the complexity of git submodules or monorepo tooling.
 
-LsiGitCheckout resolves recursive dependencies across repository trees, supports both Semantic Versioning (SemVer) and tag-based version pinning, and handles SSH authentication (PuTTY on Windows, OpenSSH on macOS/Linux), Git LFS, and post-checkout script execution.
+RepoHerd resolves recursive dependencies across repository trees, supports both Semantic Versioning (SemVer) and tag-based version pinning, and handles SSH authentication (PuTTY on Windows, OpenSSH on macOS/Linux), Git LFS, and post-checkout script execution.
 
 ## Table of Contents
 
@@ -80,7 +80,7 @@ LsiGitCheckout resolves recursive dependencies across repository trees, supports
 
 4. **SSH setup** (only if accessing repositories via SSH URLs):
 
-   LsiGitCheckout uses PuTTY/plink on Windows. See [SSH Setup](docs/ssh_setup.md).
+   RepoHerd uses PuTTY/plink on Windows. See [SSH Setup](docs/ssh_setup.md).
 
 ### macOS
 
@@ -160,13 +160,13 @@ LsiGitCheckout resolves recursive dependencies across repository trees, supports
 
 ## Installation
 
-1. Download `LsiGitCheckout.ps1`, `LsiGitCheckout.psm1`, and `LsiGitCheckout.psd1` to the same directory
+1. Download `RepoHerd.ps1`, `RepoHerd.psm1`, and `RepoHerd.psd1` to the same directory
 2. Create `dependencies.json` with your repository configuration
 3. Create `git_credentials.json` with your SSH key mappings (if using SSH repositories)
 4. Run with `pwsh`:
 
    ```bash
-   pwsh ./LsiGitCheckout.ps1 -InputFile dependencies.json
+   pwsh ./RepoHerd.ps1 -InputFile dependencies.json
    ```
 
 ## Basic Usage (Non-Recursive)
@@ -179,34 +179,34 @@ In non-recursive mode, the script processes only the repositories listed in your
 
 ```powershell
 # Use default settings (recursive mode and intelligent tag sorting enabled by default)
-.\LsiGitCheckout.ps1
+.\RepoHerd.ps1
 
 # Specify custom JSON files
-.\LsiGitCheckout.ps1 -InputFile "C:\configs\myrepos.json" -CredentialsFile "C:\configs\my_credentials.json"
+.\RepoHerd.ps1 -InputFile "C:\configs\myrepos.json" -CredentialsFile "C:\configs\my_credentials.json"
 
 # Enable debug logging
-.\LsiGitCheckout.ps1 -EnableDebug
+.\RepoHerd.ps1 -EnableDebug
 
 # Dry run mode (preview without changes)
-.\LsiGitCheckout.ps1 -DryRun
+.\RepoHerd.ps1 -DryRun
 
 # Verbose output
-.\LsiGitCheckout.ps1 -Verbose
+.\RepoHerd.ps1 -Verbose
 
 # Set default API compatibility mode (applies only to Agnostic mode repositories)
-.\LsiGitCheckout.ps1 -ApiCompatibility Strict
+.\RepoHerd.ps1 -ApiCompatibility Strict
 
 # Disable recursive mode (non-recursive mode)
-.\LsiGitCheckout.ps1 -DisableRecursion
+.\RepoHerd.ps1 -DisableRecursion
 
 # Disable post-checkout script execution
-.\LsiGitCheckout.ps1 -DisablePostCheckoutScripts
+.\RepoHerd.ps1 -DisablePostCheckoutScripts
 
 # Enable detailed error context for debugging
-.\LsiGitCheckout.ps1 -EnableErrorContext
+.\RepoHerd.ps1 -EnableErrorContext
 
 # Export structured JSON results for CI/CD pipelines
-.\LsiGitCheckout.ps1 -OutputFile result.json
+.\RepoHerd.ps1 -OutputFile result.json
 ```
 
 ### Parameters
@@ -227,7 +227,7 @@ In non-recursive mode, the script processes only the repositories listed in your
 When `-OutputFile` is specified, a JSON file is written with the results of the checkout operation. The output is guaranteed to be written even on failure, making it safe for CI/CD pipelines. Schema version: **1.0.0**.
 
 ```powershell
-.\LsiGitCheckout.ps1 -InputFile deps.json -OutputFile result.json
+.\RepoHerd.ps1 -InputFile deps.json -OutputFile result.json
 ```
 
 **Output structure:**
@@ -261,7 +261,7 @@ When `-OutputFile` is specified, a JSON file is written with the results of the
 
 ### Understanding Dependency Resolution Modes
 
-LsiGitCheckout provides two approaches for determining which git tag to checkout for each repository. Both modes examine the available git tags in each repository to make their selection decisions.
+RepoHerd provides two approaches for determining which git tag to checkout for each repository. Both modes examine the available git tags in each repository to make their selection decisions.
 
 #### SemVer Mode (Recommended)
 
@@ -469,19 +469,19 @@ Maps hostnames to SSH key file paths. The key format depends on your platform:
 
 ```powershell
 # Default behavior (recursive mode enabled with intelligent tag sorting)
-.\LsiGitCheckout.ps1
+.\RepoHerd.ps1
 
 # Disable recursive mode for simple single-file processing
-.\LsiGitCheckout.ps1 -DisableRecursion
+.\RepoHerd.ps1 -DisableRecursion
 
 # Customize recursive behavior
-.\LsiGitCheckout.ps1 -MaxDepth 10
+.\RepoHerd.ps1 -MaxDepth 10
 
 # Use strict compatibility mode for Agnostic mode repositories
-.\LsiGitCheckout.ps1 -ApiCompatibility Strict
+.\RepoHerd.ps1 -ApiCompatibility Strict
 
 # Disable post-checkout scripts
-.\LsiGitCheckout.ps1 -DisablePostCheckoutScripts
+.\RepoHerd.ps1 -DisablePostCheckoutScripts
 ```
 
 ### Recursion and Discovering Common Dependencies
@@ -519,7 +519,7 @@ At this point, the script must determine:
 
 ## Dependency Resolution Modes
 
-LsiGitCheckout provides two powerful approaches to solve the dependency resolution problem:
+RepoHerd provides two powerful approaches to solve the dependency resolution problem:
 
 1. **SemVer Mode**: Automatically resolves compatible versions based on Semantic Versioning 2.0.0 rules with floating version support
 2. **Agnostic Mode**: Uses explicit "API Compatible Tags" lists with intelligent intersection/union algorithms
@@ -555,11 +555,11 @@ Common issues and solutions, debug mode instructions, and enhanced error context
 
 ## Version Migration Guide
 
-Step-by-step instructions for upgrading between LsiGitCheckout versions (6.2.x to 7.0.0, 7.0.0 to 7.1.0). For details, see [Version Migration Guide](docs/version_migration.md).
+Step-by-step instructions for upgrading between RepoHerd versions (6.2.x to 7.0.0, 7.0.0 to 7.1.0). For details, see [Version Migration Guide](docs/version_migration.md).
 
 ## Advanced Topics
 
-Links to in-depth guides on migrating dependency trees to LsiGitCheckout and tool comparisons. For details, see [Advanced Topics](docs/advanced_topics.md).
+Links to in-depth guides on migrating dependency trees to RepoHerd and tool comparisons. For details, see [Advanced Topics](docs/advanced_topics.md).
 
 ## License