tree-sitter-analyzer 1.2.5__tar.gz → 1.3.3__tar.gz

tree_sitter_analyzer-1.3.3/.gitattributes

@@ -0,0 +1,51 @@
+# Set the default behavior for all files
+* text=auto
+
+# Explicitly declare text files you want to always be normalized and converted
+# to native line endings on checkout
+*.py text eol=lf
+*.md text eol=lf
+*.yml text eol=lf
+*.yaml text eol=lf
+*.toml text eol=lf
+*.txt text eol=lf
+*.json text eol=lf
+*.js text eol=lf
+*.ts text eol=lf
+*.html text eol=lf
+*.css text eol=lf
+*.sh text eol=lf
+*.bat text eol=crlf
+
+# Declare files that will always have CRLF line endings on checkout
+*.sln text eol=crlf
+
+# Denote all files that are truly binary and should not be modified
+*.png binary
+*.jpg binary
+*.jpeg binary
+*.gif binary
+*.ico binary
+*.mov binary
+*.mp4 binary
+*.mp3 binary
+*.flv binary
+*.fla binary
+*.swf binary
+*.gz binary
+*.zip binary
+*.7z binary
+*.ttf binary
+*.eot binary
+*.woff binary
+*.woff2 binary
+*.pyc binary
+*.pdf binary
+*.ez binary
+*.bz2 binary
+*.swp binary
+*.cache binary
+*.so binary
+*.dll binary
+*.dylib binary
+*.exe binary

{tree_sitter_analyzer-1.2.5 → tree_sitter_analyzer-1.3.3}/CHANGELOG.md

@@ -1,22 +1,191 @@
 # Changelog
 
-## [1.2.5] - 2025-09-15
+## [1.3.3] - 2025-01-15
 
 ### Fixed
-- Fixed MCP list_files tool failing to detect Java files in specific directories
-- Resolved fd command parameter ordering issue in Windows environment
-- Improved --search-path parameter usage for better cross-platform compatibility
+- **🔍 MCP Search Tools Gitignore Detection**: Added missing gitignore auto-detection to `find_and_grep_tool` for consistent behavior with other MCP tools
+- **⚙️ FD Command Pattern Handling**: Fixed fd command construction when no pattern is specified to prevent absolute paths being interpreted as patterns
+- **🛠️ List Files Tool Error**: Resolved fd command errors in `list_files_tool` by ensuring '.' pattern is used when no explicit pattern provided
+- **🧪 Test Coverage**: Updated test cases to reflect corrected fd command pattern handling behavior
 
 ### Technical Details
-- Modified `build_fd_command` in `fd_rg_utils.py` to use `--search-path` instead of positional arguments
-- Eliminated automatic `"."` pattern injection that caused command conflicts
-- Enhanced Windows environment compatibility for file discovery operations
+- **Root Cause**: Missing gitignore auto-detection in `find_and_grep_tool` and incorrect fd command pattern handling in `fd_rg_utils.py`
+- **Solution**: Implemented gitignore detector integration and ensured default '.' pattern is always provided to fd command
+- **Impact**: Fixes search failures in projects with `.gitignore` 'code/*' patterns and resolves fd command errors with absolute path interpretation
+- **Affected Tools**: `find_and_grep_tool`, `list_files_tool`, and `search_content_tool` consistency
 
-### Documentation Updates
-- Updated GitFlow documentation with comprehensive AI-assisted development workflow
-- Added complete bug fix and release automation procedures
-- Synchronized multi-language documentation (English, Chinese, Japanese)
-- Corrected PyPI deployment flow documentation to match actual GitHub Actions workflows
+This hotfix ensures MCP search tools work correctly across different project configurations and .gitignore patterns.
+
+## [1.3.2] - 2025-09-16
+
+### Fixed
+- **🐛 Critical Cache Format Compatibility Bug**: Fixed a severe bug in the smart caching system where `get_compatible_result` was returning wrong format cached data
+- **Format Validation**: Added `_is_format_compatible` method to prevent `total_only` integer results from being returned for detailed query requests
+- **User Impact**: Resolved the issue where users requesting detailed results after `total_only` queries received integers instead of proper structured data
+- **Backward Compatibility**: Maintained compatibility for dict results with unknown formats while preventing primitive data return bugs
+
+### Technical Details
+- **Root Cause**: Direct cache hit was returning cached results without format validation
+- **Solution**: Implemented format compatibility checking before returning cached data
+- **Test Coverage**: Added comprehensive test suite with 6 test cases covering format compatibility scenarios
+- **Bug Discovery**: Issue was identified through real-world usage documented in `roo_task_sep-16-2025_1-18-38-am.md`
+
+This hotfix ensures MCP tools return correctly formatted data and prevents cache format mismatches that could break AI-assisted development workflows.
+
+## [1.3.1] - 2025-01-15
+
+### Added
+- **🧠 Intelligent Cross-Format Cache Optimization**: Revolutionary smart caching system that eliminates duplicate searches across different result formats
+- **🎯 total_only → count_only_matches Optimization**: Solves the specific user pain point of "don't waste double time re-searching when user wants file details after getting total count"
+- **⚡ Smart Result Derivation**: Automatically derives file lists and summaries from cached count data without additional ripgrep executions
+- **🔄 Cross-Format Cache Keys**: Intelligent cache key mapping enables seamless format transitions
+- **📊 Dual Caching Mechanism**: total_only searches now cache both simple totals and detailed file counts simultaneously
+
+### Performance Improvements
+- **99.9% faster follow-up queries**: Second queries complete in ~0.001s vs ~14s for cache misses (14,000x improvement)
+- **Zero duplicate executions**: Related search format requests served entirely from cache derivation
+- **Perfect for LLM workflows**: Optimized for "total → details" analysis patterns common in AI-assisted development
+- **Memory efficient derivation**: File lists and summaries generated from existing count data without additional storage
+
+### Technical Implementation
+- **Enhanced SearchCache**: Added `get_compatible_result()` method for intelligent cross-format result derivation
+- **Smart Cache Logic**: `_create_count_only_cache_key()` enables cross-format cache key generation
+- **Result Format Detection**: `_determine_requested_format()` automatically identifies output format requirements
+- **Comprehensive Derivation**: `create_file_summary_from_count_data()` and `extract_file_list_from_count_data()` utility functions
+
+### New Files & Demonstrations
+- **Core Implementation**: Enhanced `search_cache.py` with cross-format optimization logic
+- **Tool Integration**: Updated `search_content_tool.py` with dual caching mechanism
+- **Utility Functions**: Extended `fd_rg_utils.py` with result derivation capabilities
+- **Comprehensive Testing**: `test_smart_cache_optimization.py` with 11 test cases covering all optimization scenarios
+- **Performance Demos**: `smart_cache_demo.py` and `total_only_optimization_demo.py` showcasing real-world improvements
+
+### User Experience Improvements
+- **Transparent Optimization**: Users get performance benefits without changing their usage patterns
+- **Intelligent Workflows**: "Get total count → Get file distribution" workflows now complete almost instantly
+- **Cache Hit Indicators**: Results include `cache_hit` and `cache_derived` flags for transparency
+- **Real-world Validation**: Tested with actual project codebases showing consistent 99.9%+ performance improvements
+
+### Developer Benefits
+- **Type-Safe Implementation**: Full TypeScript-style type annotations for better IDE support
+- **Comprehensive Documentation**: Detailed docstrings and examples for all new functionality
+- **Robust Testing**: Mock-based tests ensure CI stability across different environments
+- **Performance Monitoring**: Built-in cache statistics and performance tracking
+
+This release addresses the critical performance bottleneck identified by users: avoiding redundant searches when transitioning from summary to detailed analysis. The intelligent caching system represents a fundamental advancement in search result optimization for code analysis workflows.
+
+## [1.3.0] - 2025-01-15
+
+### Added
+- **Phase 2 Cache System**: Implemented comprehensive search result caching for significant performance improvements
+- **SearchCache Module**: Thread-safe in-memory cache with TTL and LRU eviction (`tree_sitter_analyzer/mcp/utils/search_cache.py`)
+- **Cache Integration**: Integrated caching into `search_content` MCP tool for automatic performance optimization
+- **Performance Monitoring**: Added comprehensive cache statistics tracking and performance validation
+- **Cache Demo**: Interactive demonstration script showing 200-400x performance improvements (`examples/cache_demo.py`)
+
+### Performance Improvements
+- **99.8% faster repeated searches**: Cache hits complete in ~0.001s vs ~0.4s for cache misses
+- **200-400x speed improvements**: Demonstrated with real-world search operations
+- **Automatic optimization**: Zero-configuration caching with smart defaults
+- **Memory efficient**: LRU eviction and configurable cache size limits
+
+### Technical Details
+- **Thread-safe implementation**: Uses `threading.RLock()` for concurrent access
+- **Configurable TTL**: Default 1-hour cache lifetime with customizable settings
+- **Smart cache keys**: Deterministic key generation based on search parameters
+- **Path normalization**: Consistent caching across different path representations
+- **Comprehensive testing**: 19 test cases covering functionality and performance validation
+
+### Documentation
+- **Cache Feature Summary**: Complete implementation and performance documentation
+- **Usage Examples**: Clear examples for basic usage and advanced configuration
+- **Performance Benchmarks**: Real-world performance data and optimization benefits
+
+## [1.2.5] - 2025-09-15
+
+### 🐛 Bug Fixes
+
+#### Fixed list_files tool Java file detection issue
+- **Problem**: The `list_files` MCP tool failed to detect Java files when using root path "." due to command line argument conflicts in the `fd` command construction
+- **Root Cause**: Conflicting pattern and path arguments in `build_fd_command` function
+- **Solution**: Modified `fd_rg_utils.py` to use `--search-path` option for root directories and only append pattern when explicitly provided
+- **Impact**: Significantly improved cross-platform compatibility, especially for Windows environments
+
+### 🔧 Technical Changes
+- **File**: `tree_sitter_analyzer/mcp/tools/fd_rg_utils.py`
+  - Replaced positional path arguments with `--search-path` option
+  - Removed automatic "." pattern addition that caused conflicts
+  - Enhanced command construction logic for better reliability
+- **Tests**: Updated `tests/test_mcp_fd_rg_tools.py`
+  - Modified test assertions to match new `fd` command behavior
+  - Ensured test coverage for both pattern and no-pattern scenarios
+
+### 📚 Documentation Updates
+- **Enhanced GitFlow Documentation**: Added comprehensive AI-assisted development workflow
+- **Multi-language Sync**: Updated English, Chinese, and Japanese versions of GitFlow documentation
+- **Process Clarification**: Clarified PyPI deployment process and manual steps
+
+### 🚀 Deployment
+- **PyPI**: Successfully deployed to PyPI as version 1.2.5
+- **Compatibility**: Tested and verified on Windows environments
+- **CI/CD**: All automated workflows executed successfully
+
+### 📊 Testing
+- **Test Suite**: All 156 tests passing
+- **Coverage**: Maintained high test coverage
+- **Cross-platform**: Verified Windows compatibility
+
+## [1.2.4] - 2025-09-15
+
+### 🚀 Major Features
+
+#### SMART Analysis Workflow
+- **Complete S-M-A-R-T workflow**: Comprehensive workflow replacing the previous 3-step process
+  - **S (Setup)**: Project initialization and prerequisite verification
+  - **M (Map)**: File discovery and structure mapping
+  - **A (Analyze)**: Code analysis and element extraction
+  - **R (Retrieve)**: Content search and pattern matching
+  - **T (Trace)**: Dependency tracking and relationship analysis
+
+#### Advanced MCP Tools
+- **ListFilesTool**: Lightning-fast file discovery powered by `fd`
+- **SearchContentTool**: High-performance text search powered by `ripgrep`
+- **FindAndGrepTool**: Combined file discovery and content analysis
+- **Enterprise-grade Testing**: 50+ comprehensive test cases ensuring reliability and stability
+- **Multi-platform Support**: Complete installation guides for Windows, macOS, and Linux
+
+### 📋 Prerequisites & Installation
+- **fd and ripgrep**: Complete installation instructions for all platforms
+- **Windows Optimization**: winget commands and PowerShell execution policies
+- **Cross-platform**: Support for macOS (Homebrew), Linux (apt/dnf/pacman), Windows (winget/choco/scoop)
+- **Verification Steps**: Commands to verify successful installation
+
+### 🔧 Quality Assurance
+- **Test Coverage**: 1564 tests passed, 74.97% coverage
+- **MCP Tools Coverage**: 93.04% (Excellent)
+- **Real-world Validation**: All examples tested and verified with actual tool execution
+- **Enterprise-grade Reliability**: Comprehensive error handling and validation
+
+### 📚 Documentation & Localization
+- **Complete Translation**: Japanese and Chinese READMEs fully updated
+- **SMART Workflow**: Detailed step-by-step guides in all three languages
+- **Prerequisites Documentation**: Comprehensive installation guides
+- **Verified Examples**: All MCP tool examples tested and validated
+
+### 🎯 Sponsor Acknowledgment
+Special thanks to **@o93** for sponsoring this comprehensive MCP tools enhancement, enabling the early release of advanced file search and content analysis features.
+
+### 🛠️ Technical Improvements
+- **Advanced File Search**: Powered by fd for lightning-fast file discovery
+- **Intelligent Content Search**: Powered by ripgrep for high-performance text search
+- **Combined Tools**: FindAndGrepTool for comprehensive file discovery and content analysis
+- **Token Optimization**: Multiple output formats optimized for AI assistant interactions
+
+### ⚡ Performance & Reliability
+- **Built-in Timeouts**: Responsive operation with configurable time limits
+- **Result Limits**: Prevents overwhelming output with smart result limiting
+- **Error Resilience**: Comprehensive error handling and graceful degradation
+- **Cross-platform Testing**: Validated on Windows, macOS, and Linux environments
 
 ## [1.2.3] - 2025-08-27
 
@@ -395,7 +564,7 @@
 
 ##### Test Coverage
 - **QueryService Tests**: 13 comprehensive unit tests
-- **QueryFilter Tests**: 29 detailed filtering tests  
+- **QueryFilter Tests**: 29 detailed filtering tests
 - **CLI Integration Tests**: 11 real-world usage scenarios
 - **MCP Tool Tests**: 9 tool definition and functionality tests
 
@@ -1257,7 +1426,7 @@ If you're using the MCP server, update your tool calls:
 **After:**
 ```json
 {
-  "tool": "analyze_code_structure", 
+  "tool": "analyze_code_structure",
   "arguments": { ... }
 }
 ```

{tree_sitter_analyzer-1.2.5 → tree_sitter_analyzer-1.3.3}/GITFLOW.md

@@ -9,30 +9,30 @@ gitGraph
     commit id: "Initial commit"
     branch develop
     commit id: "dev-1"
-    
+
     branch feature/my-feature
     commit id: "feat-1"
     commit id: "feat-2"
-    
+
     checkout develop
     merge feature/my-feature id: "merge-feat"
-    
+
     branch release/v1.0.0
     commit id: "release-prep"
-    
+
     checkout main
     merge release/v1.0.0 tag: "v1.0.0"
-    
+
     checkout develop
     merge release/v1.0.0
-    
+
     checkout main
     branch hotfix/critical-fix
     commit id: "fix-bug"
-    
+
     checkout main
     merge hotfix/critical-fix tag: "v1.0.1"
-    
+
     checkout develop
     merge hotfix/critical-fix
 ```
@@ -108,7 +108,18 @@ For manual releases:
 
 3. **Update documentation**:
    ```bash
-   uv run python scripts/improved_readme_updater.py
+   # Update README.md with new version, test counts, and coverage:
+   #   - Version badges ([![Version](https://img.shields.io/badge/version-X.X.X-blue.svg)])
+   #   - Test count badges ([![Tests](https://img.shields.io/badge/tests-XXXX%20passed-brightgreen.svg)])
+   #   - Coverage badges ([![Coverage](https://img.shields.io/badge/coverage-XX.XX%25-green.svg)])
+   #   - "Latest Quality Achievements" section version references
+   #   - Test environment section version references
+   #   - All other version mentions throughout the document
+   # Update README_zh.md and README_ja.md translations with same changes
+   # Update GITFLOW_zh.md and GITFLOW_ja.md if workflow changes were made
+   # Update CHANGELOG.md with release details
+   # Update version references throughout all documentation files
+   # Note: scripts/improved_readme_updater.py may not exist, do manual updates
    ```
 
 4. **Commit changes**:
@@ -123,7 +134,7 @@ For manual releases:
    git merge release/v1.0.0
    git tag -a v1.0.0 -m "Release v1.0.0"
    git push origin main --tags
-   
+
    git checkout develop
    git merge release/v1.0.0
    git push origin develop
@@ -153,21 +164,39 @@ For manual releases:
 3. **Update version** for hotfix:
    ```bash
    # Update pyproject.toml version (e.g., 1.0.0 -> 1.0.1)
+   # Update server_version in pyproject.toml
+   # Sync version to __init__.py
+   uv run python scripts/sync_version_minimal.py
    ```
 
-4. **Merge to main and develop**:
+4. **Update documentation**:
+   ```bash
+   # Update CHANGELOG.md with hotfix details
+   # Update README.md with new version, test counts, and coverage:
+   #   - Version badges ([![Version](https://img.shields.io/badge/version-X.X.X-blue.svg)])
+   #   - Test count badges ([![Tests](https://img.shields.io/badge/tests-XXXX%20passed-brightgreen.svg)])
+   #   - Coverage badges ([![Coverage](https://img.shields.io/badge/coverage-XX.XX%25-green.svg)])
+   #   - "Latest Quality Achievements" section version references
+   #   - Test environment section version references
+   #   - All other version mentions throughout the document
+   # Update README_zh.md and README_ja.md translations with same changes
+   # Update GITFLOW_zh.md and GITFLOW_ja.md if workflow changes were made
+   # Update version references throughout all documentation files
+   ```
+
+5. **Merge to main and develop**:
    ```bash
    git checkout main
    git merge hotfix/critical-bug-fix
    git tag -a v1.0.1 -m "Hotfix v1.0.1"
    git push origin main --tags
-   
+
    git checkout develop
    git merge hotfix/critical-bug-fix
    git push origin develop
    ```
 
-5. **Delete hotfix branch**:
+6. **Delete hotfix branch**:
    ```bash
    git branch -d hotfix/critical-bug-fix
    git push origin --delete hotfix/critical-bug-fix
@@ -210,6 +239,40 @@ uv run python scripts/automated_release.py
 
 ## Best Practices
 
+### Line Ending Configuration
+
+To prevent mixed line ending errors in pre-commit hooks:
+
+1. **Ensure `.gitattributes` exists** with proper configuration:
+   ```
+   * text=auto
+   *.py text eol=lf
+   *.md text eol=lf
+   *.yml text eol=lf
+   *.toml text eol=lf
+   ```
+
+2. **Configure Git locally**:
+   ```bash
+   git config core.autocrlf input
+   ```
+
+3. **Configure your editor** (VS Code example in `.vscode/settings.json`):
+   ```json
+   {
+     "files.eol": "\n",
+     "files.insertFinalNewline": true,
+     "files.trimTrailingWhitespace": true
+   }
+   ```
+
+4. **If you encounter mixed line ending errors**:
+   ```bash
+   # Re-normalize all files
+   git rm --cached -r . && git reset --hard HEAD
+   git add . && git commit -m "Normalize line endings"
+   ```
+
 ### Commit Messages
 
 Use conventional commit format:
@@ -253,195 +316,6 @@ Before merging to `develop`:
 - **Automatic versioning**: Managed by automated release process
 - **Version consistency**: All files updated together
 
-## 🤖 AI-Assisted Development Workflow
-
-### Complete Bug Fix & Release Automation
-
-This section provides a comprehensive workflow for AI assistants to handle bug fixes, version updates, and releases with minimal human intervention.
-
-#### 1. **Bug Fix Workflow**
-
-When fixing bugs, follow this automated sequence:
-
-```bash
-# 1. Check current branch and status
-git status
-git branch -v
-
-# 2. Create feature branch from develop
-git checkout develop
-git pull origin develop
-git checkout -b feature/fix-[bug-description]
-
-# 3. Fix the bug (already completed in this session)
-# - Edit the problematic files
-# - Test the fix locally
-
-# 4. Run comprehensive quality checks
-uv run pytest tests/ -v
-uv run python check_quality.py --new-code-only
-uv run python llm_code_checker.py --check-all
-
-# 5. Update version number (automatic patch increment)
-python -c "
-import re
-with open('pyproject.toml', 'r') as f:
-    content = f.read()
-current = re.search(r'version = \"(\d+)\.(\d+)\.(\d+)\"', content)
-if current:
-    major, minor, patch = map(int, current.groups())
-    new_version = f'{major}.{minor}.{patch + 1}'
-    new_content = re.sub(r'version = \"(\d+)\.(\d+)\.(\d+)\"', f'version = \"{new_version}\"', content)
-    with open('pyproject.toml', 'w') as f:
-        f.write(new_content)
-    print(f'Version updated to {new_version}')
-"
-
-# 6. Update CHANGELOG.md
-echo "
-## [$(python -c "import re; content=open('pyproject.toml').read(); print(re.search(r'version = \"([^\"]+)\"', content).group(1))")] - $(date +%Y-%m-%d)
-
-### Fixed
-- Fixed MCP list_files tool failing to detect Java files in specific directories
-- Resolved fd command parameter ordering issue in Windows environment
-- Improved --search-path parameter usage for better cross-platform compatibility
-
-### Technical Details
-- Modified \`build_fd_command\` in \`fd_rg_utils.py\` to use \`--search-path\` instead of positional arguments
-- Eliminated automatic \`\".\"\` pattern injection that caused command conflicts
-- Enhanced Windows environment compatibility for file discovery operations
-" >> CHANGELOG.md
-
-# 7. Update README statistics (if test count changed)
-uv run python scripts/improved_readme_updater.py
-
-# 8. Commit all changes
-git add .
-git commit -m "fix: Resolve MCP list_files tool Java file detection issue
-
-- Fix fd command parameter ordering in fd_rg_utils.py
-- Use --search-path for better cross-platform compatibility  
-- Update version to $(python -c "import re; content=open('pyproject.toml').read(); print(re.search(r'version = \"([^\"]+)\"', content).group(1))")
-- Update CHANGELOG.md and README statistics"
-
-# 9. Push feature branch
-git push origin feature/fix-[bug-description]
-```
-
-#### 2. **Automated Release Trigger**
-
-After bug fix is committed:
-
-```bash
-# 10. Merge to develop (triggers automated PR creation)
-git checkout develop
-git pull origin develop
-git merge feature/fix-[bug-description]
-git push origin develop
-
-# 11. Clean up feature branch
-git branch -d feature/fix-[bug-description]
-git push origin --delete feature/fix-[bug-description]
-```
-
-**Note**: Pushing to `develop` triggers the `develop-automation.yml` workflow which:
-1. Runs all tests and quality checks
-2. Builds the package
-3. Creates an automated PR from develop to main
-4. **Does NOT deploy to PyPI** (PyPI deployment happens only on release/hotfix branches)
-
-#### 3. **Actual Release Process**
-
-For PyPI deployment, you need to create a release branch:
-
-```bash
-# Create release branch for PyPI deployment
-git checkout develop  
-git pull origin develop
-git checkout -b release/v[new-version]
-git push origin release/v[new-version]
-```
-
-This triggers `release-automation.yml` which:
-- ✅ **Runs comprehensive tests**
-- ✅ **Builds and validates package**
-- ✅ **Deploys to PyPI automatically**
-- ✅ **Creates release-to-main PR**
-
-#### 4. **Post-Release Verification**
-
-After release branch is created, the automated system will handle:
-
-- ✅ **PyPI Deployment**: Package automatically published from release branch
-- ✅ **GitHub PR Creation**: Automated PR from release to main
-- ✅ **Quality Assurance**: All tests and builds verified
-- ⚠️ **Manual Step Required**: README updates need to be done manually
-
-Verify the release:
-
-```bash
-# Check PyPI deployment
-pip index versions tree-sitter-analyzer
-
-# Verify GitHub release
-gh release list
-
-# Check README updates
-git log --oneline -5
-```
-
-#### 5. **AI Assistant Checklist**
-
-When fixing bugs, AI assistants should automatically:
-
-- [ ] **Identify Root Cause**: Analyze the technical issue thoroughly
-- [ ] **Fix Implementation**: Apply the correct technical solution
-- [ ] **Version Increment**: Automatically bump patch version in pyproject.toml
-- [ ] **Update CHANGELOG**: Add detailed fix description with technical details
-- [ ] **Quality Checks**: Run all tests and linting locally
-- [ ] **Commit & Push**: Use conventional commit messages
-- [ ] **Merge to Develop**: Triggers automated testing and PR creation
-- [ ] **Create Release Branch**: For PyPI deployment (release/v[version])
-- [ ] **Manual README Update**: Update statistics if test count changed (not automated)
-- [ ] **Verify PyPI Deployment**: Check package publication after release branch
-
-#### 6. **Multi-language Documentation Sync**
-
-When updating GitFlow documentation, ensure all language versions are synchronized:
-
-```bash
-# Update all GitFlow documents
-# 1. GITFLOW.md (English - primary)
-# 2. GITFLOW_zh.md (Chinese)  
-# 3. GITFLOW_ja.md (Japanese)
-
-# Verify consistency
-diff -u GITFLOW.md GITFLOW_zh.md | head -20
-diff -u GITFLOW.md GITFLOW_ja.md | head -20
-```
-
-#### 7. **Emergency Hotfix Protocol**
-
-For critical production issues:
-
-```bash
-# 1. Create hotfix from main
-git checkout main
-git pull origin main
-git checkout -b hotfix/critical-[issue]
-
-# 2. Apply minimal fix
-# 3. Update version (patch increment)
-# 4. Update CHANGELOG
-# 5. Commit with hotfix message
-# 6. Merge to both main and develop
-# 7. Tag and push
-
-# Automated PyPI deployment will trigger immediately
-```
-
-This workflow ensures consistent, high-quality releases with minimal manual intervention while maintaining full traceability and documentation.
-
 ## CI/CD Integration
 
 ### GitHub Actions Workflows