@pzy560117/opentest 0.1.3 → 0.1.5

package/README.md

@@ -26,25 +26,73 @@ requirement / design
 
 ## Install
 
-Install into the current project:
+Install the package, then run the initializer from any project:
 
 ```bash
-npx @pzy560117/opentest install
+npm install -g @pzy560117/opentest
+opentest init
 ```
 
-Install globally for Codex:
+`opentest init` lets you choose the target tool, language, project/global scope, and project path. This is the recommended path for Claude Code, Codex, Cursor, OpenCode, Gemini CLI, Qwen Code, and Qoder users.
+
+You can still run fully scripted installs. For example, install Chinese OpenTest skills for Claude Code in the current project:
+
+```bash
+opentest install --scope project --platform claude --language zh
+```
+
+Install Chinese OpenTest skills for Qoder in a specific project:
 
 ```bash
-npx @pzy560117/opentest install --global
+npx @pzy560117/opentest install --scope project --platform qoder --language zh --project /path/to/project
 ```
 
-Overwrite an existing OpenTest install:
+Install Chinese OpenTest skills globally for Codex:
 
 ```bash
-npx @pzy560117/opentest install --force
+npx @pzy560117/opentest install --scope global --platform codex --language zh
 ```
 
-Restart Codex or open a new session after installation so the new skills are loaded.
+Legacy global install with overwrite:
+
+```bash
+npx @pzy560117/opentest install --global --force
+```
+
+Legacy project install with overwrite:
+
+```bash
+npx @pzy560117/opentest install --project /path/to/project --force
+```
+
+### Install Options
+
+| Option | Meaning | Default |
+| --- | --- | --- |
+| `--scope <project|global>` | Install into the selected project skills directory or the user's global skills directory. | `project` |
+| `--platform <id>` | Target AI programming tool. Supported IDs are listed below and are read by the CLI from `assets/manifest.json`. | `codex` |
+| `--language <en|zh>` | Skill language to install. `en` installs English skills; `zh` installs Chinese skills. | `en` |
+| `--project <path>` | Project root used for project-scope installs. This also selects project scope for legacy compatibility. | Current working directory |
+| `--global` | Legacy alias for `--scope global --platform codex`. | Disabled |
+| `--force` | Overwrite existing manifest-managed OpenTest skill directories. | Disabled |
+
+### Supported Platforms
+
+The CLI reads platform data directly from the package manifest at `assets/manifest.json`; the paths below are shown using project-relative and home-relative notation.
+
+| Platform ID | Tool | Project skills directory | Global skills directory |
+| --- | --- | --- | --- |
+| `codex` | Codex | `.codex/skills` | `~/.codex/skills` |
+| `claude` | Claude Code | `.claude/skills` | `~/.claude/skills` |
+| `cursor` | Cursor | `.cursor/skills` | `~/.cursor/skills` |
+| `opencode` | OpenCode | `.opencode/skills` | `~/.config/opencode/skills` |
+| `gemini` | Gemini CLI | `.gemini/skills` | `~/.gemini/skills` |
+| `qwen` | Qwen Code | `.qwen/skills` | `~/.qwen/skills` |
+| `qoder` | Qoder | `.qoder/skills` | `~/.qoder/skills` |
+
+When adding a platform, update at least `assets/manifest.json` and `scripts/smoke-test.js` in this package so the installer data and smoke coverage stay in sync. Update this README table in the same change.
+
+Restart the target AI programming tool or open a new session after installation so the new skills are loaded.
 
 ## Included Skills
 
@@ -59,6 +107,7 @@ Restart Codex or open a new session after installation so the new skills are loa
 
 ## Package Contents
 
-- `assets/skills/`: Codex skill files
+- `assets/skills/`: English skill files
+- `assets/skills-zh/`: Chinese skill files
 - `assets/manifest.json`: published asset manifest
 - `bin/opentest.js`: installer CLI

package/assets/manifest.json

@@ -1,31 +1,88 @@
 {
-  "version": "0.1.3",
-  "skills": [
-    "opentest/SKILL.md",
-    "opentest/scripts/opentest-state.sh",
-    "opentest/scripts/opentest-detect.sh",
-    "opentest/scripts/opentest-guard.sh",
-    "opentest/references/lifecycle.md",
-    "opentest/references/matrix-format.md",
-    "opentest/references/quality-gate.md",
-    "opentest/references/acceptance-evidence.md",
-    "opentest/references/command-routing.md",
-    "opentest/references/codex-harness-coverage-heuristics.md",
-    "opentest/references/opentest-driven-development.md",
-    "opentest/templates/plan-template.md",
-    "opentest/templates/matrix-template.md",
-    "opentest/templates/acceptance-template.md",
-    "opentest/templates/report-template.md",
-    "opentest/templates/archive-layout.md",
-    "opentest-plan/SKILL.md",
-    "opentest-author/SKILL.md",
-    "opentest-run/SKILL.md",
-    "opentest-accept/SKILL.md",
-    "opentest-verify/SKILL.md",
-    "opentest-heal/SKILL.md",
-    "opentest-archive/SKILL.md"
+  "version": "0.1.5",
+  "languages": [
+    {
+      "id": "en",
+      "name": "English",
+      "skillsDir": "skills"
+    },
+    {
+      "id": "zh",
+      "name": "中文",
+      "skillsDir": "skills-zh"
+    }
   ],
   "platforms": [
-    { "id": "codex", "skillsDir": ".codex/skills" }
-  ]
+    {
+      "id": "codex",
+      "name": "Codex",
+      "projectSkillsDir": ".codex/skills",
+      "globalSkillsDir": "~/.codex/skills"
+    },
+    {
+      "id": "claude",
+      "name": "Claude Code",
+      "projectSkillsDir": ".claude/skills",
+      "globalSkillsDir": "~/.claude/skills"
+    },
+    {
+      "id": "cursor",
+      "name": "Cursor",
+      "projectSkillsDir": ".cursor/skills",
+      "globalSkillsDir": "~/.cursor/skills"
+    },
+    {
+      "id": "opencode",
+      "name": "OpenCode",
+      "projectSkillsDir": ".opencode/skills",
+      "globalSkillsDir": ".config/opencode/skills"
+    },
+    {
+      "id": "gemini",
+      "name": "Gemini CLI",
+      "projectSkillsDir": ".gemini/skills",
+      "globalSkillsDir": "~/.gemini/skills"
+    },
+    {
+      "id": "qwen",
+      "name": "Qwen Code",
+      "projectSkillsDir": ".qwen/skills",
+      "globalSkillsDir": "~/.qwen/skills"
+    },
+    {
+      "id": "qoder",
+      "name": "Qoder",
+      "projectSkillsDir": ".qoder/skills",
+      "globalSkillsDir": "~/.qoder/skills"
+    }
+  ],
+  "managedFiles": {
+    "localized": [
+      "opentest/SKILL.md",
+      "opentest/references/acceptance-evidence.md",
+      "opentest/references/codex-harness-coverage-heuristics.md",
+      "opentest/references/command-routing.md",
+      "opentest/references/lifecycle.md",
+      "opentest/references/matrix-format.md",
+      "opentest/references/opentest-driven-development.md",
+      "opentest/references/quality-gate.md",
+      "opentest/templates/acceptance-template.md",
+      "opentest/templates/archive-layout.md",
+      "opentest/templates/matrix-template.md",
+      "opentest/templates/plan-template.md",
+      "opentest/templates/report-template.md",
+      "opentest-accept/SKILL.md",
+      "opentest-archive/SKILL.md",
+      "opentest-author/SKILL.md",
+      "opentest-heal/SKILL.md",
+      "opentest-plan/SKILL.md",
+      "opentest-run/SKILL.md",
+      "opentest-verify/SKILL.md"
+    ],
+    "shared": [
+      "opentest/scripts/opentest-state.sh",
+      "opentest/scripts/opentest-detect.sh",
+      "opentest/scripts/opentest-guard.sh"
+    ]
+  }
 }

package/assets/skills/opentest/SKILL.md

@@ -1,93 +1,93 @@
 ---
 name: opentest
-description: "OpenTest 路由入口。自动检测 .opentest.yaml、初始化测试生命周期状态，并分发到 plan/author/run/accept/verify/heal/archive 阶段。"
+description: "OpenTest router. Detects .opentest.yaml, initializes test lifecycle state, and dispatches to plan/author/run/accept/verify/heal/archive phases."
 ---
 
-# OpenTest 路由入口
+# OpenTest Router
 
-OpenTest 是面向 AI 编程变更的测试决策与质量证据生命周期。它不是单纯的 TDD 包装，也不是只在实现结束后跑命令；它应在实现前先把显性需求、隐性边界、失败路径、交互反馈和风险场景整理成测试矩阵，再用矩阵驱动代码、验收和质量门。
+OpenTest is a test decision and quality evidence lifecycle for AI coding changes. It is not just a TDD wrapper, and it is not just a command runner at the end of implementation. Before implementation, it turns explicit requirements, implicit boundaries, failure paths, interaction feedback, and risk scenarios into a test matrix, then uses that matrix to drive code, acceptance, and quality gates.
 
-## 产出语言契约
+## Output Language Contract
 
-- 面向用户输出和生成文档默认使用中文。
-- 命令、路径、frontmatter key、代码标识符和 API 名称保持原文。
+- User-facing output and generated documents default to English.
+- Commands, paths, frontmatter keys, code identifiers, and API names stay as written.
 
-## Step 0: 定位脚本
+## Step 0: Locate Scripts
 
-运行：
+Run:
 
 ```bash
-OPENTEST_SEARCH_ROOTS=("." "$HOME/.claude/skills" "$HOME/.codex/skills" "$HOME/.cursor/skills")
+OPENTEST_SEARCH_ROOTS=("." ".codex/skills" ".claude/skills" ".cursor/skills" ".opencode/skills" ".gemini/skills" ".qwen/skills" ".qoder/skills" "$HOME/.codex/skills" "$HOME/.claude/skills" "$HOME/.cursor/skills" "$HOME/.config/opencode/skills" "$HOME/.gemini/skills" "$HOME/.qwen/skills" "$HOME/.qoder/skills")
 OPENTEST_STATE="${OPENTEST_STATE:-$(find "${OPENTEST_SEARCH_ROOTS[@]}" -path '*/opentest/scripts/opentest-state.sh' -type f -print -quit 2>/dev/null)}"
 OPENTEST_GUARD="${OPENTEST_GUARD:-$(find "${OPENTEST_SEARCH_ROOTS[@]}" -path '*/opentest/scripts/opentest-guard.sh' -type f -print -quit 2>/dev/null)}"
 OPENTEST_DETECT="${OPENTEST_DETECT:-$(find "${OPENTEST_SEARCH_ROOTS[@]}" -path '*/opentest/scripts/opentest-detect.sh' -type f -print -quit 2>/dev/null)}"
 ```
 
-若任一脚本缺失，停止并提示安装或复制 OpenTest 分发包。
+If any script is missing, stop and ask the user to install or copy the OpenTest distribution.
 
-## Step 1: 状态检测
+## Step 1: Detect State
 
-如果存在 `docs/loop-handoff/latest.md`，先读取 handoff，确认上次 OpenTest 阶段、矩阵/验收/报告路径、阻塞项和下一步。handoff 只作为恢复线索，不替代 `.opentest.yaml`。
+If `docs/loop-handoff/latest.md` exists, read it first to recover the previous OpenTest phase, matrix/acceptance/report paths, blockers, and next step. The handoff is only a recovery hint; it does not replace `.opentest.yaml`.
 
-如果 `.opentest.yaml` 不存在，运行：
+If `.opentest.yaml` does not exist, run:
 
 ```bash
 bash "$OPENTEST_STATE" init
 ```
 
-然后运行：
+Then run:
 
 ```bash
 bash "$OPENTEST_STATE" check
 bash "$OPENTEST_DETECT" summary
 ```
 
-## Step 2: 阶段分发
+## Step 2: Dispatch Phase
 
-读取 `phase`：
+Read `phase`:
 
 ```bash
 bash "$OPENTEST_STATE" get phase
 ```
 
-分发规则：
+Dispatch rules:
 
-- `archived: true`：报告 OpenTest 已完成。
-- `phase: plan`：调用 `opentest-plan`。
-- `phase: author`：调用 `opentest-author`。
-- `phase: run`：调用 `opentest-run`。
-- `phase: accept`：调用 `opentest-accept`。
-- `phase: verify`：调用 `opentest-verify`。
-- `phase: heal`：调用 `opentest-heal`。
-- `phase: archive`：调用 `opentest-archive`。
+- `archived: true`: report that OpenTest is complete.
+- `phase: plan`: invoke `opentest-plan`.
+- `phase: author`: invoke `opentest-author`.
+- `phase: run`: invoke `opentest-run`.
+- `phase: accept`: invoke `opentest-accept`.
+- `phase: verify`: invoke `opentest-verify`.
+- `phase: heal`: invoke `opentest-heal`.
+- `phase: archive`: invoke `opentest-archive`.
 
-若状态与可验证文件冲突，以文件状态为准，并用 `opentest-state.sh set` 修正；如存在 handoff，也同步更新 handoff 的“当前阶段/下一步/失败阻塞”。
+If state conflicts with verifiable files, trust the files and repair state with `opentest-state.sh set`. If a handoff exists, also update its current phase, next step, failures, and blockers.
 
-## OpenTest-Driven Development 用法
+## OpenTest-Driven Development Usage
 
-当用户想“以测试驱动开发”、需求包含前端交互、登录、表单、权限、API、数据写入、跨页面流程或高风险行为时，OpenTest 必须前置到 build 之前：
+When the user wants test-driven development, or when the requirement includes frontend interactions, login, forms, permissions, APIs, data writes, cross-page flows, or high-risk behavior, OpenTest must run before build work:
 
 ```text
-需求 / OpenSuper design
-  -> opentest plan    # 隐性场景挖掘 + acceptance-to-test matrix
-  -> opentest author  # 测试资产 / 自然语言验收用例
-  -> build            # 按矩阵实现
-  -> opentest run     # unit / integration / smoke / e2e 命令
-  -> opentest accept  # 真实页面、API 或链路验收
-  -> opentest verify  # 质量门报告
+Requirement / OpenSuper design
+  -> opentest plan    # implicit scenario mining + acceptance-to-test matrix
+  -> opentest author  # test assets / natural language acceptance cases
+  -> build            # implement against the matrix
+  -> opentest run     # unit / integration / smoke / e2e commands
+  -> opentest accept  # real page, API, or workflow acceptance
+  -> opentest verify  # quality gate report
 ```
 
-`plan` 阶段不能只复述需求。它必须主动检查：
+The `plan` phase must not merely restate requirements. It must actively inspect:
 
-- 主路径、失败路径、边界输入、空数据、权限、网络、重复提交、并发或过期状态。
-- 前端反馈位置：字段下方、表单顶部、toast、modal、inline status、页面错误态。
-- 证据分层：unit、component、integration、contract、E2E、smoke、visual/browser acceptance、security/review。
-- 哪些证据是必需，哪些是不适用，哪些是 gap 或 risk-accepted 候选。
+- Happy paths, failure paths, boundary inputs, empty data, permissions, network failures, duplicate submissions, concurrency, and stale state.
+- Frontend feedback location: field-level message, form-level alert, toast, modal, inline status, or page error state.
+- Evidence layers: unit, component, integration, contract, E2E, smoke, visual/browser acceptance, and security/review.
+- Which evidence is required, which is not applicable, and which is a gap or risk-accepted candidate.
 
-实现完成后，`OpenSuper verify` 可以引用 OpenTest 的 verification report，但不能替代 OpenTest 的矩阵、运行记录和验收证据。
+After implementation, `OpenSuper verify` may reference the OpenTest verification report, but it does not replace the OpenTest matrix, run records, or acceptance evidence.
 
-## Loop Handoff 衔接
+## Loop Handoff Integration
 
-OpenTest 每完成 `plan`、`author`、`run`、`accept`、`verify` 任一阶段后，应更新 `docs/loop-handoff/latest.md`，至少记录 `.opentest.yaml` 路径、当前阶段、测试资产路径、已运行验证、未运行验证、失败/阻塞和下一步。
+After OpenTest completes any `plan`, `author`, `run`, `accept`, or `verify` phase, update `docs/loop-handoff/latest.md` when the project uses Loop Handoff. At minimum, record the `.opentest.yaml` path, current phase, test asset paths, verification already run, verification not run, failures/blockers, and next step.
 
-`opentest-verify` 生成的 verification report 路径必须写入 handoff，方便 OpenSuper verify 或新会话恢复时直接引用。
+The verification report path produced by `opentest-verify` must be written to the handoff so OpenSuper verify or a resumed session can reference it directly.

package/assets/skills/opentest/references/codex-harness-coverage-heuristics.md

@@ -1,14 +1,14 @@
-# Codex Harness 覆盖启发参考
+# Codex Harness Coverage Heuristics
 
-## 用途
+## Purpose
 
-本文件随 OpenTest 分发，用于给 `/opentest-plan` 和 `/opentest-accept` 提供轻量覆盖启发。它不是强制 checklist，也不是 Codex Harness 全量内容副本。
+This file ships with OpenTest to provide lightweight coverage heuristics for `/opentest-plan` and `/opentest-accept`. It is not a mandatory checklist and is not a full copy of Codex Harness content.
 
-OpenTest 应根据变更类型、风险和项目事实选择适用覆盖面。适用但缺少证据的点应记录为 `gap`；不适用的点应在覆盖摘要中说明，不需要展开用例。
+OpenTest should select applicable coverage from the change type, risk, and project facts. Applicable coverage without evidence should be recorded as `gap`. Non-applicable coverage should be briefly explained in the coverage summary and does not need expanded cases.
 
-## 来源
+## Sources
 
-本参考从本地 Codex Harness 知识库中抽取短规则，主要对应：
+This reference extracts short rules from the local Codex Harness knowledge base, primarily corresponding to:
 
 - `tdd-workflow`
 - `e2e-runner`
@@ -17,67 +17,67 @@ OpenTest 应根据变更类型、风险和项目事实选择适用覆盖面。
 - `code-reviewer`
 - `speckit-checklist`
 
-## 选择规则
+## Selection Rules
 
-| 变更类型 | 默认考虑的证据 |
+| Change type | Default evidence to consider |
 | --- | --- |
-| 纯函数、工具函数、状态计算 | unit evidence |
-| 服务、模块协作、数据库读写 | integration evidence |
-| API、契约、错误处理 | contract、integration、error evidence |
-| 前端渲染或交互 | UI acceptance，必要时 component 或 E2E evidence |
-| 权限、支付、安全、数据写入、跨页面闭环 | high-risk acceptance 或 E2E evidence |
-| 文案、配置、小范围无行为变更 | targeted review 或 light evidence |
+| Pure functions, utility functions, state calculation | unit evidence |
+| Services, module collaboration, database reads/writes | integration evidence |
+| APIs, contracts, error handling | contract, integration, error evidence |
+| Frontend rendering or interaction | UI acceptance, plus component or E2E evidence when needed |
+| Permissions, payments, security, data writes, cross-page loops | high-risk acceptance or E2E evidence |
+| Copy, configuration, small non-behavioral changes | targeted review or light evidence |
 
-## 前端验收维度
+## Frontend Acceptance Dimensions
 
-前端或真实链路验收可从以下维度中选择适用项，不要求每次全部覆盖：
+Frontend or real workflow acceptance may choose applicable items from the following dimensions. Full coverage is not required every time:
 
-| 维度 | 含义 |
+| Dimension | Meaning |
 | --- | --- |
-| D1 页面渲染 | 标题、文案、结构、主要元素存在 |
-| D2 交互功能 | 点击、输入、选择、弹窗、菜单 |
-| D3 数据展示 | API 数据、格式化、状态展示 |
-| D4 表单验证 | 必填、格式、边界、关联校验 |
-| D5 导航流转 | 菜单、链接、返回、跨页面传参 |
-| D6 状态管理 | loading、empty、error、retry |
-| D7 权限控制 | 角色、路由守卫、越权拦截 |
-| D8 UI 反馈 | toast、modal、loading 指示 |
-| D9 组件联动 | 筛选、tab、数量、级联变化 |
-| D10 边界情况 | 空数据、长文本、特殊输入、前置数据缺失 |
-
-## 隐性场景默认挖掘
-
-OpenTest plan 阶段默认检查以下问题；适用则进入矩阵，不适用则简短说明：
-
-| 类别 | 默认追问 |
+| D1 Page rendering | Title, copy, structure, primary elements exist |
+| D2 Interaction behavior | Click, input, selection, dialog, menu |
+| D3 Data display | API data, formatting, status display |
+| D4 Form validation | Required fields, format, boundary, dependent validation |
+| D5 Navigation flow | Menu, link, back path, cross-page parameter passing |
+| D6 State management | loading, empty, error, retry |
+| D7 Permission control | Roles, route guards, unauthorized access blocking |
+| D8 UI feedback | toast, modal, loading indicator |
+| D9 Component coordination | Filters, tabs, counts, cascading changes |
+| D10 Boundary cases | Empty data, long text, special input, missing prerequisite data |
+
+## Default Implicit Scenario Mining
+
+The OpenTest plan phase checks these questions by default. If applicable, add them to the matrix; if not applicable, explain briefly:
+
+| Category | Default question |
 | --- | --- |
-| 输入为空 | 空字段是否阻止提交，错误显示在字段下方还是表单顶部 |
-| 输入非法 | 格式、长度、范围、重复值、依赖字段如何反馈 |
-| 网络失败 | 是否显示网络错误、重试入口，是否保留用户输入 |
-| 服务端失败 | 4xx/5xx 是否区分，是否避免泄露技术细节 |
-| 认证/会话 | token 过期、未登录、已登录访问登录页如何处理 |
-| 权限不足 | 操作隐藏、禁用还是显示权限说明 |
-| 重复提交 | 提交中按钮状态、防重复请求、幂等或冲突处理 |
-| 空数据 | 初始无数据和筛选无结果是否区分 |
-| 长内容/大数据 | 分页、截断、虚拟化、长文本和极端数量 |
-| 移动端 | 键盘遮挡、触控目标、窄屏布局和返回路径 |
-| 可访问性 | 键盘路径、焦点、错误关联、屏幕阅读器提示 |
-| 安全 | 敏感信息、越权、注入、CSRF/重复操作风险 |
-
-## 输出约束
-
-`/opentest-plan` 应优先输出窄矩阵：
+| Empty input | Does an empty field block submit, and does the error appear below the field or at form level? |
+| Invalid input | How are format, length, range, duplicate values, and dependent fields reported? |
+| Network failure | Is a network error and retry entry shown, and is user input preserved? |
+| Server failure | Are 4xx/5xx failures distinguished, and are technical details avoided? |
+| Auth/session | How are expired tokens, unauthenticated access, and signed-in visits to login handled? |
+| Missing permissions | Is the action hidden, disabled, or explained with permission copy? |
+| Duplicate submit | Does the submitting button state prevent duplicate requests, and is idempotency or conflict handled? |
+| Empty data | Are initial empty state and filtered no-result state distinguished? |
+| Long content/large data | Are pagination, truncation, virtualization, long text, and extreme counts handled? |
+| Mobile | Are keyboard overlap, touch targets, narrow layout, and return paths handled? |
+| Accessibility | Are keyboard path, focus, error association, and screen reader hints handled? |
+| Security | Are sensitive information, authorization bypass, injection, CSRF, and duplicate action risks considered? |
+
+## Output Constraints
+
+`/opentest-plan` should prefer a narrow matrix:
 
 ```markdown
-| ID | 意图 | 风险 | 必需证据 | 状态 |
+| ID | Intent | Risk | Required evidence | Status |
 | --- | --- | --- | --- | --- |
-| ACC-001 | 用户保存后看到成功反馈 | medium | UI 验收 | pending |
+| ACC-001 | User sees success feedback after save | medium | UI acceptance | pending |
 ```
 
-只有当风险或变更类型需要时，才增加覆盖维度、命令、证据路径和阻塞原因列。
+Add coverage dimension, command, evidence path, and blocker reason columns only when risk or change type requires them.
 
-## 质量门启发
+## Quality Gate Heuristics
 
-验证建议按 build、type、lint、test、security、diff 的顺序组织。构建、类型、lint、必需测试或必需验收失败时应阻塞通过；非必需证据缺口可以作为可解释风险记录。
+Verification is recommended in build, type, lint, test, security, diff order. Build, type, lint, required test, or required acceptance failures should block pass. Non-required evidence gaps may be recorded as explainable risk.
 
-工具、环境、前置数据或 MCP 不可用时，记录 `blocked` evidence，不得声称验收通过。
+When tooling, environment, prerequisite data, or MCP is unavailable, record `blocked` evidence and do not claim acceptance passed.

package/assets/skills/opentest/references/lifecycle.md

@@ -4,7 +4,7 @@
 
 `plan -> author -> run -> accept -> verify -> archive`
 
-`heal` 是失败恢复阶段，只在测试资产过期或验收执行路径失效时进入。
+`heal` is the failure recovery phase and should only be entered when test assets are stale or the acceptance execution path has broken.
 
 ## Exit Conditions
 

package/assets/skills/opentest/references/matrix-format.md

@@ -2,26 +2,26 @@
 
 ## Minimal Columns
 
-| ID | 意图 | 触发/输入 | 期望行为 | 风险 | 证据层级 | 必需证据 | 状态 |
+| ID | Intent | Trigger/Input | Expected behavior | Risk | Evidence layer | Required evidence | Status |
 | --- | --- | --- | --- | --- | --- | --- | --- |
 
 ## Optional Columns
 
-- 覆盖面
-- 命令
-- 证据路径
-- 阻塞原因
-- 风险接受说明
+- Coverage
+- Command
+- Evidence path
+- Blocker reason
+- Risk acceptance note
 
 Only add optional columns when risk or change type needs them.
 
 ## Evidence Layers
 
-- `unit`：纯函数、校验规则、状态计算。
-- `component`：表单反馈、按钮状态、局部 UI 状态。
-- `integration`：模块协作、API client、状态管理、mock server。
-- `contract`：请求/响应字段、错误码、权限响应。
-- `e2e`：跨页面、登录、权限、关键业务闭环。
-- `smoke`：关键页面或主路径不崩。
-- `browser-acceptance`：真实浏览器交互、反馈位置、响应式和视觉状态。
-- `security-review`：权限、敏感信息、越权、重复提交、注入风险。
+- `unit`: pure functions, validation rules, state calculation.
+- `component`: form feedback, button states, local UI states.
+- `integration`: module collaboration, API client, state management, mock server.
+- `contract`: request/response fields, error codes, permission responses.
+- `e2e`: cross-page flows, login, permissions, critical business loops.
+- `smoke`: key pages or happy paths do not crash.
+- `browser-acceptance`: real browser interaction, feedback location, responsive and visual state.
+- `security-review`: permissions, sensitive information, authorization bypass, duplicate submit, injection risk.

package/assets/skills/opentest/references/opentest-driven-development.md

@@ -1,48 +1,48 @@
 # OpenTest-Driven Development
 
-## 定位
+## Positioning
 
-OpenTest-driven development 不是传统 TDD 的替代名词。它把 TDD 放进更大的质量证据链里：先做隐性场景挖掘和风险矩阵，再决定哪些用 unit/component/integration/contract/E2E/smoke/browser acceptance/security review 证明。
+OpenTest-driven development is not a replacement name for traditional TDD. It places TDD inside a broader quality evidence chain: first mine implicit scenarios and build a risk matrix, then decide which behavior is proven by unit, component, integration, contract, E2E, smoke, browser acceptance, or security review evidence.
 
-## 为什么不是只写 TDD
+## Why Not Just TDD
 
-传统 TDD 容易只覆盖显性需求和 happy path。真实产品行为还包括：
+Traditional TDD can easily cover only explicit requirements and happy paths. Real product behavior also includes:
 
-- 空输入、非法输入和字段依赖。
-- 网络失败、服务端失败、认证过期和权限不足。
-- 错误反馈到底显示在字段下方、表单顶部、toast、modal 还是页面错误区。
+- Empty input, invalid input, and field dependencies.
+- Network failures, server failures, expired auth, and missing permissions.
+- Whether error feedback appears below a field, at the top of a form, in a toast, in a modal, or in a page error region.
 - loading、empty、retry、disabled、submitting、long content、mobile。
-- 跨页面跳转、返回恢复、数据刷新和重复提交。
+- Cross-page navigation, return restoration, data refresh, and duplicate submission.
 
-这些场景需要先进入 acceptance-to-test matrix，再决定证据层级。
+These scenarios should enter the acceptance-to-test matrix before evidence layers are selected.
 
-## 推荐顺序
+## Recommended Order
 
 ```text
-需求 / OpenSuper design
-  -> OpenTest plan: 隐性场景 + 风险 + 证据层级
-  -> OpenTest author: 测试资产和自然语言验收
-  -> build: 按矩阵实现
-  -> OpenTest run: 跑项目命令
-  -> OpenTest accept: 真实验收
-  -> OpenTest verify: 质量门报告
+Requirement / OpenSuper design
+  -> OpenTest plan: implicit scenarios + risk + evidence layers
+  -> OpenTest author: test assets and natural language acceptance
+  -> build: implement against the matrix
+  -> OpenTest run: run project commands
+  -> OpenTest accept: real acceptance
+  -> OpenTest verify: quality gate report
   -> OpenSuper verify/archive
 ```
 
-## 登录示例
+## Login Example
 
-| ID | 意图 | 触发/输入 | 期望行为 | 风险 | 证据层级 | 必需证据 | 状态 |
+| ID | Intent | Trigger/Input | Expected behavior | Risk | Evidence layer | Required evidence | Status |
 | --- | --- | --- | --- | --- | --- | --- | --- |
-| ACC-001 | 正确账号登录成功 | 合法账号密码 | 跳转目标页并建立会话 | high | e2e | 登录流程验收 | pending |
-| ACC-002 | 用户名为空 | 空用户名 + 任意密码 | 用户名字段下方错误，不发请求 | medium | component | 表单测试或 UI 验收 | pending |
-| ACC-003 | 密码错误 | 正确用户名 + 错误密码 | 表单顶部或密码区域显示认证失败，保留用户名 | high | integration | API mock + UI 验收 | pending |
-| ACC-004 | 网络断开 | 登录请求网络失败 | 显示网络错误和重试，不误报密码错误 | high | e2e | 网络失败验收 | pending |
-| ACC-005 | 重复点击提交 | 请求中再次点击 | 按钮 loading 且不重复提交 | medium | component | UI 状态测试 | pending |
-| ACC-006 | token 过期 | 访问受保护页面 | 回登录页并保留来源路径 | high | e2e | 会话过期验收 | pending |
-
-## 输出要求
-
-- 每个 required 场景必须有证据层级和执行面。
-- blocked 不能直接等于 pass；必须写原因和恢复路径。
-- high-risk 场景缺证据默认 fail，除非用户明确接受风险并写明理由。
-- 产品行为失败不能通过 heal 掩盖，必须回到实现或需求修正。
+| ACC-001 | Valid account logs in successfully | Valid username and password | Redirect to target page and establish session | high | e2e | Login flow acceptance | pending |
+| ACC-002 | Username is empty | Empty username plus any password | Show username field error and do not send request | medium | component | Form test or UI acceptance | pending |
+| ACC-003 | Password is wrong | Valid username plus wrong password | Show auth failure at form level or near password, preserving username | high | integration | API mock plus UI acceptance | pending |
+| ACC-004 | Network is disconnected | Login request network failure | Show network error and retry, without misreporting password failure | high | e2e | Network failure acceptance | pending |
+| ACC-005 | Submit clicked repeatedly | Click submit again while request is in flight | Button shows loading and duplicate submit is prevented | medium | component | UI state test | pending |
+| ACC-006 | Token expires | Visit protected page | Return to login and preserve source path | high | e2e | Session expiry acceptance | pending |
+
+## Output Requirements
+
+- Every required scenario must have an evidence layer and execution surface.
+- blocked is not pass; it must include a reason and recovery path.
+- Missing evidence for high-risk scenarios defaults to fail unless the user explicitly accepts the risk and the reason is written down.
+- Product behavior failure must not be hidden by heal; return to implementation or requirement correction.

package/assets/skills/opentest/templates/acceptance-template.md

@@ -1,4 +1,4 @@
-# OpenTest 验收用例
+# OpenTest Acceptance Case
 
 ## ACC-001