Add session status file creation rule across workflow commands

Updates all workflow commands to create .workflow/session_status.jsonl if it doesn't exist when checking for active sessions. This ensures consistent behavior across:

- gemini-chat.md: Added creation rule and updated workflow pseudocode
- gemini-execute.md: Added session file creation requirement
- gemini-mode.md: Updated session check process
- workflow/action-plan.md: Updated both session check locations
- task/replan.md: Added creation rule to session validation
- task/breakdown.md: Updated session check process
- workflow/brainstorm.md: Added creation rule to session registry query

Also includes cleanup of deprecated command files (context.md, sync.md) and documentation updates for task creation complexity escalation.

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

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

.claude/prompt-templates/plan.md

@@ -57,7 +57,7 @@ Your response **MUST** be in Chinese and structured in Markdown as follows:
 ### **代码修改规划方案 (Code Modification Plan)**
 
 ### **第一部分：需求分析与规划总览 (Part 1: Requirements Analysis & Planning Overview)**
-*   **1.1 用户原始需求结构化解析 (Structured Analysis of User's Original Requirements):**
+*   **1.1 用户原始需求结构化解析 (Structured Analysis of Users Original Requirements):**
     *   [将用户的原始需求拆解成一个或多个清晰、独立、可操作的要点列表。每个要点都是一个明确的目标。]
     *   **- 需求点 A:** [描述第一个具体需求]
     *   **- 需求点 B:** [描述第二个具体需求]
@@ -78,7 +78,7 @@ Your response **MUST** be in Chinese and structured in Markdown as follows:
     *   [清晰说明函数、类、方法或具体的代码区域，如果可能，指出大致行号范围。示例: 函数 `calculate_total_price` 内部，约第 75-80 行]
 
 *   **1.bis 相关原始代码片段 (Relevant Original Code Snippet):**
-    *   [**在此处引用需要修改或在其附近进行修改的、最相关的几行原始代码。** 这为开发者提供了直接的上下文。如果代码未提供，则注明“相关代码未提供，根据描述进行规划。]
+    *   [**在此处引用需要修改或在其附近进行修改的、最相关的几行原始代码。** 这为开发者提供了直接的上下文。如果代码未提供，则注明相关代码未提供，根据描述进行规划。]
     *   ```[language]
         // 引用相关的1-5行原始代码
         ```
@@ -109,16 +109,16 @@ Your response **MUST** be in Chinese and structured in Markdown as follows:
 ## VII. KEY DIRECTIVES & CONSTRAINTS
 1.  **Language**: **All** descriptive parts of your plan **MUST** be in **Chinese**.
 2.  **No Code Generation**: **Strictly refrain** from writing, suggesting, or generating any actual code. Your output is *purely* a descriptive modification plan.
-3.  **Focus on "What" and "Why", Illustrate "How" (Logic Sketch)**: Detail what needs to be done and why. The call flow sketch illustrates the *intended how* at a logical level, not implementation code.
-4.  **Completeness & Accuracy**: Ensure the plan is comprehensive. If information is insufficient, state assumptions clearly in the "思考过程 (Thinking Process)" and "必要上下文 (Necessary Context)".
+3.  **Focus on What and Why, Illustrate How (Logic Sketch)**: Detail what needs to be done and why. The call flow sketch illustrates the *intended how* at a logical level, not implementation code.
+4.  **Completeness & Accuracy**: Ensure the plan is comprehensive. If information is insufficient, state assumptions clearly in the 思考过程 (Thinking Process) and 必要上下文 (Necessary Context).
 5.  **Professional Standard**: Your plan should meet the standards expected of a senior technical document, suitable for guiding development work.
 
 ## VIII. SELF-CORRECTION / REFLECTION
 *   Before finalizing your response, review it to ensure:
-    *   The "思考过程 (Thinking Process)" clearly outlines your structured analytical approach.
-    *   All user requirements from "需求分析" have been addressed in the plan.
+    *   The 思考过程 (Thinking Process) clearly outlines your structured analytical approach.
+    *   All user requirements from 需求分析 have been addressed in the plan.
     *   The modification plan is logical, actionable, and sufficiently detailed, with relevant original code snippets for context.
-    *   The "修改理由 (Reason for Modification)" explicitly links back to the initial requirements.
+    *   The 修改理由 (Reason for Modification) explicitly links back to the initial requirements.
     *   All crucial context and risks are highlighted.
     *   The entire output is in professional, clear Chinese and adheres to the specified Markdown structure.
     *   You have strictly avoided generating any code.