jsharness 1.12.4 → 1.13.0

package/.harness/agents/project-manager/contract.yaml

@@ -1,49 +1,38 @@
-name: project-manager
-description: 项目经理路由Agent，负责需求接收与分类路由、任务分配、进度追踪和跨角色协调
+agent: project-manager
 version: "1.0.0"
+description: 项目经理路由Agent，负责需求接收与分类路由、任务分配、进度追踪和跨角色协调
 
-tools:
-  - search_content
-  - read_file
-  - write_to_file
-  - list_files
-  - search_file
-  - ask_followup_question
-
-model: lite
-agentMode: supervised
-enabled: true
-enabledAutoRun: false
-maxTurns: 5
-
-scope:
-  - .harness/
-  - jsspec/
-
-triggers:
-  - new_requirement
-  - status_check
-  - escalation
-  - change_request
-
-permissions:
-  - read
-  - write
+inputs:
+  - name: "原始需求"
+    source: "origin_requirements"
+    format: "markdown"
+    required: true
+  - name: "TaskBoard"
+    source: "task_board"
+    format: "markdown"
+    required: true
+
+outputs:
+  - name: "路由决策"
+    format: "markdown"
+    path: ".harness/doc/project/routing-decision.md"
+    required: true
+  - name: "TaskBoard 更新"
+    format: "markdown"
+    required: true
+
+stage_mapping:
+  - stage: "delivery"
+    role: "归档协调"
 
-safetyLevel: low
-dependencies: []
-outputFormat: .harness/doc/project/routing-decision.md
+constraints:
+  - "只做路由和协调，绝对不参与技术判断"
+  - "不得修改技术文档内容"
+  - "不得跳过必要流程阶段"
+  - "不得越过闸门总控强行推进"
 
-responsibilities:
-  - 接收需求，判断其类型（新功能/Bug/热修复/文档等）
-  - 选择合适的流程变体并分配给对应角色
-  - 维护 TaskBoard 看板的准确性
-  - 追踪各阶段进度，识别阻塞点
-  - 协调跨角色的沟通和变更请求
+rules:
+  - "rules/global/process-discipline.md"
 
-constraints:
-  - 不得指定技术实现方案
-  - 不得跳过必要的流程阶段
-  - 不得评价代码质量或设计优劣
-  - 不得修改技术文档的内容
-  - 不得在闸门判定为BLOCK时强行推进
+model_tier: lite
+max_turns: 5

package/.harness/agents/requirements-analyst/contract.yaml

@@ -1,48 +1,61 @@
-name: requirements-analyst
-description: 需求分析Agent，将原始需求转化为结构化需求文档、验收标准和用户故事，使用 prd-generator 技能生成标准化 PRD
+agent: requirements-analyst
 version: "1.0.0"
+description: 需求分析Agent，将原始需求转化为结构化需求文档、验收标准和用户故事
+
+inputs:
+  - name: "原始需求文件"
+    source: "origin_requirements"
+    path: ".harness/doc/originRequirements/{filename}"
+    format: "markdown"
+    required: true
+  - name: "ttspec change 目录"
+    source: "ttspec_change"
+    path: ".harness/doc/ttspec/change/{name}/"
+    format: "directory"
+    required: true
+  - name: "TaskBoard"
+    source: "task_board"
+    format: "markdown"
+    required: true
+  - name: "dev-map"
+    source: "dev_map"
+    format: "markdown"
+    required: true
+
+outputs:
+  - name: "explore 笔记"
+    format: "markdown"
+    path: ".harness/doc/ttspec/change/{name}/explore-notes.md"
+    required: true
+  - name: "结构化提案"
+    format: "directory"
+    path: ".harness/doc/ttspec/change/{name}/"
+    required: true
+  - name: "需求文档（PRD）"
+    format: "markdown"
+    path: ".harness/doc/prd/requirements-{task-id}.md"
+    required: true
+  - name: "TaskBoard 更新"
+    format: "markdown"
+    required: true
+
+stage_mapping:
+  - stage: "requirements-analysis"
+    role: "主力执行"
 
-tools:
-  - search_content
-  - read_file
-  - write_to_file
-  - list_files
-  - search_file
-  - ask_followup_question
-
-model: standard
-agentMode: interactive
-enabled: true
-enabledAutoRun: false
-maxTurns: 10
-
-scope:
-  - jsspec/
-  - .harness/
-
-triggers:
-  - requirement_received
-  - clarification_needed
-
-permissions:
-  - read
-  - write
+constraints:
+  - "不做技术方案设计"
+  - "不评估技术可行性细节"
+  - "不写代码"
+  - "禁止跳过任何步骤（必须 explore → propose → prd 顺序执行）"
 
-safetyLevel: low
-dependencies:
-  - project-manager
-outputFormat: .harness/doc/prd/requirements-{task-id}.md
+skills:
+  - "jsspec-explore"
+  - "jsspec-propose"
+  - "prd-generator"
 
-responsibilities:
-  - 将模糊的原始需求转化为结构化规格说明
-  - 确保每个需求都有明确可测试的验收标准
-  - 先 explore（深度探索），再 propose（结构化提案），最后 prd-generation（标准化 PRD）
-  - 产出 explore-notes.md、proposal/design/specs/tasks 和标准化 PRD
-  - 用户故事拆分
+rules:
+  - "rules/global/process-discipline.md"
 
-constraints:
-  - 不做技术方案设计
-  - 不评估技术可行性细节
-  - 不写代码
-  - 每个需求至少有一个验收标准
-  - 明确写出"不做什么"
+model_tier: standard
+max_turns: 10

package/.harness/agents/solution-designer/contract.yaml

@@ -1,47 +1,73 @@
-name: solution-designer
-description: 方案设计Agent，基于需求文档输出技术方案、接口定义（OpenAPI 3.0）、数据模型和架构设计
+agent: solution-designer
 version: "1.0.0"
+description: 方案设计Agent，基于需求文档输出技术方案、接口定义、数据模型、架构设计和 UI 设计规范
 
-tools:
-  - search_content
-  - read_file
-  - write_to_file
-  - list_files
-  - search_file
-  - ask_followup_question
+inputs:
+  - name: "需求文档"
+    source: "requirements_analysis.outputs.需求文档"
+    format: "markdown"
+    required: true
+  - name: "验收标准"
+    source: "requirements_analysis.outputs.验收标准列表"
+    required: true
+  - name: "dev-map 架构参考"
+    source: "dev_map"
+    required: true
+  - name: "ADR 历史决策"
+    source: "dev-map/decisions.md"
+    required: false
 
-model: standard
-agentMode: interactive
-enabled: true
-enabledAutoRun: false
-maxTurns: 15
+outputs:
+  - name: "技术设计文档"
+    format: "markdown"
+    path: ".harness/doc/design/{需求名称}/design.md"
+    required: true
+  - name: "API 定义"
+    format: "yaml (OpenAPI 3.0)"
+    path: ".harness/doc/design/{需求名称}/api/"
+    required: true
+  - name: "数据模型"
+    format: "markdown"
+    path: ".harness/doc/design/{需求名称}/data-model.md"
+    required: true
+  - name: "UI 设计规范"
+    format: "markdown"
+    path: ".harness/doc/design/{需求名称}/ui-style-guide.md"
+    required: false
+    description: "前端项目必须"
+  - name: "设计令牌"
+    format: "markdown"
+    path: ".harness/doc/design/{需求名称}/design-tokens.md"
+    required: false
+    description: "前端项目必须"
+  - name: "组件封装规范"
+    format: "markdown"
+    path: ".harness/doc/design/{需求名称}/component-spec.md"
+    required: false
+    description: "前端项目必须"
+  - name: "技术决策记录"
+    format: "markdown (ADR)"
+    required: false
 
-scope:
-  - jsspec/
-  - .harness/
-  - src/
+stage_mapping:
+  - stage: "solution-design"
+    role: "主力执行"
 
-triggers:
-  - design_requested
-  - architecture_review
-
-permissions:
-  - read
-  - write
+constraints:
+  - "不写可执行代码"
+  - "不修改需求文档"
+  - "不做最终可行性判决"
+  - "设计文档禁止包含代码/测试/监控/日志/部署/数据库优化"
+  - "必须先判断需求复杂度再选择设计深度"
 
-safetyLevel: low
-dependencies:
-  - requirements-analyst
-outputFormat: .harness/doc/design/design-{task-id}.md
+skills:
+  - "architecture-designer"
+  - "ui-designer"
 
-responsibilities:
-  - 基于需求文档输出完整技术方案
-  - 先判断需求复杂度再选择设计深度
-  - 产出技术设计文档、API定义（OpenAPI 3.0）、数据模型设计
-  - 记录技术决策（ADR）
+rules:
+  - "rules/global/coding-standard.md"
+  - "rules/global/design-document-boundary.md"
+  - "rules/global/security-baseline.md"
 
-constraints:
-  - 不写可执行代码
-  - 不修改需求文档
-  - 不做最终可行性判决（由闸门负责）
-  - 设计文档禁止包含代码/测试/监控/日志/部署/数据库优化
+model_tier: standard
+max_turns: 15

package/.harness/agents/solution-designer/prompt.md

@@ -1,6 +1,6 @@
 ---
 name: solution-designer
-description: 方案设计Agent，基于需求文档输出技术方案、接口定义（OpenAPI 3.0）、数据模型和架构设计
+description: 方案设计Agent，基于需求文档输出技术方案、接口定义（OpenAPI 3.0）、数据模型、架构设计和 UI 设计规范
 tools:
   - search_content
   - read_file
@@ -26,7 +26,16 @@ permissions:
 safetyLevel: low
 dependencies:
   - requirements-analyst
-outputFormat: .harness/doc/design/design-{task-id}.md
+outputFormat: .harness/doc/design/{需求名称}/design.md
+inputs:
+  - name: "需求文档"
+    required: true
+  - name: "验收标准"
+    required: true
+  - name: "dev-map 架构参考"
+    required: true
+  - name: "ADR 历史决策"
+    required: false
 ---
 
 # 方案设计 Agent
@@ -36,6 +45,7 @@ outputFormat: .harness/doc/design/design-{task-id}.md
 - 你是连接"做什么"和"怎么实现"的关键环节
 - 你的方案将直接指导开发者的编码工作
 - 你在架构设计阶段引用 architecture-designer skill 获取完整设计模板
+- 你在方案设计阶段引用 ui-designer skill 获取 UI 设计规范和风格模板
 
 ## 你的输入
 - 需求文档（来自需求分析师）
@@ -44,16 +54,17 @@ outputFormat: .harness/doc/design/design-{task-id}.md
 - ADR 决策记录
 
 ## 你的输出（必须全部交付）
-1. 技术设计文档（design-{task-id}.md）
+1. 技术设计文档（`.harness/doc/design/{需求名称}/design.md`）
    - **必须先判断需求复杂度**（简单 vs 复杂，参见 design-document-boundary 规则 §3）
    - 简单需求（< 3000 行）：简化模板，单体架构，Context+Container 层
    - 复杂需求（≥ 3000 行）：完整模板，C4模型+限界上下文+领域模型
    - 架构设计、接口定义、数据模型
    - 关键实现逻辑（文字描述，非代码）
    - 影响面分析和风险
-2. API 定义（api-definition.yaml）— 每服务独立 OpenAPI 3.0 YAML
-3. 数据模型设计（data-model.md）— ER图 + 领域模型描述
+2. API 定义（`.harness/doc/design/{需求名称}/api/`）— 每服务独立 OpenAPI 3.0 YAML
+3. 数据模型设计（`.harness/doc/design/{需求名称}/data-model.md`）— ER图 + 领域模型描述
 4. 如有新的技术决策 → ADR 记录
+5. UI 设计规范和风格模板（`.harness/doc/design/{需求名称}/ui-style-guide.md` + `.harness/doc/design/{需求名称}/design-tokens.md` + `.harness/doc/design/{需求名称}/component-spec.md`）— 引用 ui-designer skill
 
 ## 你的约束
 - ❌ 不写可执行代码
@@ -64,6 +75,7 @@ outputFormat: .harness/doc/design/design-{task-id}.md
 - ✅ 接口定义必须足够详细，可供开发者和测试者直接使用
 - ✅ 必须先判断需求复杂度再选择设计深度
 - ✅ 引用 architecture-designer skill 获取 C4模型、领域模型、类图等完整设计规范
+- ✅ 引用 ui-designer skill 获取设计令牌、组件风格模板、页面布局模板、组件封装规范等 UI 设计规范
 
 ## 设计原则
 - 优先复用 dev-map 中的已有模式
@@ -80,6 +92,7 @@ outputFormat: .harness/doc/design/design-{task-id}.md
 
 ## 关键参考文件
 - skills/architecture-designer/SKILL.md — 架构设计完整模板
+- skills/ui-designer/SKILL.md — UI 设计规范和风格模板
 - rules/global/design-document-boundary.md — 设计文档边界约束 + 复杂度分流
 - rules/project/java-backend.md — 后端编码规范
 - rules/project/frontend-vue3.md — 前端编码规范

package/.harness/agents/tester/contract.yaml

@@ -1,59 +1,106 @@
-name: tester
-description: 测试验证Agent，制定测试策略、设计测试用例、执行测试、记录缺陷并输出完整测试报告
+agent: tester
 version: "1.0.0"
+description: 测试验证Agent，制定测试策略、设计测试用例、执行测试、记录缺陷并输出完整测试报告
 
-tools:
-  - search_content
-  - read_file
-  - write_to_file
-  - execute_command
-  - list_files
-  - search_file
-  - ask_followup_question
-
-model: strong
-agentMode: supervised
-enabled: true
-enabledAutoRun: false
-maxTurns: 15
-
-scope:
-  - src/
-  - test/
-  - .harness/
+inputs:
+  - name: "需求文档"
+    source: "requirements_analysis"
+    format: "markdown"
+    required: true
+  - name: "技术设计文档"
+    source: "solution_design"
+    format: "markdown"
+    required: true
+  - name: "实现代码"
+    source: "development"
+    format: "source code"
+    required: true
+  - name: "验收标准"
+    source: "requirements_analysis"
+    required: true
+  - name: "审查报告"
+    source: "code_review"
+    format: "markdown"
+    required: true
+  - name: "测试用例文档"
+    source: "development"
+    path: ".harness/doc/test-cases/{需求名称}/"
+    format: "markdown"
+    required: true
+  - name: "UI 设计规范"
+    source: "solution_design"
+    path: ".harness/doc/design/{需求名称}/ui-style-guide.md"
+    format: "markdown"
+    required: false
+    description: "前端项目测试时必须，用于验证 UI 实现是否符合设计规范"
+  - name: "组件封装规范"
+    source: "solution_design"
+    path: ".harness/doc/design/{需求名称}/component-spec.md"
+    format: "markdown"
+    required: false
+    description: "前端项目测试时必须，用于验证组件接口和封装合规"
+  - name: "设计令牌"
+    source: "solution_design"
+    path: ".harness/doc/design/{需求名称}/design-tokens.md"
+    format: "markdown"
+    required: false
+    description: "前端项目测试时可选，用于验证令牌覆盖率"
+  - name: "Skill 测试动作集"
+    source: "skills/test-*.md"
+    required: true
 
-triggers:
-  - test_requested
-  - pre_release
-  - regression_needed
+outputs:
+  - name: "测试计划"
+    format: "markdown"
+    required: true
+  - name: "测试报告"
+    format: "markdown"
+    path: ".harness/doc/test-report/test-report-{task-id}.md"
+    required: true
+  - name: "缺陷列表"
+    format: "markdown"
+    required: true
+  - name: "回归风险评估"
+    format: "markdown"
+    required: true
+  - name: "Gate 验证结果"
+    format: "json"
+    required: true
 
-permissions:
-  - read
-  - write
-  - execute
+stage_mapping:
+  - stage: "testing"
+    role: "主力执行"
 
-safetyLevel: medium
-dependencies:
-  - developer
-  - code-reviewer
-outputFormat: .harness/doc/test-report/test-report-{task-id}.md
+constraints:
+  - "不改被测代码"
+  - "不降低验收标准"
+  - "不省略必测项目"
+  - "安全问题立即阻断升级"
 
-responsibilities:
-  - 制定测试策略和计划
-  - 设计和执行各类测试
-  - 记录和跟踪缺陷
-  - 输出完整的测试报告
-  - 评估回归风险
+test_types:
+  - name: "unit_tests"
+    skill: "test-unit"
+    required: true
+  - name: "test_case_validation"
+    skill: "test-case-designer"
+    required: true
+  - name: "api_integration"
+    skill: "test-api"
+    required: true
+  - name: "e2e_critical_path"
+    skill: "test-e2e"
+    required: true
+  - name: "security_scan"
+    skill: "lint-check"
+    required: true
+  - name: "performance_test"
+    required: false
+  - name: "regression_test"
+    required: true
 
-pass_conditions:
-  - P0 = 0 且 P1 = 0
-  - 核心 E2E 路径全部通过
-  - API 契约无破坏性变更
-  - 测试覆盖率不低于基线
+rules:
+  - "rules/global/security-baseline.md"
+  - "rules/global/process-discipline.md"
 
-constraints:
-  - 不改被测代码
-  - 不降低验收标准
-  - 不省略必测项目
-  - 基于验收标准设计用例
-  - 安全问题立即阻断升级
+model_tier: strong
+max_turns: 15

package/.harness/agents/tester/prompt.md

@@ -31,6 +31,28 @@ dependencies:
   - developer
   - code-reviewer
 outputFormat: .harness/doc/test-report/test-report-{task-id}.md
+inputs:
+  - name: "需求文档"
+    required: true
+  - name: "技术设计文档"
+    required: true
+  - name: "实现代码"
+    required: true
+  - name: "验收标准"
+    required: true
+  - name: "审查报告"
+    required: true
+  - name: "测试用例文档"
+    required: true
+  - name: "UI 设计规范"
+    path: ".harness/doc/design/{需求名称}/ui-style-guide.md"
+    required: false
+  - name: "组件封装规范"
+    path: ".harness/doc/design/{需求名称}/component-spec.md"
+    required: false
+  - name: "设计令牌"
+    path: ".harness/doc/design/{需求名称}/design-tokens.md"
+    required: false
 ---
 
 # 测试验证 Agent
@@ -50,7 +72,9 @@ outputFormat: .harness/doc/test-report/test-report-{task-id}.md
 ## 测试覆盖矩阵
 | 测试类型 | 执行时机 | 负责人 | 必须? | 引用Skill |
 |----------|----------|--------|-------|-----------|
+| 测试用例验证 | 测试开始前 | Tester | ✅ 必须 | test-case-designer |
 | 单元测试 | 开发时 | Developer | ✅ 必须 | test-unit |
+| 前端组件测试 | 开发时 | Developer | ✅ 必须 | test-unit |
 | 静态检查 | 每次 commit | Dev/CI | ✅ 必须 | lint-check |
 | API 集成测试 | PR 前 | Tester | ✅ 必须 | test-api |
 | E2E 关键路径 | 预发布前 | Tester | ✅ 必须 | test-e2e |
@@ -73,6 +97,15 @@ outputFormat: .harness/doc/test-report/test-report-{task-id}.md
 - 核心 E2E 路径全部通过
 - API 契约无破坏性变更
 - 测试覆盖率不低于基线
+- **测试用例文档存在且与验收标准对齐**（.harness/doc/test-cases/ 下有 feature-points.md）
+- **前端组件测试覆盖 ≥80%**（每个 .vue 有对应 .test.ts/.spec.ts）
+
+## 测试执行前置检查
+在正式执行测试前，必须验证以下前置条件：
+1. **测试用例文档检查** — 确认 `.harness/doc/test-cases/{需求名称}/feature-points.md` 存在
+2. **前端测试文件存在性** — 扫描 src/ 下 .vue 文件，确认每个组件有对应测试文件
+3. **后端测试类存在性** — 扫描 Service/ServiceImpl 类，确认有对应 Test 类
+4. 任何前置条件不满足 → 记录为 P1 缺陷并要求开发补充
 
 ## 你的约束
 - ❌ 不改被测代码

package/.harness/commands/js/build-gates-frontend.md

@@ -5,7 +5,7 @@ description: 前端构建门槛 — TypeScript 类型检查、依赖完整性、
 
 # 前端构建门槛 (Frontend Build Gates)
 
-> **源文件**: `.harness/gate/checks/build-gates-frontend.js`
+> **源文件**: `.harness/gate/checks/build-gates-frontend.cjs`
 > **类别**: B 类 — 构建门槛 (前端)
 
 适用于 `package.json` 存在的项目（Vue3/Vite 等）。

package/.harness/commands/js/build-gates-java.md

@@ -5,7 +5,7 @@ description: Java 后端构建门槛 — Maven 编译、单元测试、Checkstyl
 
 # Java 后端构建门槛 (Java Build Gates)
 
-> **源文件**: `.harness/gate/checks/build-gates-java.js`
+> **源文件**: `.harness/gate/checks/build-gates-java.cjs`
 > **类别**: B 类 — 构建门槛 (Java)
 
 适用于 `pom.xml` 存在的 Spring Boot / Maven 项目（JDK21 + Spring Boot）。

package/.harness/commands/js/build-gates.md

@@ -5,12 +5,12 @@ description: 构建门槛检查 — 自动检测项目类型并分发到对应
 
 # 构建门槛检查 (Build Gates)
 
-> **源文件**: `.harness/gate/checks/build-gates.js`
+> **源文件**: `.harness/gate/checks/build-gates.cjs`
 > **类别**: B 类 — 构建门槛
 
 自动检测项目类型并分发到对应的门禁检查模块：
-- 检测到 `pom.xml` → 调用 build-gates-java.js (Maven/Java)
-- 检测到 `package.json` → 调用 build-gates-frontend.js (Node/前端)
+- 检测到 `pom.xml` → 调用 build-gates-java.cjs (Maven/Java)
+- 检测到 `package.json` → 调用 build-gates-frontend.cjs (Node/前端)
 - 都没有 → 返回 warning
 
 ## 检查项

package/.harness/commands/js/engineering-consistency.md

@@ -5,7 +5,7 @@ description: 工程一致性检查 — CHANGELOG 更新、dev-map 一致性、
 
 # 工程一致性检查 (Engineering Consistency)
 
-> **源文件**: `.harness/gate/checks/engineering-consistency.js`
+> **源文件**: `.harness/gate/checks/engineering-consistency.cjs`
 > **类别**: E 类 — 工程一致性
 
 ## 检查项

package/.harness/commands/js/security-quality.md

@@ -5,7 +5,7 @@ description: 安全与质量检查 — CVE 依赖审计、Code Review Approval
 
 # 安全与质量检查 (Security & Quality)
 
-> **源文件**: `.harness/gate/checks/security-quality.js`
+> **源文件**: `.harness/gate/checks/security-quality.cjs`
 > **类别**: D 类 — 安全与质量
 
 ## 检查项

package/.harness/commands/js/static-compliance.md

@@ -5,7 +5,7 @@ description: 静态合规检查 — ESLint、Prettier、console.log 残留、硬
 
 # 静态合规检查 (Static Compliance)
 
-> **源文件**: `.harness/gate/checks/static-compliance.js`
+> **源文件**: `.harness/gate/checks/static-compliance.cjs`
 > **类别**: A 类 — 静态合规
 
 ## 检查项

package/.harness/commands/js/test-compliance.md

@@ -5,7 +5,7 @@ description: 测试合规检查 — 单元测试执行与覆盖率、E2E 测试
 
 # 测试合规检查 (Test Compliance)
 
-> **源文件**: `.harness/gate/checks/test-compliance.js`
+> **源文件**: `.harness/gate/checks/test-compliance.cjs`
 > **类别**: C 类 — 测试合规
 
 ## 检查项