docs: Refactor comparison guide to emphasize SemVer mode and minor README updates

Comparison Guide improvements:
- Restructure content to position SemVer floating versions as primary approach
- Update all comparison tables to highlight automatic dependency management
- Remove references to past tool limitations and "bridging the gap" language
- Present current capabilities without implying evolution from deficient state

Technical improvements:
- Fix asterisk escaping in floating version patterns (x.y.*, x.*)
- Ensure proper markdown rendering for version specifications
- Update section headings from "SemVer Mode: Bridging the Gap" to "SemVer Mode Features"
- Add "Agnostic Mode for Complex Cases" section for explicit control scenarios

Content enhancements:
- Emphasize zero-maintenance updates via floating patterns
- Highlight automatic compatibility resolution with clear error reporting
- Position SemVer as modern solution for source-level dependency management
- Update use cases to reflect automatic update capabilities
- Strengthen technical comparison sections with SemVer advantages

Consistency improvements:
- Align migration considerations with SemVer-first approach
- Update target user descriptions to include automatic update benefits
- Ensure all examples demonstrate SemVer floating version patterns
- Remove conclusion section that referenced previous tool versions

Additional README refinements:
- Minor formatting and content adjustments

The comparison guide now presents LsiGitCheckout as a mature tool with
sophisticated SemVer capabilities rather than a solution that evolved
to address past limitations.

Author: AndreaV-Lsi

README.md

@@ -10,8 +10,9 @@ A PowerShell script for managing multiple Git repositories with support for tags
 - [Basic Usage (Non-Recursive)](#basic-usage-non-recursive)
 - [Advanced Usage (Recursive Mode)](#advanced-usage-recursive-mode)
 - [Dependency Resolution Modes](#dependency-resolution-modes)
-- [API Compatibility Modes](#api-compatibility-modes)
-- [Checkout Tag Selection Algorithm](#checkout-tag-selection-algorithm)
+- [SemVer Mode](#semver-mode)
+- [Agnostic Mode](#agnostic-mode)
+- [Choosing Between Dependency Resolution Modes](#choosing-between-dependency-resolution-modes)
 - [Custom Dependency Files](#custom-dependency-files)
 - [Post-Checkout Scripts](#post-checkout-scripts)
 - [Security Best Practices](#security-best-practices)
@@ -156,7 +157,7 @@ Contains repository configurations without any credential information:
 }
 ```
 
-**Simple Array Format (Legacy Support):**
+**Simple Array Format (No Post-Checkout Scripts):**
 ```json
 [
   {
@@ -175,7 +176,7 @@ Contains repository configurations without any credential information:
 - **Repository URL** (required): Git repository URL (HTTPS or SSH)
 - **Base Path** (required): Local directory checkout path (relative or absolute)
 - **Dependency Resolution** (optional): "SemVer" (recommended) or "Agnostic" (default) - see [Dependency Resolution Modes](#dependency-resolution-modes)
-- **Version** (required for SemVer mode): Semantic version requirement (e.g., "2.1.0", "2.1.*", "2.*")
+- **Version** (required for SemVer mode): Semantic version requirement (e.g., "2.1.0", "2.1.\*", "2.\*")
 - **Version Regex** (optional, SemVer mode): Custom regex pattern for version extraction from tags
 - **Tag** (required for Agnostic mode): Git tag to checkout
 - **API Compatible Tags** (optional, Agnostic mode): List of API-compatible tags (can be in any order - automatic chronological sorting)
@@ -474,6 +475,33 @@ A tag-based resolution using exact tags and explicit API Compatible Tags lists.
 }
 ```
 
+### Version Management Rules
+
+When updating dependencies, simply add or remove versions from the API Compatible Tags array:
+
+1. **Adding a new compatible version** (e.g., v1.0.3 → v1.0.4):
+   - Add the new version to "API Compatible Tags" or update "Tag"
+   - Order doesn't matter - automatic sorting handles chronology
+   
+   ```json
+   {
+     "Tag": "v1.0.4",
+     "API Compatible Tags": ["v1.0.0", "v1.0.1", "v1.0.2", "v1.0.3"]
+   }
+   ```
+
+2. **Bumping to an incompatible version** (e.g., v1.0.3 → v2.0.0):
+   - Update "Tag" to the new version
+   - Clear or update "API Compatible Tags" for the new API version
+   
+   ```json
+   {
+     "Tag": "v2.0.0",
+     "API Compatible Tags": []
+   }
+   ```
+
+
 ### API Compatibility Modes in Agnostic Mode
 
 API compatibility modes control how version conflicts are resolved when multiple projects depend on the same repository. These modes apply to Agnostic mode repositories.