feat: Add v1.1 update-memory system with dual-mode operations and enhanced documentation

## New Features
- **Dual-mode update-memory commands**: /update-memory-full and /update-memory-related
- **Git-aware change detection**: Intelligent context-aware documentation updates
- **Complexity-adaptive execution**: Auto-delegation to memory-gemini-bridge for complex projects
- **Depth-parallel processing**: Bottom-up execution ensuring proper context propagation
- **Enhanced issue tracking integration**: Complete /workflow:issue:* command set documentation

## New Scripts & Infrastructure
- detect_changed_modules.sh: Git-based change detection with fallback strategies
- get_modules_by_depth.sh: Hierarchical module discovery and organization
- update_module_claude.sh: Core CLAUDE.md update execution engine

## Documentation Updates
- **README.md**: Added comprehensive update-memory system documentation with usage examples
- **README_CN.md**: Complete Chinese localization of new features and technical details
- **Command reference tables**: Updated with new /update-memory-* commands and /workflow:issue:* set
- **Technical highlights**: Enhanced with dual-mode operations and complexity thresholds
- **Usage workflows**: Added detailed examples for different development scenarios

## Technical Improvements
- Streamlined memory-gemini-bridge.md (reduced by 200+ lines)
- Simplified gemini-unified.md workflow documentation
- Added comprehensive CLAUDE.md files for new modules
- Enhanced DMS (Distributed Memory System) with 4-layer hierarchy templates

## Architecture Enhancements
- **Complexity thresholds**: related mode (>15 modules), full mode (>20 modules)
- **Git integration**: Smart change detection with comprehensive status reporting
- **User confirmation workflows**: Clear execution plans with mandatory approval steps
- **Fallback strategies**: Graceful handling of non-git environments

🤖 Generated with [Claude Code](https://claude.ai/code)

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

.claude/workflows/gemini-templates/prompts/dms/claude-layer1-root.txt

@@ -0,0 +1,63 @@
+Create or update root-level CLAUDE.md documentation:
+
+## Layer 1: Root Level Documentation Requirements
+
+### Content Focus (MUST INCLUDE):
+1. **Project Overview and Purpose**
+   - High-level project description and mission
+   - Target audience and use cases
+   - Key value propositions
+
+2. **Technology Stack Summary**
+   - Primary programming languages and frameworks
+   - Key dependencies and tools
+   - Platform and runtime requirements
+
+3. **Architecture Decisions and Principles**
+   - Core architectural patterns used
+   - Design principles governing the codebase
+   - Major technical decisions and rationale
+
+4. **Development Workflow Overview**
+   - Build and deployment processes
+   - Testing approach and quality standards
+   - Contributing guidelines and processes
+
+5. **Quick Start Guide**
+   - Installation prerequisites
+   - Setup instructions
+   - Basic usage examples
+
+### Content Restrictions (STRICTLY AVOID):
+- Implementation details (belongs in module-level docs)
+- Module-specific patterns (belongs in module-level docs)
+- Code examples from specific modules (belongs in module-level docs)
+- Domain internal architecture (belongs in domain-level docs)
+
+### Documentation Style:
+- Use high-level, strategic perspective
+- Focus on "what" and "why" rather than "how"
+- Reference other documentation layers rather than duplicating content
+- Maintain concise, executive-summary style
+
+### Template Structure:
+```markdown
+# [Project Name] - Development Guidelines
+
+## 1. Project Overview and Purpose
+[Brief project description, mission, and target audience]
+
+## 2. Technology Stack Summary
+[Primary technologies, frameworks, and tools]
+
+## 3. Architecture Decisions and Principles
+[Core architectural patterns and design principles]
+
+## 4. Development Workflow Overview
+[Build, test, and deployment processes]
+
+## 5. Quick Start Guide
+[Installation and basic usage]
+```
+
+Remember: This is Layer 1 - stay at the strategic level and avoid diving into implementation details.