Modernize task and workflow documentation architecture

Based on Gemini CLI analysis, updated all command documentation to align with current Single Source of Truth (SSoT) architecture.

## Key Updates

### Command Reference Modernization
- Updated all `/task:context` and `/workflow:context` references to unified `/context` command
- Removed all references to deprecated `/task:sync` and `/workflow:sync` commands
- Updated related commands sections across all task and workflow files

### Architecture Alignment
- Clarified JSON-first data model where `.task/*.json` files are authoritative
- Updated descriptions to reflect that markdown files are generated views, not synchronized documents
- Removed outdated "bidirectional sync" concepts in favor of automatic data consistency

### File Reference Standardization
- Fixed `TODO_CHECKLIST.md` → `TODO_LIST.md` naming inconsistencies
- Updated workflow integration examples to use proper command names
- Standardized command integration descriptions

### Documentation Consistency
- Aligned task creation, breakdown, execution, and replanning documentation with current architecture
- Updated workflow issue integration to reflect JSON-based task creation
- Enhanced CHANGELOG.md with comprehensive documentation modernization details

## Impact
- Eliminates confusion about deprecated commands
- Provides accurate guidance on current system behavior
- Aligns documentation with actual implementation
- Reduces maintenance overhead by removing outdated synchronization concepts

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

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

.claude/commands/task/breakdown.md

@@ -436,7 +436,7 @@ Post-breakdown validation:
 After breakdown:
 - `/task:execute` - Run subtasks using JSON task context
 - `/task:status` - View hierarchy from JSON files and TODO_LIST.md
-- `/task:context` - Analyze task relationships and JSON structure
+- `/context` - Analyze task relationships and JSON structure
 - `/task:replan` - Adjust breakdown and update task structure
 
 ## Examples

.claude/commands/task/create.md

@@ -397,8 +397,7 @@ Created 3 tasks:
 After creation, use:
 - `/task:breakdown` - Split into hierarchical subtasks with JSON files
 - `/task:execute` - Run the task with summary generation
-- `/task:context` - View task details and file references
+- `/context` - View task details, status and relationships
-- `/task:sync` - Validate file consistency across system
 
 ## Examples
 

.claude/commands/task/replan.md

@@ -460,7 +460,7 @@ Apply? (y/n): y
 ## Related Commands
 
 - `/task:breakdown` - Initial task breakdown with JSON file creation
-- `/task:context` - Analyze current state from file system
+- `/context` - Analyze current state from file system
 - `/task:execute` - Execute replanned tasks with new structure
-- `/task:sync` - Validate file consistency after replanning
+- `/context` - View updated task structure and relationships
 - `/workflow:replan` - Replan entire workflow with session updates

.claude/commands/workflow/implement.md

@@ -322,7 +322,7 @@ Always generates complete document suite:
 - Generates decomposition documents based on complexity triggers
 - Links documents to workflow-session.json with paths and status
 - Enables task commands (/task:*) with document integration
-- Starts progress tracking in both JSON and TODO_CHECKLIST.md
+- Initializes tasks in 'pending' state within their JSON files
 - Synchronizes task creation between documents and JSON states
 
 ### Next Actions

.claude/commands/workflow/issue.md

@@ -100,7 +100,7 @@ Integrates a specified issue into the current workflow plan.
         log("Executing integration...")
         // These steps correspond to the "集成步骤" in the example output.
         update_document("IMPL_PLAN.md")
-        update_document("TODO_CHECKLIST.md")
+        create_task_json_files("issue integration")
         update_tool_state("TodoWrite")
         update_session_file("workflow-session.json")
         log("Integration complete!")
@@ -134,9 +134,9 @@ Closes an issue that is completed or no longer relevant.
 ### 🤝 Command Integrations
 
 -   **Automatic Triggers**:
-    -   `/workflow:context`: Automatically displays the status of relevant issues.
+    -   `/context`: Displays the status of relevant issues and their integration with tasks.
     -   `/workflow:replan`: Can be automatically called by `integrate` to update the plan.
-    -   `/workflow:sync`: Ensures issue status is synchronized with project documents.
+    -   Issues are automatically integrated with the JSON-based workflow state.
 -   **Shared Data**:
     -   `workflow-session.json`: Stores core issue data and statistics.
     -   `WORKFLOW_ISSUES.md`: Provides a human-readable tracking document.

CHANGELOG.md

@@ -36,6 +36,14 @@
 - **ENHANCED**: Consistent session handling in gemini-chat, gemini-execute, gemini-mode, workflow commands
 - **IMPROVED**: Error handling for missing session registry files
 
+#### Documentation Modernization & Architecture Alignment
+- **UPDATED**: All command references to use unified `/context` command instead of deprecated `/task:context` and `/workflow:context`
+- **REMOVED**: All references to deprecated `/task:sync` and `/workflow:sync` commands
+- **ALIGNED**: Task and workflow documentation with Single Source of Truth (SSoT) architecture
+- **CLARIFIED**: JSON-first data model where `.task/*.json` files are authoritative and markdown files are generated views
+- **STANDARDIZED**: File naming consistency (TODO_CHECKLIST.md → TODO_LIST.md)
+- **ENHANCED**: Command integration descriptions to reflect automatic data consistency instead of manual synchronization
+
 ## [Previous] - 2025-01-28
 
 ### ✨ New Features