@guanlin4924/devflow-pi 0.1.21 → 0.1.23

package/README.md

@@ -1,8 +1,8 @@
 # Devflow for Oh My Pi
 
-面向项目代码开发的 OMP 原生能力仓库。仓库同时提供 Agent Skills、运行时 extension、task agents、项目配置模板和 marketplace 插件目录。
+面向项目代码开发的 OMP 原生 Devflow 能力仓库。仓库同时提供 Agent Skills、运行时 extension、task agents、项目配置模板和 marketplace 插件目录。Devflow 的流程真相由需求图谱、冻结测试集、机器证据和控制面状态组成，Markdown 只负责展示。
 
-完整的第一性原理拆分、控制面不变量和对抗式审查见 [`docs/OMP-NATIVE-ARCHITECTURE.md`](docs/OMP-NATIVE-ARCHITECTURE.md)。
+完整的第一性原理拆分、控制面不变量和对抗式审查见 [`docs/OMP-NATIVE-ARCHITECTURE.md`](docs/OMP-NATIVE-ARCHITECTURE.md)。本项目不依赖外部会话式验收或里程碑工作流；验收和版本收口均由 Devflow 自有节点完成。
 
 ## Devflow 专项 Pi（当前功能分支）
 
@@ -80,14 +80,27 @@ skills:
     # 其余四个插件目录同理
 ```
 
-## 完整接入：项目固定版本
+## npm 安装：推荐入口
+
+```bash
+npm install -g @guanlin4924/devflow-pi@0.1.22
+cd /path/to/your-project
+devflow-pi init
+devflow-pi doctor
+devflow-pi
+```
+
+npm 包已经内置完整 Devflow Runtime、Extension、task agents、项目策略和生命周期配置，不需要复制私有 Git 仓库，也不需要把本仓库作为 submodule 加入业务项目。
+
+## 私有源码兼容模式
+
+`install.sh --apply` 只用于已经获得内部源码访问权限的开发环境。本文档不提供私有仓库地址；在内部工作副本中执行：
 
 ```bash
-git submodule add https://gitee.com/guanlin4924/skill-kit.git .skills
 bash .skills/install.sh --apply
 ```
 
-`install.sh --apply` 是完整 Devflow Runtime 的标准入口。它不仅安装能力目录，还部署 `/devflow` 所依赖的 Extension、task agents、项目策略和生命周期配置。安装器会执行 postflight；已有但不兼容的 `.omp/config.yml` 会使安装失败，不会再以警告方式假装安装完整。
+它会执行 postflight；已有但不兼容的 `.omp/config.yml` 会使安装失败，不会以警告方式假装安装完整。
 
 安装器只生成以下 OMP 原生资源：
 
@@ -100,7 +113,7 @@ bash .skills/install.sh --apply
 .agent-gates/index-first.json
 ```
 
-已有且兼容的 `.omp/config.yml` 会保留。已有配置缺少 Devflow skill 来源、model overrides 或工具策略时，先审查差异，再显式运行：
+已有且兼容的 `.omp/config.yml` 会保留。源码兼容模式下，已有配置缺少 Devflow skill 来源、model overrides 或工具策略时，先审查差异，再显式运行：
 
 ```bash
 bash .skills/install.sh --apply --force-config
@@ -128,31 +141,28 @@ bash .skills/install.sh --apply --force-config
                                                         ↓
                     CP-3：校验候选绑定 → 冻结 TC → 写入 Core attestation
                                                         ↓
-                    RED / GREEN / REGRESSION 证据 → 按冻结 TC 执行 API / 页面 / 专项测试 → UAT → CP-4
+                    RED / GREEN / REGRESSION 证据 → 按冻结 TC 执行 API / 页面 / 专项测试 → CP-4 → 版本收口
 ```
 
 - `TC-*` 的步骤和 oracle 在代码出现前冻结；CP-3 在同一次确认中先校验候选绑定，再冻结 TC 并固定绑定哈希。需求或契约变化会使它 stale，不能继续以旧测试集宣称通过。
 - `tdd_required` 任务必须先由 Core 记录准备快照，再记录 RED（命中预期失败）、同一目标的 GREEN 和回归；缺失或环境失败不算完成。
 - API、跨数据域、边界、迁移、工作负载与架构风险会派生相应的 `api`、`permission`、`boundary`、`migration`、`performance`、`resilience` TC 义务。
 - 代码完成后，`workflow-run-acceptance-tests` 只能运行绑定到冻结 TC、且已在初始化 `.planning/toolchain.md` 发现的测试运行器命令。任何失败、未执行、人工待执行或环境阻塞用例都会阻止 CP-4。
+- 验收不是代码完成后的临时手工检查。它是需求基线在编码前派生并冻结的完整测试集，覆盖主流程、异常、边界、权限、迁移、兼容、韧性和工作负载义务；代码只能补充执行适配信息，不能改变测试意图。
+- 验收失败不会创建另一套人工台账，而是进入 `acceptance-remediation`：诊断 → 修复 → code-index 刷新 → 原冻结 `TC-*` 重跑。
+- CP-4 通过后只进入一个 `workflow-release-closeout` 步骤，统一写入 `.planning/milestones/current-CLOSEOUT.md` 并更新项目状态、导航和版本记录。
 
 正常使用不需要记忆底层命令：在 Devflow 工作流中按步骤继续即可。需要排查时，可用 `devflow_acceptance_tests` 查看冻结套件，或由工作流调用 `devflow_tdd_evidence` 与 `devflow_run_acceptance_tests` 生成 Core-owned 证据；不要手写“已测试”来替代结果文件。
 
-## Marketplace 能力包
+## 更新
 
-仓库也可作为 OMP marketplace 使用，但 Marketplace 安装只用于发现和安装 Skills、Agents、命令等能力内容，不代表完整 Devflow Runtime 已启用。OMP 不会从 Marketplace 安装加载 `package.json` 中的 `omp.extensions`，因此下面的命令不能替代 `bash .skills/install.sh --apply`：
+升级 npm 发行版：
 
 ```bash
-omp plugin marketplace add https://gitee.com/guanlin4924/skill-kit.git
-omp plugin install --scope project devflow-core@devflow
-omp plugin install --scope project devflow-intel@devflow
-omp plugin install --scope project devflow-requirements@devflow
-omp plugin install --scope project devflow-design@devflow
-omp plugin install --scope project devflow-implementation@devflow
-omp plugin install --scope project devflow-quality@devflow
+npm install -g @guanlin4924/devflow-pi@latest
 ```
 
-完整研发流程仍必须在项目固定版本模式下运行安装器。安装或升级 Extension 后重启会话；仅刷新 Skill/Command 时可使用 `/reload-plugins`。
+安装或升级 Extension 后重启会话；仅刷新 Skill/Command 时可使用 `/reload-plugins`。
 
 ## 插件边界
 
@@ -163,7 +173,7 @@ omp plugin install --scope project devflow-quality@devflow
 | `devflow-requirements` | 需求决策 | 分诊、探索、领域建模、可行性、需求基线、对抗审查 |
 | `devflow-design` | 契约设计 | API/UI/前后端方案、功能拆解、集成一致性 |
 | `devflow-implementation` | 代码变更 | 变更计划、隔离执行、Bug 修复 |
-| `devflow-quality` | 独立验证 | 代码审查、主流程用例、UAT、里程碑审计与归档 |
+| `devflow-quality` | 质量与收口 | 代码审查、主流程适配、冻结 TC 执行、失败修复编排与版本收口 |
 
 每个 skill 恰好归属一个插件，插件目录中的实体文件是唯一真本；仓库根目录的同名入口只是兼容现有脚本和人工浏览的相对链接。marketplace 因而可以独立缓存单个插件，而不会留下指向缓存外部的断链。
 
@@ -175,12 +185,10 @@ omp plugin install --scope project devflow-quality@devflow
 - 人工 checkpoint 不得在 headless 模式静默通过。
 - semantic correctness 不能靠 prompt 保证，必须由契约、确定性校验、独立审查和可复现测试共同约束。
 
-## 更新
+源码兼容模式刷新：
 
 ```bash
-git -C .skills pull
 bash .skills/install.sh --refresh
-git add .skills .omp .agent-gates
 ```
 
 刷新完成后重启 OMP 并再次运行 `/devflow doctor`。如果模板新增了强制配置而项目配置被保留，安装器会拒绝完成；审查后使用 `--force-config` 更新。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@guanlin4924/devflow-pi",
-  "version": "0.1.21",
+  "version": "0.1.23",
   "type": "module",
   "description": "Devflow 专项研发 Pi，基于固定版本 OMP Runtime 组装研发状态机、代码智能、设计、实现与质量门禁。",
   "license": "UNLICENSED",
@@ -32,7 +32,6 @@
     "!plugins/**/*.pyc",
     "!plugins/**/tests",
     "templates",
-    "docs",
     "README.md"
   ],
   "publishConfig": {

package/plugins/devflow-core/extensions/devflow-core.ts

@@ -362,12 +362,10 @@ const REQUIRED_SKILLS = [
   "workflow-api-contract",
   "workflow-api-supplement",
   "workflow-acceptance-test-design",
-  "workflow-audit-milestone",
   "workflow-backend-tech-spec",
   "workflow-bug-fix",
   "workflow-change-plan",
   "workflow-code-index",
-  "workflow-complete-milestone",
   "workflow-context-sync",
   "workflow-demand-clarify",
   "workflow-design-rule-pack",
@@ -381,11 +379,11 @@ const REQUIRED_SKILLS = [
   "workflow-pipeline",
   "workflow-project-context",
   "workflow-run-acceptance-tests",
+  "workflow-release-closeout",
   "workflow-requirement-baseline",
   "workflow-requirement-triage",
   "workflow-ui-spec",
   "workflow-update-navigation",
-  "workflow-verify-work",
   "workflow-wayfinder",
 ];
 

package/plugins/devflow-core/skills/workflow-orchestrator/scripts/init_workflow.rb

@@ -58,7 +58,7 @@ end
 
 targets = {
   "feature-development.yaml" => ".planning/workflows/feature-development.yaml",
-  "uat-remediation.yaml" => ".planning/workflows/uat-remediation.yaml",
+  "acceptance-remediation.yaml" => ".planning/workflows/acceptance-remediation.yaml",
   "workflows-README.md" => ".planning/workflows/README.md"
 }
 

package/plugins/devflow-core/skills/workflow-orchestrator/scripts/validate_state.rb

@@ -79,7 +79,7 @@ module WorkflowStateValidator
     validate_waiting_checkpoint(issues, root, state, step_by_id, artifact_by_path, strict_artifact_status)
     validate_current_in_progress_output_drift(issues, root, state, step_by_id, artifact_by_path)
     graph_gate = workflow.dig("governance", "requirement_graph_gate").to_s
-    governed_steps = %w[requirement-baseline api-contract architecture-feasibility integration-verify change-plan execute verify]
+    governed_steps = %w[requirement-baseline api-contract architecture-feasibility integration-verify change-plan execute run-acceptance-tests]
     # A historical completed state is never rolled back solely because it has
     # no v2 graph/evidence. Its first new governed step, however, must satisfy
     # the new contract before it can advance.
@@ -695,18 +695,17 @@ module WorkflowStateValidator
   end
 
   def validate_verification_gate(issues, step, data)
-    return unless step["id"] == "verify"
+    return unless step["id"] == "run-acceptance-tests"
 
-    if data["uat_failed"].to_i.positive?
-      issues << issue("error", "verification_uat_failed", "Verification meta reports failed UAT items", step: step["id"], count: data["uat_failed"])
+    failed = data["acceptance_tc_failed"].to_i
+    blocked = data["acceptance_tc_blocked"].to_i
+    if failed.positive? || blocked.positive?
+      issues << issue("error", "acceptance_tests_not_passed", "Frozen acceptance tests contain failed or blocked cases", step: step["id"], failed: failed, blocked: blocked)
     end
 
-    gate_passed = data["gate_passed"].to_i
-    gate_total = data["gate_total"].to_i
-    if gate_total.zero?
-      issues << issue("error", "verification_gate_total_zero", "Verification meta gate_total must be greater than zero", step: step["id"])
-    elsif gate_passed != gate_total
-      issues << issue("error", "verification_gates_not_all_passed", "Verification meta reports incomplete gates", step: step["id"], gate_passed: gate_passed, gate_total: gate_total)
+    passed = data["acceptance_tc_passed"].to_i
+    if passed.zero?
+      issues << issue("error", "acceptance_tests_empty", "Acceptance result must contain at least one passed TC", step: step["id"])
     end
   end
 

package/plugins/devflow-core/skills/workflow-orchestrator/templates/acceptance-remediation.yaml

@@ -0,0 +1,87 @@
+schema_version: 1
+id: acceptance-remediation
+name: Acceptance Failure Remediation
+description: >
+  修复冻结需求验收测试失败或阻塞的问题，刷新 code_index 后重新执行同一套 TC-*。
+
+entry:
+  from_flow: feature-development
+  from_step: run-acceptance-tests
+  initial_step: diagnose
+
+state_contract:
+  source: ".planning/STATE.md"
+  suggested_transition:
+    current_flow: acceptance-remediation
+    current_step: diagnose
+    status: in_progress
+    completed_steps: []
+    pending_steps:
+      - diagnose
+      - execute-fix
+      - code-index-refresh
+      - run-acceptance-tests
+
+variables:
+  feature:
+    source: state.current_feature
+  phase:
+    source: state.current_phase
+
+steps:
+  - id: diagnose
+    order: 10
+    label: Diagnose acceptance failure
+    skill: workflow-bug-fix
+    depends_on: []
+    inputs:
+      - ".planning/test-runs/{feature}/acceptance-results.json"
+      - ".planning/features/{feature}/acceptance-test-bindings.json"
+    outputs:
+      - path: ".planning/features/{feature}/acceptance-remediation.md"
+        type: acceptance-remediation
+        required: true
+
+  - id: execute-fix
+    order: 20
+    label: Execute fix
+    skill: workflow-execute-phase
+    depends_on:
+      - diagnose
+    inputs:
+      - ".planning/features/{feature}/acceptance-remediation.md"
+      - ".planning/features/{feature}/变更清单.md"
+
+  - id: code-index-refresh
+    order: 30
+    label: Refresh code index
+    skill: workflow-code-index
+    depends_on:
+      - execute-fix
+    inputs:
+      - ".planning/features/{feature}/acceptance-remediation.md"
+    outputs:
+      - path: ".planning/code-index/AUDIT.md"
+        type: code-index-audit
+        required: true
+
+  - id: run-acceptance-tests
+    order: 40
+    label: Re-run frozen acceptance tests
+    skill: workflow-run-acceptance-tests
+    depends_on:
+      - code-index-refresh
+    inputs:
+      - ".planning/requirements/{feature}/tests.json"
+      - ".planning/features/{feature}/acceptance-test-bindings.json"
+      - ".planning/code-index/AUDIT.md"
+    outputs:
+      - path: ".planning/test-runs/{feature}/acceptance-results.json"
+        type: acceptance-test-results
+        required: true
+
+return_to:
+  flow: feature-development
+  step: run-acceptance-tests
+  status: waiting_checkpoint
+  checkpoint: CP-4

package/plugins/devflow-core/skills/workflow-orchestrator/templates/feature-development.yaml

@@ -67,7 +67,7 @@ governance:
       - test-coverage-check
       - acceptance-test-results-check
       - change-impact-check
-    verify:
+    run-acceptance-tests:
       - acceptance-coverage-check
       - acceptance-test-results-check
       - change-impact-check
@@ -132,11 +132,11 @@ parallel_windows:
         - ".planning/features/{feature}/前端技术方案.md"
 
 failure_branches:
-  verify:
-    id: verify-failed-remediation
-    label: Verify failure remediation
-    workflow: uat-remediation
-    workflow_config: ".planning/workflows/uat-remediation.yaml"
+  run-acceptance-tests:
+    id: acceptance-failed-remediation
+    label: Acceptance failure remediation
+    workflow: acceptance-remediation
+    workflow_config: ".planning/workflows/acceptance-remediation.yaml"
     trigger_conditions:
       state_statuses:
         - failed
@@ -147,7 +147,7 @@ failure_branches:
         - failed
     resume_after_success:
       flow: feature-development
-      step: verify
+      step: run-acceptance-tests
       status: waiting_checkpoint
       checkpoint: CP-4
 
@@ -306,28 +306,23 @@ checkpoints:
     skip_policy: never
     resume_behavior: "user confirms, then continue with phase-structure"
   CP-4:
-    name: Acceptance confirmation
-    gate_after: verify
-    producing_step: verify
+    name: Acceptance result confirmation
+    gate_after: run-acceptance-tests
+    producing_step: run-acceptance-tests
     required_outputs:
-      - ".planning/phases/{phase}/01-UAT.md"
-      - ".planning/phases/{phase}/01-VERIFICATION.md"
-    required_meta_output: ".planning/phases/{phase}/01-VERIFICATION.meta.json"
+      - ".planning/test-runs/{feature}/acceptance-results.json"
     required_meta_fields:
-      - uat_passed
-      - uat_failed
-      - uat_skipped
-      - gate_passed
-      - gate_total
-      - known_issues
+      - acceptance_tc_passed
+      - acceptance_tc_failed
+      - acceptance_tc_blocked
+      - acceptance_suite_graph_revision
+      - acceptance_results_fingerprint
     summary_fields:
-      - uat_passed
-      - uat_failed
-      - uat_skipped
-      - gate_passed
-      - gate_total
-      - known_issues
-    prompt: "确认 UAT、主流程、规则、兼容性和工具链验证已通过，并允许进入审计归档。"
+      - acceptance_tc_passed
+      - acceptance_tc_failed
+      - acceptance_tc_blocked
+      - acceptance_results_fingerprint
+    prompt: "确认冻结的 TC-* 已全部执行并通过，允许进入版本收口与里程碑归档。"
     confirm_options:
       - approve
       - needs_fix
@@ -907,84 +902,20 @@ steps:
         type: acceptance-test-results
         required: true
 
-  - id: verify
-    order: 90
-    label: Verify
-    skill: workflow-verify-work
+  - id: release-closeout
+    order: 100
+    label: Release closeout and milestone archive
+    skill: workflow-release-closeout
     depends_on:
-      - code-review
-      - generate-mainflow-cases
       - run-acceptance-tests
     inputs:
-      - ".planning/features/{feature}/PROGRESS.md"
-      - ".planning/phases/{phase}/SUMMARY.md"
-      - ".planning/phases/{phase}/MAINFLOW-CASES.md"
-      - ".planning/generated-cases/{feature}/validation-report.md"
-      - ".planning/generated-cases/{feature}/case-import-payloads.json"
       - ".planning/test-runs/{feature}/acceptance-results.json"
-    outputs:
-      - path: ".planning/phases/{phase}/01-UAT.md"
-        type: uat-report
-        required: true
-      - path: ".planning/phases/{phase}/01-VERIFICATION.md"
-        type: verification-report
-        required: true
-    meta_output:
-      path: ".planning/phases/{phase}/01-VERIFICATION.meta.json"
-      fields:
-        uat_passed: { type: integer, required: true }
-        uat_failed: { type: integer, required: true }
-        uat_skipped: { type: integer, required: true }
-        gate_passed: { type: integer, required: true }
-        gate_total: { type: integer, required: true }
-        acceptance_tc_passed: { type: integer, required: true }
-        acceptance_tc_failed: { type: integer, required: true }
-        acceptance_tc_blocked: { type: integer, required: true }
-        acceptance_suite_graph_revision: { type: integer, required: true }
-        acceptance_results_fingerprint: { type: string, required: true }
-        known_issues: { type: array, required: true }
-    checkpoint: CP-4
-
-  - id: audit
-    order: 100
-    label: Audit
-    skill: workflow-audit-milestone
-    depends_on:
-      - verify
-    inputs:
-      - ".planning/phases/{phase}/01-UAT.md"
-      - ".planning/phases/{phase}/01-VERIFICATION.md"
-      - ".planning/features/{feature}/PROGRESS.md"
-    outputs:
-      - path: ".planning/milestone-audit.md"
-        type: milestone-audit
-        required: true
-
-  - id: update-navigation
-    order: 110
-    label: Update navigation
-    skill: workflow-update-navigation
-    depends_on:
-      - audit
-    inputs:
-      - "."
-    outputs:
-      - path: ".planning/navigation/INDEX.md"
-        type: navigation-index
-        required: true
-
-  - id: archive
-    order: 120
-    label: Archive
-    skill: workflow-complete-milestone
-    depends_on:
-      - update-navigation
-    inputs:
-      - ".planning/milestone-audit.md"
+      - ".planning/code-index/AUDIT.md"
+      - ".planning/features/{feature}/变更清单.md"
       - ".planning/navigation/INDEX.md"
     outputs:
-      - path: ".planning/milestones/current-MILESTONE.md"
-        type: milestone-archive
+      - path: ".planning/milestones/current-CLOSEOUT.md"
+        type: release-closeout
         required: true
 
 resume_rules:

package/plugins/devflow-core/skills/workflow-pipeline/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow-pipeline
-description: Use when running or resuming the full .planning delivery pipeline from requirements through implementation, verification, audit, and milestone archive.
+description: Use when running or resuming the full .planning delivery pipeline from requirements through implementation, frozen acceptance tests, and Devflow release closeout.
 ---
 
 <objective>
@@ -42,10 +42,8 @@ pipeline 本身不包含执行规则——所有门禁、CP 协议、失败分
 | 84 | code-index-refresh | 刷新机器代码索引并审查 |
 | 85 | code-review | 代码审查（完成标准验证） |
 | 86 | generate-mainflow-cases | 主流程自动化用例生成 |
-| 90 | verify | UAT 验收 |
-| 100 | audit | 里程碑审计 |
-| 110 | update-navigation | 更新导航 |
-| 120 | archive | 里程碑归档 |
+| 90 | run-acceptance-tests | 冻结 TC 验收执行 |
+| 100 | release-closeout | 验收通过后的版本收口与里程碑归档 |
 
 - **`--track A`**：后端/API 轨道产物模式。可跑 `requirement-triage → requirement-wayfinder → domain-modeling → requirement-feasibility-review → requirement-baseline → api-contract → architecture-feasibility → backend-tech-spec → api-call-guide`，但不能自动进入 `integration-verify / change-plan / execute`。
 - **`--track B`**：前端/UI 轨道产物模式。要求 `api-contract` 与 `architecture-feasibility` 已完成；新需求从需求主链开始，已有共同事实可跑 `ui-spec → feature-breakdown → frontend-tech-spec`，但不能自动进入 `change-plan / execute`。

package/plugins/devflow-core/skills/workflow-pipeline/references/pipeline-flow.md

@@ -102,38 +102,25 @@ workflow-pipeline 启动
 	         │             ↑
 	         ▼             │ 审查失败/用例生成失败
 ┌─────────────────────────────────────┐
-│ Step 6: UAT 验证                     │
-│ workflow-verify-work                 │
-│ 按功能点逐条验证                     │
-│ 失败 → 诊断 → 修复 → 回 Step 5       │
+│ Step 6: 需求验收测试执行              │
+│ workflow-run-acceptance-tests         │
+│ 执行冻结的 TC-*                       │
+│ 失败/阻塞 → 修复 → 重跑                │
 └──────────────┬──────────────────────┘
 	         │             ↑
 	         ▼             │ 用户拒绝
 ┌─────────────────────────────────────┐
-│ 🔴 CP-4: 验收人工确认                 │
+│ 🔴 CP-4: 验收结果确认                 │
 │ ask 强制暂停              │
 │ 不可跳过                              │
-│ 确认: UAT/5门gate通过,可归档         │
+│ 确认: TC-* 全部通过,允许版本收口       │
 └──────────────┬──────────────────────┘
          │ 用户确认
          ▼
 ┌─────────────────────────────────────┐
-│ Step 7: 里程碑审计                   │
-│ workflow-audit-milestone             │
-│ gaps → Bug 修复或人工拆分后重审       │
-└──────────────┬──────────────────────┘
-         │             ↑
-         ▼             │ 补齐后重试
-┌─────────────────────────────────────┐
-│ Step 7.5: 更新导航                   │
-│ workflow-update-navigation           │
-│ 增量同步 navigation 到代码结构       │
-└──────────────┬──────────────────────┘
-         ▼
-┌─────────────────────────────────────┐
-│ Step 8: 里程碑归档                   │
-│ workflow-complete-milestone              │
-│ 归档 → 更新 PROJECT.md → git tag    │
+│ Step 7: 版本收口与里程碑归档          │
+│ workflow-release-closeout             │
+│ 校验 TC/code-index → 归档 → 更新状态   │
 └─────────────────────────────────────┘
          │
          ▼

package/plugins/devflow-core/skills/workflow-pipeline/references/slice-safety-guide.md

@@ -53,7 +53,7 @@ Write this table into the baseline and carry `SL-*` IDs downstream:
 
 | Slice ID | Name | Outcome | Included FP/BR/BC | Depends on | Entry/chain | Excluded/deferred | Gate |
 |----------|------|---------|-------------------|------------|-------------|-------------------|------|
-| SL-001 | Core path | User can complete X | FP-001, BR-001, BC-001 | none | page -> API -> table -> list | reporting | UAT path |
+| SL-001 | Core path | User can complete X | FP-001, BR-001, BC-001 | none | page -> API -> table -> list | reporting | TC acceptance path |
 
 Rules:
 

package/plugins/devflow-implementation/skills/workflow-change-plan/references/output-template.md

@@ -164,8 +164,8 @@ Redis / MQ 等变更（如有）。
 | 阶段 | 负责 | 不负责 |
 |------|------|--------|
 | workflow-change-plan | 规划任务级测试策略、范围、规划级命令、跳过自动化测试分级 | 不执行测试 |
-| workflow-execute-phase | 新增/更新任务级单元、集成、组件、API、迁移验证；补充执行级命令并运行 | 不替代 UAT、全局回归、跨模块验收 |
-| workflow-verify-work | UAT、全局工具链、E2E/浏览器验证、兼容性、回归、需求覆盖 | 不重新设计每个任务的单元/集成策略 |
+| workflow-execute-phase | 新增/更新任务级单元、集成、组件、API、迁移验证；补充执行级命令并运行 | 不替代冻结 TC 的需求验收执行 |
+| workflow-run-acceptance-tests | 执行冻结 TC、全局工具链、E2E/浏览器验证、兼容性、回归、需求覆盖 | 不重新设计每个任务的单元/集成策略 |
 
 ### 5.2 任务测试策略矩阵