Rename update_dms to update-memory and document command streamlining

## Command Updates
- Renamed `/update_dms` → `/update-memory` for kebab-case consistency
- Updated all references across documentation, installation scripts, and agents

## Files Updated
- `.claude/commands/update_dms.md` → `.claude/commands/update-memory.md`
- Updated 8 files with command name references
- Updated both English and Chinese README files
- Updated installation scripts and agent documentation

## Documentation Enhancement
- Added comprehensive command streamlining section to CHANGELOG.md
- Documented removal of 4 redundant commands (context.md, sync.md)
- Documented cleanup of 10 legacy documentation files
- Highlighted 60% reduction in maintenance overhead

## Consistency Improvements
- Standardized command naming convention across entire system
- Enhanced session management documentation
- Improved error handling documentation for session registry

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

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

.claude/agents/memory-gemini-bridge.md

@@ -19,14 +19,14 @@ color: purple
 
 You are a Memory System Bridge Agent specializing in task-driven project analysis and Gemini CLI integration for CLAUDE.md documentation generation. Your primary focus is executing specific analysis tasks (not reading file contents) and performing targeted Gemini CLI commands to create hierarchical documentation.
 
-**Task Reception**: When called by update_dms command, you receive structured task instructions containing task type, analysis commands, target module, and context information. Execute the provided analysis commands and adapt your Gemini CLI analysis to the specific task requirements.
+**Task Reception**: When called by update-memory command, you receive structured task instructions containing task type, analysis commands, target module, and context information. Execute the provided analysis commands and adapt your Gemini CLI analysis to the specific task requirements.
 
 **Single Task Focus**: This agent processes one task at a time, focusing on the assigned module or scope without knowledge of other concurrent operations.
 
 ## Core Responsibilities
 
 You will:
-1. **Task Instruction Parsing**: Parse structured task instructions from update_dms with task type, analysis commands, target module, and context
+1. **Task Instruction Parsing**: Parse structured task instructions from update-memory with task type, analysis commands, target module, and context
 2. **Analysis Execution**: Execute task-specific analysis commands on the assigned module or scope
 3. **Documentation Generation**: Generate complete CLAUDE.md content for the assigned task
 4. **Gemini CLI Integration**: Execute targeted Gemini CLI commands for content analysis
@@ -92,7 +92,7 @@ ELSE:
 ## Task-Driven Execution Protocol
 
 ### Phase 1: Task Instruction Parsing
-Parse the task instruction received from update_dms:
+Parse the task instruction received from update-memory:
 ```json
 {
   "task_type": "module_update" | "global_summary",

.claude/commands/update-memory.md

@@ -1,16 +1,16 @@
 ---
-name: update_dms
+name: update-memory
 description: Distributed Memory System management with intelligent classification
-usage: /update_dms [mode] [target]
+usage: /update-memory [mode] [target]
 argument-hint: [full|fast|deep] [path or scope]
 examples:
-  - /update_dms                    # Fast mode on current directory
-  - /update_dms full               # Complete initialization
-  - /update_dms fast src/api/      # Quick update on specific path
-  - /update_dms deep auth-system   # Deep analysis on scope
+  - /update-memory                    # Fast mode on current directory
+  - /update-memory full               # Complete initialization
+  - /update-memory fast src/api/      # Quick update on specific path
+  - /update-memory deep auth-system   # Deep analysis on scope
 ---
 
-### 🚀 **Command Overview: `/update_dms`**
+### 🚀 **Command Overview: `/update-memory`**
 
 -   **Type**: Distributed Memory System (DMS) Management.
 -   **Purpose**: Manages a hierarchical `CLAUDE.md` documentation system using intelligent project classification and agent-based task integration.
@@ -47,7 +47,7 @@ examples:
 
 ### 🧠 **Parallel Execution Logic**
 
-This describes the command's internal logic for selecting an execution strategy. It is handled automatically by `/update_dms`.
+This describes the command's internal logic for selecting an execution strategy. It is handled automatically by `/update-memory`.
 
 ```pseudo
 FUNCTION select_execution_strategy(project_structure):
@@ -152,7 +152,7 @@ In `full` mode, the orchestrator generates tasks for agents in this JSON format.
 
 ### 🤖 **Agent Integration Examples**
 
-The `/update_dms` command orchestrates `memory-gemini-bridge` agents using tasks formatted like this.
+The `/update-memory` command orchestrates `memory-gemini-bridge` agents using tasks formatted like this.
 
 #### **Single Agent (Fast/Deep Mode)**
 ```yaml
@@ -263,4 +263,3 @@ The command auto-selects the optimal strategy. Below are the patterns it uses.
 -   **🔬 Deep Mode**: ~10-30 minutes with parallel execution.
 -   **🚀 Full Mode**: ~30-45 minutes with parallel execution.
 -   **Benefit**: Parallel execution provides a massive speedup, offsetting a small coordination overhead.
-

.claude/workflows/gemini-memory-bridge.md

@@ -45,7 +45,7 @@ Target: [project-name or specific scope]
 - **Hierarchy Recommendation**: Specific CLAUDE.md file structure with rationale
 - **Content Strategy**: Level-specific focus areas and content differentiation
 - **Template Selection**: Appropriate DMS and core templates for analysis
-- **Integration Plan**: Workflow coordination with update_dms and agent systems
+- **Integration Plan**: Workflow coordination with update-memory and agent systems
 - **Quality Standards**: Cross-system compatibility and maintenance guidelines
 
 Focus on architectural understanding for documentation strategy rather than implementation details."