@pzy560117/opentest 0.1.6 → 0.1.7

package/assets/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.1.6",
+  "version": "0.1.7",
   "languages": [
     {
       "id": "en",
@@ -68,6 +68,7 @@
       "opentest/references/quality-gate.md",
       "opentest/templates/acceptance-template.md",
       "opentest/templates/archive-layout.md",
+      "opentest/templates/fixtures-template.md",
       "opentest/templates/matrix-template.md",
       "opentest/templates/plan-template.md",
       "opentest/templates/report-template.md",

package/assets/skills/opentest/scripts/opentest-detect.sh

@@ -39,6 +39,8 @@ summary() {
   if [ -f pom.xml ]; then printf 'maven_project: present\n'; else printf 'maven_project: missing\n'; fi
   if [ -f Cargo.toml ]; then printf 'cargo_project: present\n'; else printf 'cargo_project: missing\n'; fi
   if [ -d tests ]; then printf 'tests_dir: present\n'; else printf 'tests_dir: missing\n'; fi
+  if [ -d docs/opentest/fixtures ]; then printf 'fixtures_dir: present\n'; else printf 'fixtures_dir: missing\n'; fi
+  if [ -f docs/opentest/fixtures/seed.md ] || [ -f docs/opentest/fixtures/seed.json ]; then printf 'seed_data: present\n'; else printf 'seed_data: missing\n'; fi
   if [ -d docs/opentest ]; then printf 'opentest_docs: present\n'; else printf 'opentest_docs: missing\n'; fi
   if [ -d docs/opentest/acceptance ]; then printf 'acceptance_docs: present\n'; else printf 'acceptance_docs: missing\n'; fi
 

package/assets/skills/opentest/scripts/opentest-state.sh

@@ -69,7 +69,7 @@ require_state_file() {
 
 validate_known_field() {
   case "$1" in
-    workflow|phase|plan|matrix|acceptance|run_mode|run_report|test_framework|coverage_report|verification_result|verification_report|archived|created_at|updated_at)
+    workflow|phase|plan|matrix|fixtures|acceptance|run_mode|run_report|smoke_report|pre_push_report|test_framework|coverage_report|verification_result|verification_report|archived|created_at|updated_at)
       return 0
       ;;
     *)
@@ -110,9 +110,12 @@ workflow: standard
 phase: plan
 plan: null
 matrix: null
+fixtures: null
 acceptance: null
 run_mode: targeted
 run_report: null
+smoke_report: null
+pre_push_report: null
 test_framework: pytest
 coverage_report: null
 verification_result: pending
@@ -144,7 +147,7 @@ cmd_set() {
       validate_enum "$value" plan author run accept verify heal archive
       ;;
     run_mode)
-      validate_enum "$value" targeted fast full ci-like
+      validate_enum "$value" targeted fast full ci-like pre-push
       ;;
     verification_result)
       validate_enum "$value" pending pass fail risk-accepted
@@ -246,7 +249,7 @@ cmd_check() {
 
   validate_enum "$workflow" standard
   validate_enum "$phase" plan author run accept verify heal archive
-  validate_enum "$run_mode" targeted fast full ci-like
+  validate_enum "$run_mode" targeted fast full ci-like pre-push
   validate_enum "$verification_result" pending pass fail risk-accepted
   validate_enum "$archived" true false
 

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

@@ -30,3 +30,22 @@
 - status:
 - notes:
 - artifacts:
+
+## Full CRUD Flow
+
+Use this default full-chain case when the change touches create, read, update, delete, data writes, files, permissions, or cross-page flows.
+
+```text
+create -> list -> detail -> update -> read back -> delete -> confirm absence -> teardown
+```
+
+- fixture:
+- actor/role:
+- create assertion:
+- list assertion:
+- detail assertion:
+- update assertion:
+- read-back assertion:
+- delete/cancel assertion:
+- post-delete assertion:
+- cleanup assertion:

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

@@ -0,0 +1,52 @@
+# OpenTest Test Data Fixtures
+
+## Purpose
+
+Record the exact test data needed to prove every matrix item. Keep fixtures deterministic, isolated, and safe to rerun.
+
+## users
+
+| id | role | permissions | purpose |
+| --- | --- | --- | --- |
+| user-admin | admin | create/read/update/delete | CRUD happy path |
+| user-readonly | viewer | read only | permission denial |
+
+## roles
+
+- admin:
+- viewer:
+- unauthorized:
+
+## Entities
+
+| id | state | fields | used by ACC IDs |
+| --- | --- | --- | --- |
+| entity-create-valid | valid new record |  | ACC-001 |
+| entity-existing | persisted record |  | ACC-002, ACC-003, ACC-004 |
+| entity-invalid | invalid/boundary data |  | ACC-005 |
+
+## files/images
+
+| path | type | purpose | cleanup |
+| --- | --- | --- | --- |
+| docs/opentest/fixtures/files/sample-image.png | image | upload / preview / file validation | remove after test |
+
+## Seed
+
+- command:
+- data source:
+- idempotency rule:
+
+## teardown
+
+- command:
+- cleanup scope:
+- rollback notes:
+
+## Assertions
+
+- UI:
+- API:
+- DB/storage:
+- files:
+- logs:

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

@@ -2,5 +2,12 @@
 
 | ID | Intent | Coverage dimension | Trigger/Input | Expected behavior | Risk | Evidence layer | Framework/command | Required evidence | Gap/blocker | Status |
 | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| ACC-001 | Happy path succeeds | main path |  |  | low | smoke | project command or `python -m pytest` | targeted review | none | pending |
-| ACC-002 | Failure or boundary path | failure/boundary |  |  | medium | acceptance | natural-language acceptance or `python -m pytest` | UI/API acceptance | none | pending |
+| ACC-001 | create succeeds | create | valid fixture entity | entity is created and visible in list/detail | high | integration + acceptance | `python -m pytest` + real workflow | create evidence, UI/API/DB assertion, fixture used | none | pending |
+| ACC-002 | read/list/detail succeeds | read/list/detail | seeded entity | list, search/filter, and detail show correct data | high | integration + acceptance | `python -m pytest` + real workflow | read/list/detail evidence and data consistency check | none | pending |
+| ACC-003 | update succeeds | update | edited fixture entity | updated values persist after read back | high | integration + acceptance | `python -m pytest` + real workflow | update evidence and read-back assertion | none | pending |
+| ACC-004 | delete succeeds safely | delete | existing fixture entity | confirm/cancel behavior works; deleted item disappears after confirmation | high | integration + acceptance | `python -m pytest` + real workflow | delete evidence, cancel evidence, post-delete read check | none | pending |
+| ACC-005 | failure and boundary paths are handled | failure/boundary | invalid, empty, duplicate, unauthorized, or stale fixture data | clear feedback without corrupting data | high | unit/integration/acceptance | `python -m pytest` + acceptance | validation, permission, duplicate, stale-state evidence | none | pending |
+| ACC-006 | data consistency holds | data consistency | create/update/delete flow | UI, API, database/storage, files, and logs agree | high | integration | project command or `python -m pytest` | consistency evidence across surfaces | none | pending |
+| ACC-007 | end-to-end CRUD flow works | end-to-end CRUD | create -> list -> detail -> update -> read back -> delete | full user workflow completes and leaves clean state | high | E2E/acceptance | browser/API workflow | full-chain steps, screenshots/logs, cleanup evidence | none | pending |
+| ACC-008 | smoke gate passes | smoke | app starts and core entry points open | core route/API/CRUD happy path does not crash | high | smoke | project smoke command or targeted workflow | smoke_report path | none | pending |
+| ACC-009 | pre-push gate passes | pre-push | staged change before push | format/lint/type/unit/integration/smoke/diff checks pass or block push | high | pre-push | project command sequence | pre_push_report path | none | pending |

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

@@ -21,6 +21,24 @@
 | ID | evidence layer | required evidence | result | gap/risk |
 | --- | --- | --- | --- | --- |
 
+## Test Data
+
+- fixtures:
+- seed:
+- teardown:
+- data cleanup result:
+
+## Smoke
+
+- smoke_report:
+- result:
+
+## Pre-Push
+
+- pre_push_report:
+- command sequence:
+- result:
+
 ## Quality Gate
 
 - blocking:

package/assets/skills/opentest-author/SKILL.md

@@ -16,12 +16,14 @@ This phase turns the matrix into executable evidence. Write tests for behavior t
 1. Read `matrix` from `.opentest.yaml`.
 2. For unit/component/integration/contract evidence, create or update test files using the project's existing test framework.
 3. Default to pytest when code-level tests are required and the project has no explicit framework rule or existing framework. Prefer `tests/` and a command that can run with `python -m pytest`.
-4. For E2E, smoke, browser acceptance, real APIs, or cross-page flows, write natural language acceptance cases under `docs/opentest/acceptance/`.
-5. For frontend feedback cases, specify the feedback location and shape, such as field-level errors, form-level errors, toast, modal, inline status, or page error state.
-6. Record reasons and risk for evidence that is not applicable or cannot currently be created.
-7. Write the `.opentest.yaml` `acceptance` field.
-8. If the project uses Loop Handoff, update `docs/loop-handoff/latest.md` with test assets, natural language acceptance cases, gaps/risks, and next step.
-9. Run `bash "$OPENTEST_GUARD" author --apply`.
+4. Create or update `docs/opentest/fixtures/` from the fixtures template, including users, roles, entities, files/images, seed, teardown, and assertion surfaces.
+5. For E2E, smoke, browser acceptance, real APIs, or cross-page flows, write natural language acceptance cases under `docs/opentest/acceptance/`.
+6. For CRUD or data-writing changes, include a full workflow case: create -> list -> detail -> update -> read back -> delete -> confirm absence -> teardown.
+7. For frontend feedback cases, specify the feedback location and shape, such as field-level errors, form-level errors, toast, modal, inline status, or page error state.
+8. Record reasons and risk for evidence that is not applicable or cannot currently be created.
+9. Write the `.opentest.yaml` `fixtures` and `acceptance` fields.
+10. If the project uses Loop Handoff, update `docs/loop-handoff/latest.md` with fixtures, seed/teardown, test assets, natural language acceptance cases, gaps/risks, and next step.
+11. Run `bash "$OPENTEST_GUARD" author --apply`.
 
 ## Existing Skill Routing
 

package/assets/skills/opentest-plan/SKILL.md

@@ -16,12 +16,14 @@ This phase is the entry point for OpenTest-driven development. Before implementa
 1. Read project rules, requirements, design, diff, existing test commands, and `opentest/references/codex-harness-coverage-heuristics.md`.
 2. If the change involves frontend UI, forms, navigation, CRUD, status feedback, or motion, first read the project's `docs/frontend/DESIGN.md` and any available `harness-frontend-design` / `product-ui-defaults` rules.
 3. Classify the change type, risk level, applicable coverage dimensions, and whether code-level evidence should use an existing project framework or the default `pytest` framework.
-4. Mine implicit scenarios: empty input, invalid input, network failure, missing permissions, duplicate submission, long content, empty data, error mapping, mobile behavior, accessibility, cross-page return paths, and state restoration.
-5. Produce a narrow matrix with at least `ID`, `intent`, `coverage dimension`, `trigger/input`, `expected behavior`, `risk`, `evidence layer`, `framework/command`, `required evidence`, `gap/blocker`, and `status`.
-6. Mark applicable but uncovered evidence as `gap`, and record a concrete blocker or recovery path instead of leaving coverage unknown.
-7. Write the `.opentest.yaml` `plan` and `matrix` fields.
-8. If the project uses Loop Handoff, update `docs/loop-handoff/latest.md` with the plan path, matrix path, current phase, and next step.
-9. Run `bash "$OPENTEST_GUARD" plan --apply`.
+4. Define the test data plan: users, roles, permissions, entities, files/images, seed command, teardown command, and UI/API/DB/file/log assertions.
+5. Mine implicit scenarios: empty input, invalid input, network failure, missing permissions, duplicate submission, long content, empty data, error mapping, mobile behavior, accessibility, cross-page return paths, and state restoration.
+6. Apply the CRUD baseline for create, read/list/detail/search/filter, update/read-back, delete/cancel/post-delete, data consistency, and end-to-end CRUD flow whenever the change touches persisted data, APIs, forms, files, or stateful workflows.
+7. Produce a narrow matrix with at least `ID`, `intent`, `coverage dimension`, `trigger/input`, `expected behavior`, `risk`, `evidence layer`, `framework/command`, `required evidence`, `gap/blocker`, and `status`.
+8. Mark applicable but uncovered evidence as `gap`, and record a concrete blocker or recovery path instead of leaving coverage unknown.
+9. Write the `.opentest.yaml` `plan`, `matrix`, and `fixtures` fields.
+10. If the project uses Loop Handoff, update `docs/loop-handoff/latest.md` with the plan path, matrix path, fixtures path, current phase, and next step.
+11. Run `bash "$OPENTEST_GUARD" plan --apply`.
 
 ## Constraints
 
@@ -30,3 +32,5 @@ Do not expand the full Codex Harness checklist into fixed required items. Keep a
 Do not force all evidence into unit tests. The matrix must state which behavior is proven by unit, component, integration, contract, E2E, smoke, browser acceptance, or security review evidence.
 
 Coverage completeness means every applicable product behavior, failure path, boundary, and risk surface has either required evidence or an explicit gap/blocker. It does not mean every task must run every possible test type.
+
+CRUD baseline and test data are default requirements for data-writing changes. If any CRUD leg is not applicable, the matrix must state why.

package/assets/skills/opentest-run/SKILL.md

@@ -15,17 +15,20 @@ Run existing project verification commands and write a run report.
 - `fast`: run fast feedback commands, such as type, lint, and unit.
 - `full`: run the project's full test command set.
 - `ci-like`: reproduce CI verification order as closely as practical.
+- `pre-push`: run the push gate sequence before publishing or pushing.
 
 Evidence layers are decided by the matrix. Do not run only unit tests just because `npm test` exists. If the matrix requires integration, contract, E2E, smoke, or security checks, run the matching project command or record missing command / blocked.
 
 If `.opentest.yaml` has `test_framework: pytest`, or code-level test evidence is required and no project framework is declared, use `python -m pytest` as the default test command. When the matrix requires coverage evidence, prefer `python -m pytest --cov=. --cov-report=term-missing` and write the coverage output path to `.opentest.yaml` `coverage_report`. If pytest or pytest-cov is unavailable, record `missing command` with the install/remediation step instead of passing the gate.
 
+Smoke evidence is required for ordinary feature changes unless explicitly not applicable in the matrix. A pre-push run should include the project equivalent of format/check, lint, type, unit, integration-targeted, smoke, and `git diff --check`. Missing commands must be recorded as missing or not applicable.
+
 ## Steps
 
 1. Read `run_mode` and the matrix from `.opentest.yaml`.
 2. Prefer explicit project commands, and select targeted, fast, full, or ci-like mode based on matrix evidence layers.
 3. If no explicit command exists for code-level tests, run or document the default pytest command.
-4. Record command, exit code, summary, coverage output, and log path under `docs/opentest/runs/`.
-5. Write the `.opentest.yaml` `run_report` field, and write `coverage_report` when coverage evidence was required or produced.
+4. Record command, exit code, summary, coverage output, smoke output, pre-push output, and log path under `docs/opentest/runs/`.
+5. Write the `.opentest.yaml` `run_report` field, and write `coverage_report`, `smoke_report`, or `pre_push_report` when the matching evidence was required or produced.
 6. If the project uses Loop Handoff, update `docs/loop-handoff/latest.md` with verification already run, verification not run, failures/blockers, run report path, and next step.
 7. Run `bash "$OPENTEST_GUARD" run --apply`.

package/assets/skills/opentest-verify/SKILL.md

@@ -20,6 +20,9 @@ The verification report must also review the matrix and confirm:
 
 - Every required evidence item has a pass, fail, blocked, or risk-accepted conclusion.
 - Coverage completeness is checked: every applicable coverage dimension in the matrix has required evidence, a run/acceptance result, or an explicit gap/blocker with recovery path.
+- Test data is traceable: fixture, seed, teardown, and cleanup evidence exist for data-writing or CRUD changes.
+- Smoke evidence is required unless the matrix explicitly marks smoke as not applicable.
+- pre-push evidence is required before push/publish unless the user explicitly skips it and the report records the risk.
 - High-risk behavior does not pass merely because tooling, a test framework, or seed data is missing.
 - If code-level coverage was required and `test_framework: pytest` is active, the report must include the `python -m pytest` command result and the `coverage_report` path, or fail/block with a reason.
 - Blocked evidence includes a blocker reason and recovery path.

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

@@ -30,3 +30,22 @@
 - status:
 - 备注:
 - 产物:
+
+## 完整 CRUD 链路
+
+当变更涉及新增、查询、修改、删除、数据写入、文件、权限或跨页面流程时，默认补这个全链路用例。
+
+```text
+新增 -> 列表 -> 详情 -> 修改 -> 回读 -> 删除 -> 确认消失 -> 清理
+```
+
+- fixture:
+- 执行角色:
+- 新增断言:
+- 列表断言:
+- 详情断言:
+- 修改断言:
+- 回读断言:
+- 删除/取消断言:
+- 删除后断言:
+- 清理断言:

package/assets/skills-zh/opentest/templates/fixtures-template.md

@@ -0,0 +1,52 @@
+# OpenTest 测试数据 Fixtures
+
+## 目的
+
+记录每个矩阵项需要的测试数据。测试数据必须确定、隔离、可重复执行。
+
+## 用户
+
+| id | 角色 | 权限 | 用途 |
+| --- | --- | --- | --- |
+| user-admin | admin | 新增/查询/修改/删除 | CRUD 主路径 |
+| user-readonly | viewer | 只读 | 权限拒绝 |
+
+## 角色
+
+- admin:
+- viewer:
+- unauthorized:
+
+## 实体
+
+| id | 状态 | 字段 | 对应 ACC |
+| --- | --- | --- | --- |
+| entity-create-valid | 有效新记录 |  | ACC-001 |
+| entity-existing | 已存在记录 |  | ACC-002, ACC-003, ACC-004 |
+| entity-invalid | 非法/边界数据 |  | ACC-005 |
+
+## 文件/图片
+
+| 路径 | 类型 | 用途 | 清理 |
+| --- | --- | --- | --- |
+| docs/opentest/fixtures/files/sample-image.png | 图片 | 上传/预览/文件校验 | 测试后删除 |
+
+## Seed
+
+- 命令:
+- 数据来源:
+- 幂等规则:
+
+## Teardown
+
+- 命令:
+- 清理范围:
+- 回滚说明:
+
+## 断言
+
+- UI:
+- API:
+- DB/存储:
+- 文件:
+- 日志:

package/assets/skills-zh/opentest/templates/matrix-template.md

@@ -2,5 +2,12 @@
 
 | ID | 意图 | 覆盖维度 | 触发/输入 | 期望行为 | 风险 | 证据层级 | 框架/命令 | 必需证据 | 缺口/阻塞 | 状态 |
 | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| ACC-001 | 主路径成功 | 主路径 |  |  | low | smoke | 项目命令或 `python -m pytest` | targeted review | 无 | pending |
-| ACC-002 | 失败/边界路径 | 失败/边界 |  |  | medium | acceptance | 自然语言验收或 `python -m pytest` | UI/API 验收 | 无 | pending |
+| ACC-001 | 新增成功 | 新增 | 有效 fixture 实体 | 创建成功，并能在列表/详情中看到 | high | integration + acceptance | `python -m pytest` + 真实工作流 | 新增证据、UI/API/DB 断言、使用的测试数据 | 无 | pending |
+| ACC-002 | 查询/列表/详情成功 | 查询/列表/详情 | 已 seed 的实体 | 列表、搜索/筛选、详情显示正确数据 | high | integration + acceptance | `python -m pytest` + 真实工作流 | 查询/列表/详情证据和数据一致性检查 | 无 | pending |
+| ACC-003 | 修改成功 | 修改 | 编辑 fixture 实体 | 保存后回读仍是新值 | high | integration + acceptance | `python -m pytest` + 真实工作流 | 修改证据和回读断言 | 无 | pending |
+| ACC-004 | 删除安全成功 | 删除 | 已存在 fixture 实体 | 删除确认/取消正确；确认删除后不可见 | high | integration + acceptance | `python -m pytest` + 真实工作流 | 删除证据、取消证据、删除后回读检查 | 无 | pending |
+| ACC-005 | 失败/边界路径可控 | 失败/边界 | 非法、空、重复、无权限或过期 fixture 数据 | 给出清晰反馈且不污染数据 | high | unit/integration/acceptance | `python -m pytest` + 验收 | 校验、权限、重复提交、过期状态证据 | 无 | pending |
+| ACC-006 | 数据一致性成立 | 数据一致性 | 新增/修改/删除闭环 | UI、API、数据库/存储、文件和日志一致 | high | integration | 项目命令或 `python -m pytest` | 跨界面一致性证据 | 无 | pending |
+| ACC-007 | 端到端 CRUD 链路可用 | 端到端 CRUD | 新增 -> 列表 -> 详情 -> 修改 -> 回读 -> 删除 | 完整用户链路通过并留下干净状态 | high | E2E/acceptance | 浏览器/API 工作流 | 全链路步骤、截图/日志、清理证据 | 无 | pending |
+| ACC-008 | 冒烟质量门通过 | 冒烟 | 应用启动且核心入口可访问 | 核心路由/API/CRUD 主路径不崩 | high | smoke | 项目冒烟命令或 targeted workflow | smoke_report 路径 | 无 | pending |
+| ACC-009 | pre-push 质量门通过 | pre-push | push 前 staged change | format/lint/type/unit/integration/smoke/diff 检查通过，否则阻止 push | high | pre-push | 项目命令序列 | pre_push_report 路径 | 无 | pending |

package/assets/skills-zh/opentest/templates/report-template.md

@@ -21,6 +21,24 @@
 | ID | 证据层级 | 必需证据 | result | 缺口/风险 |
 | --- | --- | --- | --- | --- |
 
+## 测试数据
+
+- fixtures:
+- seed:
+- teardown:
+- 数据清理结果:
+
+## 冒烟
+
+- smoke_report:
+- result:
+
+## Pre-Push
+
+- pre_push_report:
+- 命令序列:
+- result:
+
 ## 质量门
 
 - 阻塞项:

package/assets/skills-zh/opentest-author/SKILL.md

@@ -16,12 +16,14 @@ description: "OpenTest 阶段 2：根据矩阵补齐测试资产和自然语言
 1. 读取 `.opentest.yaml` 中的 `matrix`。
 2. 对 unit/component/integration/contract 证据，按项目已有测试框架创建或更新测试文件。
 3. 当矩阵要求代码级测试、且项目没有明确框架规则或既有框架时，默认使用 pytest；优先放在 `tests/`，并确保可用 `python -m pytest` 运行。
-4. 对 E2E、smoke、browser acceptance、真实 API 或跨页面流程，写入 `docs/opentest/acceptance/` 自然语言验收用例。
-5. 对前端反馈类用例，写清反馈位置和形态，例如字段下方错误、表单顶部错误、轻提示、模态框、行内状态或页面错误态。
-6. 对不适用或当前无法补齐的证据，记录原因和风险。
-7. 写入 `.opentest.yaml` 的 `acceptance` 字段。
-8. 更新 `docs/loop-handoff/latest.md`（如果项目使用 Loop Handoff），记录测试资产、自然语言验收用例、gap/risk 和下一步。
-9. 运行 `bash "$OPENTEST_GUARD" author --apply`。
+4. 根据 fixtures 模板创建或更新 `docs/opentest/fixtures/`，包括用户、角色、实体、文件/图片、seed、teardown 和断言界面。
+5. 对 E2E、smoke、browser acceptance、真实 API 或跨页面流程，写入 `docs/opentest/acceptance/` 自然语言验收用例。
+6. 对 CRUD 或数据写入类变更，补完整工作流用例：新增 -> 列表 -> 详情 -> 修改 -> 回读 -> 删除 -> 确认消失 -> 清理。
+7. 对前端反馈类用例，写清反馈位置和形态，例如字段下方错误、表单顶部错误、轻提示、模态框、行内状态或页面错误态。
+8. 对不适用或当前无法补齐的证据，记录原因和风险。
+9. 写入 `.opentest.yaml` 的 `fixtures` 和 `acceptance` 字段。
+10. 更新 `docs/loop-handoff/latest.md`（如果项目使用 Loop Handoff），记录 fixtures、seed/teardown、测试资产、自然语言验收用例、gap/risk 和下一步。
+11. 运行 `bash "$OPENTEST_GUARD" author --apply`。
 
 ## 现有技能路由
 

package/assets/skills-zh/opentest-plan/SKILL.md

@@ -16,12 +16,14 @@ description: "OpenTest 阶段 1：分析变更、风险和项目事实，生成
 1. 读取项目规则、需求、设计、diff、现有测试命令和 `opentest/references/codex-harness-coverage-heuristics.md`。
 2. 如果存在前端、表单、导航、CRUD、状态反馈或动效，优先读取项目内 `docs/frontend/DESIGN.md` 和可用的 `harness-frontend-design` / `product-ui-defaults` 规则。
 3. 判断变更类型、风险等级、适用覆盖维度，以及代码级证据应使用项目已有框架还是默认 `pytest` 框架。
-4. 做隐性场景挖掘：空输入、非法输入、网络失败、权限不足、重复提交、长内容、空数据、错误映射、移动端、可访问性、跨页面返回和状态恢复。
-5. 生成窄矩阵，至少包含 `ID`、`意图`、`覆盖维度`、`触发/输入`、`期望行为`、`风险`、`证据层级`、`框架/命令`、`必需证据`、`缺口/阻塞`、`状态`。
-6. 对适用但未覆盖的证据面标记 `gap`，并写清具体阻塞或恢复路径，不把覆盖状态留成 unknown。
-7. 写入 `.opentest.yaml` 的 `plan` 和 `matrix` 字段。
-8. 更新 `docs/loop-handoff/latest.md`（如果项目使用 Loop Handoff），记录 plan、matrix 路径、当前阶段和下一步。
-9. 运行 `bash "$OPENTEST_GUARD" plan --apply`。
+4. 定义测试数据计划：用户、角色、权限、实体、文件/图片、seed 命令、teardown 命令，以及 UI/API/DB/文件/日志断言。
+5. 做隐性场景挖掘：空输入、非法输入、网络失败、权限不足、重复提交、长内容、空数据、错误映射、移动端、可访问性、跨页面返回和状态恢复。
+6. 对涉及持久化数据、API、表单、文件或有状态工作流的变更，默认套用 CRUD 基线：新增、查询/列表/详情/搜索/筛选、修改/回读、删除/取消/删除后检查、数据一致性、端到端 CRUD。
+7. 生成窄矩阵，至少包含 `ID`、`意图`、`覆盖维度`、`触发/输入`、`期望行为`、`风险`、`证据层级`、`框架/命令`、`必需证据`、`缺口/阻塞`、`状态`。
+8. 对适用但未覆盖的证据面标记 `gap`，并写清具体阻塞或恢复路径，不把覆盖状态留成 unknown。
+9. 写入 `.opentest.yaml` 的 `plan`、`matrix` 和 `fixtures` 字段。
+10. 更新 `docs/loop-handoff/latest.md`（如果项目使用 Loop Handoff），记录 plan、matrix、fixtures 路径、当前阶段和下一步。
+11. 运行 `bash "$OPENTEST_GUARD" plan --apply`。
 
 ## 约束
 
@@ -30,3 +32,5 @@ description: "OpenTest 阶段 1：分析变更、风险和项目事实，生成
 不要把所有证据都写成 unit test。矩阵要明确哪些用 unit/component/integration/contract/E2E/smoke/browser acceptance/security review 证明。
 
 覆盖完整性指每个适用的产品行为、失败路径、边界和风险面都有必需证据，或有明确的 gap/blocker；不是要求每次任务都跑所有测试类型。
+
+CRUD 基线和测试数据是数据写入类变更的默认要求。若某个 CRUD 环节不适用，必须在矩阵中写明原因。

package/assets/skills-zh/opentest-run/SKILL.md

@@ -15,17 +15,20 @@ description: "OpenTest 阶段 3：按 targeted、fast、full 或 ci-like 模式
 - `fast`：运行快速反馈命令，例如 type、lint、unit。
 - `full`：运行项目完整测试命令。
 - `ci-like`：尽量复现 CI 验证顺序。
+- `pre-push`：push 或发布前运行推送质量门序列。
 
 证据层级由矩阵决定。不要因为存在 `npm test` 就只跑 unit test；如果矩阵要求 integration、contract、E2E、smoke 或安全检查，必须运行对应项目命令，或记录 missing command / blocked。
 
 如果 `.opentest.yaml` 中 `test_framework: pytest`，或矩阵要求代码级测试但项目没有声明测试框架，默认测试命令使用 `python -m pytest`。当矩阵要求覆盖率证据时，优先使用 `python -m pytest --cov=. --cov-report=term-missing`，并把覆盖率输出路径写入 `.opentest.yaml` 的 `coverage_report`。如果缺少 pytest 或 pytest-cov，记录 `missing command` 和安装/恢复步骤，不允许直接通过质量门。
 
+普通功能变更默认必须有冒烟证据，除非矩阵明确写明不适用。pre-push 运行应包含项目等价的 format/check、lint、type、unit、targeted integration、smoke 和 `git diff --check`；缺少命令时必须记录 missing 或 not applicable。
+
 ## 步骤
 
 1. 读取 `.opentest.yaml` 的 `run_mode` 和矩阵。
 2. 优先使用项目显式命令，按矩阵中的证据层级选择 targeted、fast、full 或 ci-like。
 3. 如果代码级测试没有显式命令，运行或记录默认 pytest 命令。
-4. 记录命令、退出码、摘要、覆盖率输出和日志路径到 `docs/opentest/runs/`。
-5. 写入 `.opentest.yaml` 的 `run_report` 字段；当要求或产生覆盖率证据时，也写入 `coverage_report`。
+4. 记录命令、退出码、摘要、覆盖率输出、冒烟输出、pre-push 输出和日志路径到 `docs/opentest/runs/`。
+5. 写入 `.opentest.yaml` 的 `run_report` 字段；当要求或产生对应证据时，也写入 `coverage_report`、`smoke_report` 或 `pre_push_report`。
 6. 更新 `docs/loop-handoff/latest.md`（如果项目使用 Loop Handoff），记录已运行验证、未运行验证、失败/阻塞、run report 路径和下一步。
 7. 运行 `bash "$OPENTEST_GUARD" run --apply`。

package/assets/skills-zh/opentest-verify/SKILL.md

@@ -20,6 +20,9 @@ description: "OpenTest 阶段 5：应用质量门并生成验证报告。"
 
 - 每个 required evidence 都有 pass、fail、blocked 或 risk-accepted 结论。
 - 覆盖完整性已检查：矩阵中的每个适用覆盖维度都有必需证据、运行/验收结果，或带恢复路径的明确 gap/blocker。
+- 测试数据可追踪：数据写入或 CRUD 变更必须有 fixture、seed、teardown 和清理证据。
+- 必须有冒烟证据，除非矩阵明确标记 smoke 不适用。
+- push/publish 前必须有 pre-push 证据；除非用户明确跳过，并在报告里记录风险。
 - 高风险行为不能因为没有工具、没有测试框架或没有 seed data 就直接通过。
 - 如果要求代码级覆盖率且 `test_framework: pytest` 生效，报告必须包含 `python -m pytest` 命令结果和 `coverage_report` 路径；否则必须 fail/block 并写明原因。
 - blocked evidence 必须包含阻塞原因和后续恢复路径。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pzy560117/opentest",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "description": "OpenTest quality evidence lifecycle skills for Codex",
   "keywords": [
     "opentest",

package/scripts/smoke-test.js

@@ -32,6 +32,15 @@ function assert(condition, message) {
   }
 }
 
+function readRequiredText(filePath, message) {
+  try {
+    return readFileSync(filePath, 'utf8');
+  } catch {
+    assert(false, message);
+    return '';
+  }
+}
+
 function pathSegments(file) {
   return file.split(/[\\/]+/).filter(Boolean);
 }
@@ -183,6 +192,56 @@ function assertDefaultPytestContracts() {
   assert(chineseMatrix.includes('覆盖维度') && chineseMatrix.includes('框架/命令') && chineseMatrix.includes('缺口/阻塞'), '[COVERAGE] Chinese matrix template must include coverage, command, and gap columns');
 }
 
+function assertCompleteTestingWorkflowContracts() {
+  const stateScript = readFileSync('assets/skills/opentest/scripts/opentest-state.sh', 'utf8');
+  const detectScript = readFileSync('assets/skills/opentest/scripts/opentest-detect.sh', 'utf8');
+  const manifestText = readFileSync('assets/manifest.json', 'utf8');
+  const englishPlan = readFileSync('assets/skills/opentest-plan/SKILL.md', 'utf8');
+  const chinesePlan = readFileSync('assets/skills-zh/opentest-plan/SKILL.md', 'utf8');
+  const englishAuthor = readFileSync('assets/skills/opentest-author/SKILL.md', 'utf8');
+  const chineseAuthor = readFileSync('assets/skills-zh/opentest-author/SKILL.md', 'utf8');
+  const englishRun = readFileSync('assets/skills/opentest-run/SKILL.md', 'utf8');
+  const chineseRun = readFileSync('assets/skills-zh/opentest-run/SKILL.md', 'utf8');
+  const englishVerify = readFileSync('assets/skills/opentest-verify/SKILL.md', 'utf8');
+  const chineseVerify = readFileSync('assets/skills-zh/opentest-verify/SKILL.md', 'utf8');
+  const englishMatrix = readFileSync('assets/skills/opentest/templates/matrix-template.md', 'utf8');
+  const chineseMatrix = readFileSync('assets/skills-zh/opentest/templates/matrix-template.md', 'utf8');
+  const englishFixture = readRequiredText('assets/skills/opentest/templates/fixtures-template.md', '[FIXTURES] missing English fixture template');
+  const chineseFixture = readRequiredText('assets/skills-zh/opentest/templates/fixtures-template.md', '[FIXTURES] missing Chinese fixture template');
+  const englishAcceptance = readFileSync('assets/skills/opentest/templates/acceptance-template.md', 'utf8');
+  const chineseAcceptance = readFileSync('assets/skills-zh/opentest/templates/acceptance-template.md', 'utf8');
+
+  assert(manifestText.includes('opentest/templates/fixtures-template.md'), '[FIXTURES] manifest must ship fixture templates');
+  assert(stateScript.includes('fixtures: null'), '[FIXTURES] state init must track fixtures');
+  assert(stateScript.includes('smoke_report: null'), '[SMOKE] state init must track smoke_report');
+  assert(stateScript.includes('pre_push_report: null'), '[PREPUSH] state init must track pre_push_report');
+  assert(stateScript.includes('fixtures|'), '[FIXTURES] state script must allow fixtures field updates');
+  assert(stateScript.includes('targeted fast full ci-like pre-push'), '[PREPUSH] state script must allow pre-push run mode');
+  assert(detectScript.includes('fixtures_dir:'), '[FIXTURES] detect summary must report fixtures_dir');
+  assert(detectScript.includes('seed_data:'), '[FIXTURES] detect summary must report seed_data');
+
+  for (const keyword of ['create', 'read/list/detail', 'update', 'delete', 'data consistency', 'smoke', 'pre-push', 'end-to-end CRUD']) {
+    assert(englishMatrix.includes(keyword), `[MATRIX] English matrix missing ${keyword}`);
+  }
+  for (const keyword of ['新增', '查询/列表/详情', '修改', '删除', '数据一致性', '冒烟', 'pre-push', '端到端 CRUD']) {
+    assert(chineseMatrix.includes(keyword), `[MATRIX] Chinese matrix missing ${keyword}`);
+  }
+
+  assert(englishFixture.includes('users') && englishFixture.includes('roles') && englishFixture.includes('files/images') && englishFixture.includes('teardown'), '[FIXTURES] English fixture template must cover users, roles, files/images, and teardown');
+  assert(chineseFixture.includes('用户') && chineseFixture.includes('角色') && chineseFixture.includes('文件/图片') && chineseFixture.includes('清理'), '[FIXTURES] Chinese fixture template must cover users, roles, files/images, and teardown');
+  assert(englishAcceptance.includes('create -> list -> detail -> update -> read back -> delete'), '[ACCEPTANCE] English acceptance template must include full CRUD flow');
+  assert(chineseAcceptance.includes('新增 -> 列表 -> 详情 -> 修改 -> 回读 -> 删除'), '[ACCEPTANCE] Chinese acceptance template must include full CRUD flow');
+
+  assert(englishPlan.includes('CRUD baseline') && englishPlan.includes('test data'), '[PLAN] English plan skill must require CRUD baseline and test data planning');
+  assert(chinesePlan.includes('CRUD 基线') && chinesePlan.includes('测试数据'), '[PLAN] Chinese plan skill must require CRUD baseline and test data planning');
+  assert(englishAuthor.includes('fixtures') && englishAuthor.includes('seed') && englishAuthor.includes('teardown'), '[AUTHOR] English author skill must require fixtures, seed, and teardown assets');
+  assert(chineseAuthor.includes('fixtures') && chineseAuthor.includes('seed') && chineseAuthor.includes('teardown'), '[AUTHOR] Chinese author skill must require fixtures, seed, and teardown assets');
+  assert(englishRun.includes('pre-push') && englishRun.includes('smoke_report') && englishRun.includes('pre_push_report'), '[RUN] English run skill must cover pre-push, smoke_report, and pre_push_report');
+  assert(chineseRun.includes('pre-push') && chineseRun.includes('smoke_report') && chineseRun.includes('pre_push_report'), '[RUN] Chinese run skill must cover pre-push, smoke_report, and pre_push_report');
+  assert(englishVerify.includes('Smoke evidence is required') && englishVerify.includes('pre-push evidence is required') && englishVerify.includes('fixture'), '[VERIFY] English verify skill must gate smoke, pre-push, and fixtures');
+  assert(chineseVerify.includes('必须有冒烟证据') && chineseVerify.includes('必须有 pre-push 证据') && chineseVerify.includes('测试数据'), '[VERIFY] Chinese verify skill must gate smoke, pre-push, and test data');
+}
+
 async function assertPrepublishRejectsPublishSecretTextFiles() {
   const fixtureDir = path.join('assets', 'opentest-smoke-secret-fixtures');
   const fixtures = [
@@ -487,6 +546,7 @@ runManifestPathRelativitySelfCheck();
 assertManifestStructure();
 assertPrepublishGateCoversManifestAssets();
 assertDefaultPytestContracts();
+assertCompleteTestingWorkflowContracts();
 assertOpenTestSearchRootsCoverPlatforms();
 assertLanguageAssetContracts();
 await assertPrepublishRejectsPublishSecretTextFiles();