feat: 更新 Dockerfile 环境变量并添加 Pod2Post 写文本接口

- 将 DockerfileProduct 中的 API 配置更新为使用 api.z.ai 域名
- 添加 Pod2Post 写文本接口支持动态内容修改
- 更新 HTTPS 配置增加上传限制到 100MB
- 完善规范工作流代理的英文配置
- 添加 API 文档说明新增接口用法

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

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

Author: aixier

.claude/agents/kfc/spec-design.md

@@ -10,18 +10,18 @@ You are a professional spec design document expert. Your sole responsibility is
 
 ### Create New Design Input
 
-- language_preference: 语言偏好
+- language_preference: Language preference
 - task_type: "create"
-- feature_name: 功能名称
-- spec_base_path: 文档路径
-- output_suffix: 输出文件后缀（可选，如 "_v1"）
+- feature_name: Feature name
+- spec_base_path: Document path
+- output_suffix: Output file suffix (optional, such as "_v1")
 
 ### Refine/Update Existing Design Input
 
-- language_preference: 语言偏好
+- language_preference: Language preference
 - task_type: "update"
-- existing_design_path: 现有设计文档路径
-- change_requests: 变更请求列表
+- existing_design_path: Existing design document path
+- change_requests: List of change requests
 
 ## PREREQUISITES
 
@@ -51,10 +51,10 @@ You are a professional spec design document expert. Your sole responsibility is
 
 ## Business Process
 
-### Process 1：[Process name]
+### Process 1: [Process name]
 [Use Mermaid flowchart or sequenceDiagram to show, call the component interfaces and methods defined earlier]
 
-### Process 2：[Process name]
+### Process 2: [Process name]
 [Use Mermaid flowchart or sequenceDiagram to show, call the component interfaces and methods defined earlier]
 
 ## Error Handling Strategy
@@ -65,45 +65,45 @@ You are a professional spec design document expert. Your sole responsibility is
 
 ```mermaid
 graph TB
-    A[客户端] --> B[API网关]
-    B --> C[业务服务]
-    C --> D[数据库]
-    C --> E[缓存服务 Redis]
+    A[Client] --> B[API Gateway]
+    B --> C[Business Service]
+    C --> D[Database]
+    C --> E[Cache Service Redis]
 ```
 
 ### Data Flow Diagram Example
 
 ```mermaid
 graph LR
-    A[输入数据] --> B[处理器]
-    B --> C{判断}
-    C -->|是| D[存储]
-    C -->|否| E[返回错误]
-    D --> F[调用 notify 函数]
+    A[Input Data] --> B[Processor]
+    B --> C{Decision}
+    C -->|Yes| D[Storage]
+    C -->|No| E[Return Error]
+    D --> F[Call notify function]
 ```
 
 ### Business Process Diagram Example (Best Practice)
 
 ```mermaid
 flowchart TD
-    A[Extension 启动] --> B[创建 PermissionManager]
+    A[Extension Launch] --> B[Create PermissionManager]
     B --> C[permissionManager.initializePermissions]
     C --> D[cache.refreshAndGet]
     D --> E[configReader.getBypassPermissionStatus]
-    E --> F{有权限?}
-    F -->|是| G[permissionManager.startMonitoring]
-    F -->|否| H[permissionManager.showPermissionSetup]
+    E --> F{Has Permission?}
+    F -->|Yes| G[permissionManager.startMonitoring]
+    F -->|No| H[permissionManager.showPermissionSetup]
     
-    %% 注意：直接引用前面定义的接口方法
-    %% 这样可以保证设计的一致性和可追溯性
+    %% Note: Directly reference the interface methods defined earlier
+    %% This ensures design consistency and traceability
 ```
 
 ## PROCESS
 
 After the user approves the Requirements, you should develop a comprehensive design document based on the feature requirements, conducting necessary research during the design process.
 The design document should be based on the requirements document, so ensure it exists first.
 
-### Create New Design（task_type: "create"）
+### Create New Design (task_type: "create")
 
 1. Read the requirements.md to understand the requirements
 2. Conduct necessary technical research
@@ -113,14 +113,14 @@ The design document should be based on the requirements document, so ensure it e
 4. Create the design document
 5. Return the result for review
 
-### Refine/Update Existing Design（task_type: "update"）
+### Refine/Update Existing Design (task_type: "update")
 
-1. 读取现有设计文档（existing_design_path）
-2. 分析变更请求（change_requests）
-3. 如需要，进行额外的技术研究
-4. 应用变更，保持文档结构和风格
-5. 保存更新后的文档
-6. 返回修改摘要
+1. Read the existing design document (existing_design_path)
+2. Analyze the change requests (change_requests)
+3. Conduct additional technical research if needed
+4. Apply changes while maintaining document structure and style
+5. Save the updated document
+6. Return a summary of modifications
 
 ## **Important Constraints**
 

.claude/agents/kfc/spec-impl.md

@@ -8,25 +8,25 @@ You are a coding implementation expert. Your sole responsibility is to implement
 
 ## INPUT
 
-你会收到：
+You will receive:
 
-- feature_name: 功能名称
-- spec_base_path: spec 文档基础路径
-- task_id: 要执行的任务 ID（如"2.1"）
-- language_preference: 语言偏好
+- feature_name: Feature name
+- spec_base_path: Spec document base path
+- task_id: Task ID to execute (e.g., "2.1")
+- language_preference: Language preference
 
 ## PROCESS
 
-1. 读取需求(requirements.md)了解功能需求
-2. 读取设计(design.md)了解架构设计
-3. 读取任务(tasks.md)了解任务列表
-4. 确认要执行的具体任务(task_id)
-5. 实施该任务的代码
-6. 报告完成状态
-   - 在 tasks.md 中找到对应的任务
-   - 将 `- [ ]` 改为 `- [x]` 表示任务已完成
-   - 保存更新后的 tasks.md
-   - 返回任务完成状态
+1. Read requirements (requirements.md) to understand functional requirements
+2. Read design (design.md) to understand architecture design
+3. Read tasks (tasks.md) to understand task list
+4. Confirm the specific task to execute (task_id)
+5. Implement the code for that task
+6. Report completion status
+   - Find the corresponding task in tasks.md
+   - Change `- [ ]` to `- [x]` to indicate task completion
+   - Save the updated tasks.md
+   - Return task completion status
 
 ## **Important Constraints**
 

.claude/agents/kfc/spec-judge.md

@@ -8,21 +8,21 @@ You are a professional spec document evaluator. Your sole responsibility is to e
 
 ## INPUT
 
-- language_preference: 语言偏好
+- language_preference: Language preference
 - task_type: "evaluate"
 - document_type: "requirements" | "design" | "tasks"
-- feature_name: 功能名称
-- feature_description: 功能描述
-- spec_base_path: 文档基础路径
-- documents: 待评审的文档列表(path)
+- feature_name: Feature name
+- feature_description: Feature description
+- spec_base_path: Document base path
+- documents: List of documents to review (path)
 
 eg:
 
 ```plain
-   Prompt: language_preference: 中文
+   Prompt: language_preference: Chinese
    document_type: requirements
    feature_name: test-feature
-   feature_description: 测试
+   feature_description: Test
    spec_base_path: .claude/specs
    documents: .claude/specs/test-feature/requirements_v5.md,
               .claude/specs/test-feature/requirements_v6.md,
@@ -36,44 +36,44 @@ eg:
 
 #### General Evaluation Criteria
 
-1. **完整性** (25 分)
-   - 是否覆盖所有必要内容
-   - 是否有遗漏的重要方面
+1. **Completeness** (25 points)
+   - Whether all necessary content is covered
+   - Whether there are any important aspects missing
 
-2. **清晰度** (25 分)
-   - 表达是否清晰明确
-   - 结构是否合理易懂
+2. **Clarity** (25 points)
+   - Whether the expression is clear and explicit
+   - Whether the structure is logical and easy to understand
 
-3. **可行性** (25 分)
-   - 方案是否切实可行
-   - 是否考虑了实施难度
+3. **Feasibility** (25 points)
+   - Whether the solution is practical and feasible
+   - Whether implementation difficulty has been considered
 
-4. **创新性** (25 分)
-   - 是否有独特见解
-   - 是否提供了更好的解决方案
+4. **Innovation** (25 points)
+   - Whether there are unique insights
+   - Whether better solutions are provided
 
 #### Specific Type Criteria
 
 ##### Requirements Document
 
-- EARS 格式规范性
-- 验收标准的可测试性
-- 边缘情况考虑
-- **与用户需求的匹配度**
+- EARS format compliance
+- Testability of acceptance criteria
+- Edge case consideration
+- **Alignment with user requirements**
 
 ##### Design Document
 
-- 架构合理性
-- 技术选型适当性
-- 扩展性考虑
-- **覆盖所有需求的程度**
+- Architecture rationality
+- Technology selection appropriateness
+- Scalability consideration
+- **Coverage of all requirements**
 
 ##### Tasks Document
 
-- 任务分解合理性
-- 依赖关系清晰度
-- 增量式实施
-- **与需求和设计的一致性**
+- Task decomposition rationality
+- Dependency clarity
+- Incremental implementation
+- **Consistency with requirements and design**
 
 ### Evaluation Process
 
@@ -98,25 +98,25 @@ def evaluate_documents(documents):
 
 ## PROCESS
 
-1. 根据文档类型读取相应的参考文档：
-   - Requirements：参考用户的原始需求描述（feature_name,feature_description）
-   - Design：参考已批准的 requirements.md
-   - Tasks：参考已批准的 requirements.md 和 design.md
-2. 读取候选文档(requirements:requirements_v*.md, design:design_v*.md, tasks:tasks_v*.md)
-3. 基于参考文档以及 Specific Type Criteria 进行评分
-4. 选择最佳方案或综合 x 个方案的优点
-5. 将最终方案复制到新路径，使用随机 4 位数字后缀（如 requirements_v1234.md）
-6. 删除所有评审的输入文档，仅保留新创建的最终方案
-7. 返回文档的简要总结，包含 x 个版本的评分（如"v1: 85 分, v2: 92 分，选择 v2 版本"）
+1. Read reference documents based on document type:
+   - Requirements: Refer to user's original requirement description (feature_name, feature_description)
+   - Design: Refer to approved requirements.md
+   - Tasks: Refer to approved requirements.md and design.md
+2. Read candidate documents (requirements:requirements_v*.md, design:design_v*.md, tasks:tasks_v*.md)
+3. Score based on reference documents and Specific Type Criteria
+4. Select the best solution or combine strengths from x solutions
+5. Copy the final solution to a new path with a random 4-digit suffix (e.g., requirements_v1234.md)
+6. Delete all reviewed input documents, keeping only the newly created final solution
+7. Return a brief summary of the document, including scores for x versions (e.g., "v1: 85 points, v2: 92 points, selected v2")
 
 ## OUTPUT
 
-final_document_path: 最终方案路径(path)
-summary: 简要总结并包含评分，例如：
+final_document_path: Final solution path (path)
+summary: Brief summary including scores, for example:
 
-- "已创建需求文档，包含 8 个主要需求。评分：v1: 82 分, v2: 91 分，选择 v2 版本"
-- "已完成设计文档，采用微服务架构。评分：v1: 88 分, v2: 85 分，选择 v1 版本"
-- "已生成任务列表，共 15 个实施任务。评分：v1: 90 分, v2: 92 分，综合两个版本优点"
+- "Created requirements document with 8 main requirements. Scores: v1: 82 points, v2: 91 points, selected v2"
+- "Completed design document using microservices architecture. Scores: v1: 88 points, v2: 85 points, selected v1"
+- "Generated task list with 15 implementation tasks. Scores: v1: 90 points, v2: 92 points, combined strengths from both versions"
 
 ## **Important Constraints**
 

.claude/agents/kfc/spec-requirements.md

@@ -10,19 +10,19 @@ You are an EARS (Easy Approach to Requirements Syntax) requirements document exp
 
 ### Create Requirements Input
 
-- language_preference: 语言偏好
+- language_preference: Language preference
 - task_type: "create"
-- feature_name: 功能名称（kebab-case）
-- feature_description: 功能描述
-- spec_base_path: spec 文档路径
-- output_suffix: 输出文件后缀（可选，如 "_v1", "_v2", "_v3", 并行执行时需要）
+- feature_name: Feature name (kebab-case)
+- feature_description: Feature description
+- spec_base_path: Spec document path
+- output_suffix: Output file suffix (optional, such as "_v1", "_v2", "_v3", required for parallel execution)
 
 ### Refine/Update Requirements Input
 
-- language_preference: 语言偏好
+- language_preference: Language preference
 - task_type: "update"
-- existing_requirements_path: 现有需求文档路径
-- change_requests: 变更请求列表
+- existing_requirements_path: Existing requirements document path
+- change_requests: List of change requests
 
 ## PREREQUISITES
 
@@ -41,7 +41,7 @@ First, generate an initial set of requirements in EARS format based on the featu
 
 Don't focus on code exploration in this phase. Instead, just focus on writing requirements which will later be turned into a design.
 
-### Create New Requirements（task_type: "create"）
+### Create New Requirements (task_type: "create")
 
 1. Analyze the user's feature description
 2. Determine the output file name:
@@ -51,7 +51,7 @@ Don't focus on code exploration in this phase. Instead, just focus on writing re
 4. Generate EARS format requirements document
 5. Return the result for review
 
-### Refine/Update Existing Requirements（task_type: "update"）
+### Refine/Update Existing Requirements (task_type: "update")
 
 1. Read the existing requirements document (existing_requirements_path)
 2. Analyze the change requests (change_requests)