create-yss-spec 2.1.8 → 2.1.10

package/template/docs/process/harness-process-tailoring.md

@@ -15,7 +15,7 @@
 
 | 类型 | 默认入口 | 必需工作 | 可记录为 `not-applicable` |
 |---|---|---|---|
-| 模板源维护 | 影响面分析 | 修改单一事实来源、技能投影同步、压力场景、fresh verification、独立审查 | 产品 Spec、产品设计、OpenAPI、运行时代码 |
+| 模板源维护 | 影响面分析 | 修改单一事实来源、按验证与审查强度分级执行证据、必要的技能投影同步、fresh verification / review | 产品 Spec、产品设计、OpenAPI、运行时代码 |
 | 小改动 | 入口分诊 | 影响面、主 tracker 同步、fresh verification | Spec、架构、原型、切片（没有触发条件时） |
 | 中等变更 | 最近可信的 Spec / 架构阶段 | Spec、功能架构、必要工程审查、父 Ticket 和切片 | 未命中的 UI、数据或 API 门禁 |
 | 全新产品 / 模块 | Discovery | Discovery、Spec、产品总体设计、功能架构、必要设计 / 契约审查、父 Ticket 和切片 | 未命中的 UI、数据或 API 门禁 |
@@ -26,3 +26,39 @@
 ## 3. 执行与证据
 
 同一独立执行者可以在一个连续工作单元内完成相邻的实现动作，但不能替代独立审查者。阶段证据在集中 checkpoint 回写，至少包含：范围、变更文件、受影响仓库、验证命令及结果、阻塞项、人工审查点、Ticket 状态和下一步。
+
+## 4. 模板维护验证与审查强度分级
+
+本节只适用于 `template-source` 的模板、流程规则和共享 skill 维护，不降低 `project-instance` 的 Spec、OpenAPI Freeze、垂直切片或高风险工程门禁。强度由错误逃逸损失和是否改变 Agent 行为决定，不由文件所在目录单独决定。
+
+| 强度 | 权威触发项 | 最低验证证据 | Review |
+|---|---|---|---|
+| L1 | `maintenance-intensity.yaml` 的 `levels.L1.triggers` | 至少一项与变更直接相关的实际检查 | `self-check` 或显式 `human-checkpoint` |
+| L2 | `maintenance-intensity.yaml` 的 `levels.L2.triggers`，或该策略的 `default_level` | 修改前可失败的最小反例，以及本轮 fresh verification | 一名非实施者执行 `focused-independent` 聚焦审查；结论可内联 checkpoint |
+| L3 | `maintenance-intensity.yaml` 的 `levels.L3.triggers` | 完整 RED、GREEN、REFACTOR、压力场景与本轮 fresh verification | 冻结候选后执行 `formal-independent` 正式独立审查；需要时使用完整 `code-review` |
+
+判定规则：
+
+1. 等级只由 `maintenance-intensity.yaml` 计算；未给出 trigger 时使用该策略的 `default_level`，未知 trigger 必须更新策略后才可验证。
+2. 实施者可先分级，不要求 L1/L2 预批准；发现新影响时立即更新 `escalation`、重新分级并补齐证据。
+3. 发布、合并或阶段完成时按整体候选重新判定；不得把共同改变整体语义的修改拆成多个 L1/L2 规避 L3。
+4. RED 用于证明行为差异。L1 不人为构造失败；L2 可使用已有失败、最小 fixture 或现有测试修改前失败；只有行为无法确定性表达时才运行聚焦压力场景。L3 使用 `maintaining-skills` 并执行本节定义的完整 RED、GREEN、REFACTOR 和压力场景要求。
+5. 模板发布候选固定按 L3 聚合验证，但不追溯补造每个既有 L1/L2 修改的独立 RED。
+
+每个模板维护 checkpoint 使用以下轻量合同；L1/L2 可直接写入主 Ticket 或集中 checkpoint，不要求新增独立文档：
+
+```yaml
+schema_version: 1
+intensity: L1 | L2 | L3
+classification_reason: <分级理由>
+triggers: [<可观察触发项>]
+changed_assets: [<路径或资产引用>]
+verification_evidence:
+  - kind: relevant-check | counterexample | red | green | refactor | pressure-scenario | fresh-verification | focused-independent-review | formal-independent-review
+    command: <本轮实际命令或可读取证据引用>
+    result: pass
+review_mode: self-check | human-checkpoint | focused-independent | formal-independent # L2/L3 还必须在 verification_evidence 中给出对应 review 证据引用
+escalation: none | <升级原因和原等级>
+```
+
+使用 `scripts/verify-maintenance-checkpoint <file>` 或通过 stdin 传入 YAML / JSON 做只读校验。触发项 ID 与最低等级只由 `docs/process/maintenance-intensity.yaml` 维护；校验器消费该策略。未知触发项必须先更新该权威策略和场景，不能静默接受。

package/template/docs/process/lifecycle-artifact-map.md

@@ -24,21 +24,22 @@
 
 ### 2.1 条件门禁
 
-| 稳定 ID | 门禁 | 所属阶段 | 触发条件 | 必须留下的证据 |
-|---|---|---|---|---|
-| `gate.repository-identity-valid` | 仓库身份校验 | `stage.entry-triage` | 每次进入流程。 | `evidence.repository-identity-check` |
-| `gate.spec-baseline-approved` | Spec 基线批准 | `stage.spec-architecture` | 新功能、行为变化或范围扩大进入 Spec 基线。 | `evidence.approval-record` |
-| `gate.prototype-reviewed` | 原型评审 | `stage.product-design` | 命中产品设计影响，且低保真页面、流程、状态或 API 反推需要独立评审。 | `evidence.prototype-review-result` |
-| `gate.prototype-verified` | 高保真原型验证 | `stage.product-design` | 需要高保真 HTML 原型进行视觉与交互校准。 | `evidence.antd-cli-validation`、`evidence.browser-prototype-verification` |
-| `gate.user-confirmation` | 用户确认 | `stage.product-design` | 产品设计影响尚未被人工确认。 | `evidence.prototype-confirmation` |
-| `gate.openapi-draft-reviewed` | OpenAPI Draft Review | `stage.system-data-engineering` | 有 API 影响且 Draft 已生成。 | `evidence.openapi-draft-review` |
-| `gate.design-reviewed` | 设计审查 | `stage.system-data-engineering` | API 或架构影响。 | `evidence.design-review-result` |
-| `gate.openapi-frozen` | OpenAPI Freeze | `stage.system-data-engineering` | API 进入实现。 | `evidence.approval-record` |
-| `gate.engineering-baseline-accepted` | 工程基线 | `stage.system-data-engineering` | 后端、前端或高风险工程变化。 | `evidence.fresh-verification` |
-| `gate.architecture-reviewed` | 架构审查 | `stage.system-data-engineering` | 高风险或跨边界变化。 | `evidence.design-review-result` |
-| `gate.slice-contract-approved` | Slice Implementation Contract 批准 | `stage.ticket-formalization` | Agent 进入实现；脚手架完成后每个后续生成代码工作单元。 | `evidence.contract-approval` |
-| `gate.slice-ready-for-agent` | 垂直切片实现就绪 | `stage.ticket-formalization` | 垂直切片具备直接实现条件。 | `evidence.contract-approval`、`evidence.approval-record` |
-| `gate.release-ready` | 发布就绪 | `stage.verification-release-retrospective` | 合并、发布或阶段完成。 | `evidence.fresh-verification`、`evidence.checkpoint-and-rollback` |
+| 稳定 ID | 门禁 | 所属阶段 | 触发条件 | 前置门禁 | 必须留下的证据 |
+|---|---|---|---|---|---|
+| `gate.repository-identity-valid` | 仓库身份校验 | `stage.entry-triage` | 每次进入流程。 | 无 | `evidence.repository-identity-check` |
+| `gate.spec-baseline-approved` | Spec 基线批准 | `stage.spec-architecture` | 新功能、行为变化或范围扩大进入 Spec 基线。 | 无 | `evidence.approval-record` |
+| `gate.prototype-reviewed` | 原型评审 | `stage.product-design` | 命中产品设计影响，且低保真页面、流程、状态或 API 反推需要独立评审。 | 无 | `evidence.prototype-review-result` |
+| `gate.prototype-verified` | 高保真原型验证 | `stage.product-design` | 需要高保真 HTML 原型进行视觉与交互校准。 | 无 | `evidence.antd-cli-validation`、`evidence.browser-prototype-verification` |
+| `gate.user-confirmation` | 用户确认 | `stage.product-design` | 产品设计影响尚未被人工确认。 | 无 | `evidence.prototype-confirmation` |
+| `gate.openapi-draft-reviewed` | OpenAPI Draft Review | `stage.system-data-engineering` | 有 API 影响且 Draft 已生成。 | 无 | `evidence.openapi-draft-review` |
+| `gate.design-reviewed` | 设计审查 | `stage.system-data-engineering` | API 或架构影响。 | 无 | `evidence.design-review-result` |
+| `gate.openapi-frozen` | OpenAPI Freeze | `stage.system-data-engineering` | API 进入实现。 | 无 | `evidence.approval-record` |
+| `gate.engineering-baseline-accepted` | 工程基线 | `stage.system-data-engineering` | 后端、前端或高风险工程变化。 | 无 | `evidence.fresh-verification` |
+| `gate.architecture-reviewed` | 架构审查 | `stage.system-data-engineering` | 高风险或跨边界变化。 | 无 | `evidence.design-review-result` |
+| `gate.slice-contract-approved` | Slice Implementation Contract 批准 | `stage.ticket-formalization` | Agent 进入实现；脚手架完成后每个后续生成代码工作单元。 | 无 | `evidence.contract-approval` |
+| `gate.slice-ready-for-agent` | 垂直切片实现就绪 | `stage.ticket-formalization` | 垂直切片具备直接实现条件。 | 无 | `evidence.contract-approval`、`evidence.approval-record` |
+| `gate.frontend-implementation-verified` | 前端实现还原验证 | `stage.verification-release-retrospective` | UI 影响切片完成实现并准备合并、发布或阶段完成。 | 无 | `evidence.frontend-implementation-verification` |
+| `gate.release-ready` | 发布就绪 | `stage.verification-release-retrospective` | 合并、发布或阶段完成。 | `gate.frontend-implementation-verified` | `evidence.fresh-verification`、`evidence.checkpoint-and-rollback` |
 
 ### 2.2 生命周期产物
 
@@ -64,6 +65,8 @@
 | `artifact.parent-ticket` | 功能父 Ticket | `stage.ticket-formalization` | 每个进入追踪的功能。 |
 | `artifact.vertical-slice-ticket` | 垂直切片 Ticket | `stage.ticket-formalization` | 进入实现前。 |
 | `artifact.slice-implementation-contract` | Slice Implementation Contract | `stage.ticket-formalization` | Agent 进入实现。 |
+| `artifact.frontend-implementation-plan` | 前端实现还原计划 | `stage.ticket-formalization` | UI 影响切片提升 ready-for-agent 前。 |
+| `artifact.frontend-implementation-verification` | 前端实现还原验证记录 | `stage.verification-release-retrospective` | UI 影响切片完成实现并准备合并、发布或阶段完成。 |
 | `artifact.retrospective` | 复盘记录 | `stage.verification-release-retrospective` | 发布后或阶段性完成后满足复盘触发条件。 |
 
 ### 2.3 执行证据
@@ -71,6 +74,7 @@
 | 稳定 ID | 证据 | 说明 |
 |---|---|---|
 | `evidence.impact-assessment` | 影响面分析记录 | 受影响仓库、资产、风险与最近可信阶段。 |
+| `evidence.maintenance-intensity-checkpoint` | 模板维护强度 checkpoint | template-source 变更的 L1 / L2 / L3 分级、触发项、最低验证证据、review 模式和升级记录。 |
 | `evidence.repository-identity-check` | 仓库身份校验结果 | yss-project.yaml 的合法性与 repository_mode 裁决。 |
 | `evidence.approval-record` | 人工批准记录 | 对需要人工批准的 Spec、设计、契约或发布裁决的可追溯记录。 |
 | `evidence.design-review-result` | 设计审查结果 | API、架构或产品设计审查意见及处理结果。 |
@@ -81,6 +85,7 @@
 | `evidence.openapi-draft-review` | OpenAPI Draft 审查记录 | P0、错误、分页、幂等和契约测试审查记录。 |
 | `evidence.contract-approval` | Slice 合同批准记录 | 生命周期编排器批准且已持久化的当前版本合同引用。 |
 | `evidence.yss-skill-execution-result` | YSS Skill Execution Result | 专项 skill 的合同版本、写入、验证、延期 seam 与偏离证据。 |
+| `evidence.frontend-implementation-verification` | 前端实现还原验证证据 | UI 实现相对冻结原型和 Spec 的桌面/窄屏视觉、状态、交互、控制台与 pnpm 验证记录。 |
 | `evidence.fresh-verification` | Fresh Verification 记录 | 本轮实际执行的验证命令、结果和时间。 |
 | `evidence.checkpoint-and-rollback` | Checkpoint 与回滚点 | 可追溯的变更边界、发布记录和恢复动作。 |
 <!-- lifecycle-registry:structure:end -->

package/template/docs/process/lifecycle-registry-baseline.json

@@ -1,12 +1,14 @@
 {
   "schema_version": 1,
   "registry_id": "yss.lifecycle",
-  "semantic_sha256": "6261529654dba3e3738aa950e42d6af5b5db1b3be4ac6c2e4dc86a395c49ec6f",
+  "semantic_sha256": "6c7251b7929c696d41e04218c927a0679d61bd38c7af0c21cde96ecdc2f7107f",
   "published_ids": [
     "artifact.architecture-review",
     "artifact.data-architecture",
     "artifact.discovery-record",
     "artifact.engineering-baseline",
+    "artifact.frontend-implementation-plan",
+    "artifact.frontend-implementation-verification",
     "artifact.functional-architecture",
     "artifact.high-fidelity-html-prototype",
     "artifact.impact-assessment",
@@ -31,7 +33,9 @@
     "evidence.contract-approval",
     "evidence.design-review-result",
     "evidence.fresh-verification",
+    "evidence.frontend-implementation-verification",
     "evidence.impact-assessment",
+    "evidence.maintenance-intensity-checkpoint",
     "evidence.openapi-draft-review",
     "evidence.prototype-confirmation",
     "evidence.prototype-review-result",
@@ -40,6 +44,7 @@
     "gate.architecture-reviewed",
     "gate.design-reviewed",
     "gate.engineering-baseline-accepted",
+    "gate.frontend-implementation-verified",
     "gate.openapi-draft-reviewed",
     "gate.openapi-frozen",
     "gate.prototype-reviewed",
@@ -59,12 +64,24 @@
     "stage.verification-release-retrospective",
     "stage.vertical-slice-implementation",
     "work-unit.attach-sync-integration",
+    "work-unit.code-review",
+    "work-unit.discovery-opportunity",
+    "work-unit.discovery-requirements",
     "work-unit.entry-triage",
     "work-unit.fresh-verification",
     "work-unit.independent-review",
+    "work-unit.intensity-aware-review",
+    "work-unit.intensity-aware-verification",
+    "work-unit.frontend-implementation-verification",
+    "work-unit.prototype-design",
+    "work-unit.release-and-retrospective",
     "work-unit.release-and-rollback",
     "work-unit.skill-projection-sync",
+    "work-unit.slice-implementation",
+    "work-unit.spec-synthesis",
     "work-unit.ssot-update",
+    "work-unit.technical-analysis",
+    "work-unit.ticket-decomposition",
     "work-unit.template-snapshot-build"
   ]
 }

package/template/docs/process/lifecycle-registry.yaml

@@ -8,7 +8,7 @@ id_policy:
   pattern: '^(stage|gate|artifact|work-unit|evidence)\.[a-z0-9][a-z0-9-]*$'
   published_ids_immutable: true
   baseline: docs/process/lifecycle-registry-baseline.json
-  deprecated_ids: []
+  deprecated_ids: [work-unit.fresh-verification, work-unit.independent-review]
 
 stages:
   - id: stage.entry-triage
@@ -48,6 +48,9 @@ evidence:
   - id: evidence.impact-assessment
     name: 影响面分析记录
     description: 受影响仓库、资产、风险与最近可信阶段。
+  - id: evidence.maintenance-intensity-checkpoint
+    name: 模板维护强度 checkpoint
+    description: template-source 变更的 L1 / L2 / L3 分级、触发项、最低验证证据、review 模式和升级记录。
   - id: evidence.repository-identity-check
     name: 仓库身份校验结果
     description: yss-project.yaml 的合法性与 repository_mode 裁决。
@@ -78,6 +81,9 @@ evidence:
   - id: evidence.yss-skill-execution-result
     name: YSS Skill Execution Result
     description: 专项 skill 的合同版本、写入、验证、延期 seam 与偏离证据。
+  - id: evidence.frontend-implementation-verification
+    name: 前端实现还原验证证据
+    description: UI 实现相对冻结原型和 Spec 的桌面/窄屏视觉、状态、交互、控制台与 pnpm 验证记录。
   - id: evidence.fresh-verification
     name: Fresh Verification 记录
     description: 本轮实际执行的验证命令、结果和时间。
@@ -146,11 +152,17 @@ gates:
     stage: stage.ticket-formalization
     trigger: 垂直切片具备直接实现条件。
     evidence: [evidence.contract-approval, evidence.approval-record]
+  - id: gate.frontend-implementation-verified
+    name: 前端实现还原验证
+    stage: stage.verification-release-retrospective
+    trigger: UI 影响切片完成实现并准备合并、发布或阶段完成。
+    evidence: [evidence.frontend-implementation-verification]
   - id: gate.release-ready
     name: 发布就绪
     stage: stage.verification-release-retrospective
     trigger: 合并、发布或阶段完成。
     evidence: [evidence.fresh-verification, evidence.checkpoint-and-rollback]
+    requires_gates: [gate.frontend-implementation-verified]
 
 artifacts:
   - id: artifact.impact-assessment
@@ -233,6 +245,14 @@ artifacts:
     name: Slice Implementation Contract
     stage: stage.ticket-formalization
     trigger: Agent 进入实现。
+  - id: artifact.frontend-implementation-plan
+    name: 前端实现还原计划
+    stage: stage.ticket-formalization
+    trigger: UI 影响切片提升 ready-for-agent 前。
+  - id: artifact.frontend-implementation-verification
+    name: 前端实现还原验证记录
+    stage: stage.verification-release-retrospective
+    trigger: UI 影响切片完成实现并准备合并、发布或阶段完成。
   - id: artifact.retrospective
     name: 复盘记录
     stage: stage.verification-release-retrospective
@@ -269,21 +289,81 @@ work_units:
     input: 目标仓库、dry-run 计划。
     output: 受管资产和 metadata。
     completion: 验证通过或完整回滚。
-  - id: work-unit.fresh-verification
-    name: Fresh verification
+  - id: work-unit.intensity-aware-verification
+    name: 分级 Fresh verification
     scope: template-source
-    input: 变更仓库。
+    input: 变更仓库、强度分级与对应最低证据。
     output: 命令输出与证据。
-    completion: 所有命中门禁通过。
-  - id: work-unit.independent-review
-    name: 独立审查
+    completion: L1 相关检查、L2 最小反例与 fresh verification、L3 完整 RED / GREEN / REFACTOR 与 fresh verification 按命中等级通过。
+  - id: work-unit.intensity-aware-review
+    name: 分级审查
     scope: template-source
-    input: 变更 diff、验证证据。
-    output: review 结论。
-    completion: 无未处理阻断项。
+    input: 变更 diff、强度分级与验证证据。
+    output: L1 self-check / 人工 checkpoint、L2 聚焦独立审查或 L3 正式独立审查结论。
+    completion: 已按命中等级完成审查且无未处理阻断项；L1 不强制独立 reviewer。
   - id: work-unit.release-and-rollback
     name: 发布与回滚
     scope: template-source
     input: 已审查 commit。
     output: release note、观察信号、回滚点。
     completion: 两仓库顺序和恢复动作明确。
+  - id: work-unit.discovery-opportunity
+    name: 机会调研
+    scope: project-instance
+    input: 用户问题、市场/竞品事实需求和现有上下文。
+    output: Discovery 机会结论、证据、替代方案和关键假设。
+    completion: 机会继续/停止建议可审查；事实已 research 或记录为假设。
+  - id: work-unit.discovery-requirements
+    name: 需求分析
+    scope: project-instance
+    input: 机会结论、用户反馈和领域词汇。
+    output: 用户、MVP、非目标、成功标准、测试 seam 和未决项。
+    completion: frontier 清空；用户确认；无 runnable blocker。
+  - id: work-unit.spec-synthesis
+    name: Spec 综合
+    scope: project-instance
+    input: 已确认的 Discovery 记录和测试 seam。
+    output: Spec、产品总体设计和功能架构。
+    completion: Spec 内容完整并进入 ready-for-human；下游推进仍需 gate.spec-baseline-approved。
+  - id: work-unit.prototype-design
+    name: 原型设计与验证
+    scope: project-instance
+    input: Spec、产品设计影响和状态矩阵。
+    output: 交互说明、低/高保真原型、评审、AntD CLI 和浏览器证据。
+    completion: 原型评审、高保真验证和用户确认门禁均通过。
+  - id: work-unit.technical-analysis
+    name: 技术分析与契约冻结
+    scope: project-instance
+    input: Spec、原型、API/数据/工程影响面。
+    output: OpenAPI、数据架构、工程基线、架构审查和 Slice 合同草案。
+    completion: 命中契约已冻结；无 API 影响有可读记录；工程基线通过。
+  - id: work-unit.ticket-decomposition
+    name: 垂直切片 Ticket 正式化
+    scope: project-instance
+    input: 冻结 Spec、设计、契约和阻塞关系。
+    output: 功能父 Ticket、垂直切片和批准的 Slice Implementation Contract。
+    completion: 切片可独立验证；生命周期复算后才能 ready-for-agent。
+  - id: work-unit.slice-implementation
+    name: 垂直切片实现
+    scope: project-instance
+    input: 当前版本 Slice Implementation Contract 和允许写路径。
+    output: 前后端实现、TDD 和 YSS Skill Execution Result。
+    completion: 行为通过 `behavior-tdd`；UI 影响完成还原验证计划；无 drift/violation。
+  - id: work-unit.frontend-implementation-verification
+    name: 前端实现还原验证
+    scope: project-instance
+    input: 冻结原型、状态矩阵、实现候选和视觉验收用例。
+    output: 桌面/窄屏视觉、状态、交互、console 和 pnpm 验证证据。
+    completion: 关键场景无未解释差异；独立 Reviewer 通过 UI fidelity 轴。
+  - id: work-unit.code-review
+    name: 独立代码审查与验证
+    scope: project-instance
+    input: 不可变候选快照、Spec、Ticket、合同和执行结果。
+    output: Standards、Spec、UI fidelity 三轴 Review 与 fresh verification。
+    completion: findings 已处理；修复后重新捕获候选并全量复审。
+  - id: work-unit.release-and-retrospective
+    name: 发布与复盘
+    scope: project-instance
+    input: 已审查候选、发布窗口和回滚点。
+    output: 发布/回滚证据和复盘记录。
+    completion: 人工发布裁决、fresh verification 和治理回流均完成。

package/template/docs/process/maintenance-intensity.yaml

@@ -0,0 +1,25 @@
+schema_version: 1
+default_level: L2
+levels:
+  L1:
+    triggers:
+      - textual-only
+      - link-only
+      - deterministic-projection
+  L2:
+    triggers:
+      - local-rule
+      - template-structure
+      - non-core-validator
+  L3:
+    triggers:
+      - lifecycle-gate
+      - ticket-state
+      - permission-boundary
+      - generation-semantics
+      - release-semantics
+      - cross-repo-contract
+      - core-validator
+      - historical-important-escape
+      - aggregate-behavior-change
+      - release-candidate

package/template/docs/process/schemas/frontend-implementation-evidence.schema.json

@@ -0,0 +1,39 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://yss.dev/schemas/frontend-implementation-evidence.schema.json",
+  "title": "YSS 前端实现还原证据",
+  "type": "object",
+  "additionalProperties": true,
+  "required": ["schema_version", "kind", "template", "status", "prototype_ref", "spec_ref", "route_and_page_inventory"],
+  "properties": {
+    "schema_version": { "const": 1 },
+    "kind": { "enum": ["plan", "verification"] },
+    "template": { "type": "boolean" },
+    "status": { "enum": ["draft", "approved", "blocked"] },
+    "prototype_ref": { "type": "string", "minLength": 1 },
+    "spec_ref": { "type": "string", "minLength": 1 },
+    "route_and_page_inventory": { "type": "array", "minItems": 1 },
+    "visual_acceptance_cases": { "type": "array", "minItems": 1 },
+    "desktop_viewport": { "type": "string", "minLength": 3 },
+    "narrow_viewport": { "type": "string", "minLength": 3 },
+    "state_cases": { "type": "array", "minItems": 1 },
+    "pnpm_commands": { "type": "array", "minItems": 1 },
+    "desktop_visual_evidence": { "type": "array", "minItems": 1 },
+    "narrow_view_visual_evidence": { "type": "array", "minItems": 1 },
+    "interaction_results": { "type": "array", "minItems": 1 },
+    "console_warning_check": { "enum": ["pass", "blocked"] },
+    "uncovered_differences": { "type": "array" },
+    "difference_owner": { "type": ["string", "null"] },
+    "independent_review": { "type": "object" }
+  },
+  "allOf": [
+    {
+      "if": { "properties": { "kind": { "const": "plan" } } },
+      "then": { "required": ["visual_acceptance_cases", "desktop_viewport", "narrow_viewport", "state_cases", "pnpm_commands"] }
+    },
+    {
+      "if": { "properties": { "kind": { "const": "verification" } } },
+      "then": { "required": ["desktop_visual_evidence", "narrow_view_visual_evidence", "interaction_results", "console_warning_check", "pnpm_commands", "uncovered_differences", "difference_owner", "independent_review"] }
+    }
+  ]
+}

package/template/docs/process/schemas/lifecycle-checkpoint.schema.json

@@ -0,0 +1,56 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://yss.dev/schemas/lifecycle-checkpoint.schema.json",
+  "title": "YSS 生命周期 Checkpoint",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["schema_version", "mode", "status", "stage", "artifacts", "gates", "next_work_unit", "ticket_sync", "verification", "human_review", "git_checkpoint", "blockers", "rollback"],
+  "properties": {
+    "schema_version": { "const": 1 },
+    "mode": { "enum": ["route", "orchestrate", "resume", "audit"] },
+    "status": { "enum": ["routing", "running", "paused-human-gate", "blocked", "completed"] },
+    "stage": { "type": "string", "pattern": "^stage\\.[a-z0-9][a-z0-9-]*$" },
+    "artifacts": {
+      "type": "object",
+      "patternProperties": {
+        "^artifact\\.[a-z0-9][a-z0-9-]*$": {
+          "type": "object",
+          "additionalProperties": false,
+          "required": ["status", "ref", "evidence_refs"],
+          "properties": {
+            "status": { "enum": ["missing", "draft", "ready-for-human", "approved", "stale", "not-applicable"] },
+            "ref": { "type": ["string", "null"] },
+            "evidence_refs": { "type": "array", "items": { "type": "string" } },
+            "stale_by": { "type": "array", "items": { "type": "string" } }
+          }
+        }
+      },
+      "additionalProperties": false
+    },
+    "gates": {
+      "type": "object",
+      "patternProperties": {
+        "^gate\\.[a-z0-9][a-z0-9-]*$": {
+          "type": "object",
+          "additionalProperties": false,
+          "required": ["status", "reason", "evidence_refs"],
+          "properties": {
+            "status": { "enum": ["not-evaluated", "blocked", "ready-for-human", "approved", "stale", "not-applicable"] },
+            "reason": { "type": "string" },
+            "evidence_refs": { "type": "array", "items": { "type": "string" } }
+          }
+        }
+      },
+      "additionalProperties": false
+    },
+    "next_work_unit": { "type": ["string", "null"], "pattern": "^work-unit\\.[a-z0-9][a-z0-9-]*$" },
+    "phase_boundary": { "type": "object" },
+    "stage_trace": { "type": "object" },
+    "ticket_sync": { "type": "object" },
+    "verification": { "type": "object" },
+    "human_review": { "type": "object" },
+    "git_checkpoint": { "type": "object" },
+    "blockers": { "type": "array" },
+    "rollback": { "type": "array" }
+  }
+}

package/template/docs/process/schemas/lifecycle-registry.schema.json

@@ -28,8 +28,8 @@
   "$defs": {
     "id": { "type": "string", "pattern": "^(stage|gate|artifact|work-unit|evidence)\\.[a-z0-9][a-z0-9-]*$" },
     "stages": { "type": "array", "minItems": 1, "items": { "type": "object", "additionalProperties": false, "required": ["id", "name", "goal", "exit_criteria"], "properties": { "id": { "$ref": "#/$defs/id" }, "name": { "type": "string", "minLength": 1 }, "goal": { "type": "string", "minLength": 1 }, "exit_criteria": { "type": "string", "minLength": 1 } } } },
-    "objects": { "type": "array", "items": { "type": "object", "additionalProperties": false, "required": ["id", "name", "stage", "trigger"], "properties": { "id": { "$ref": "#/$defs/id" }, "name": { "type": "string", "minLength": 1 }, "stage": { "type": "string", "pattern": "^stage\\." }, "trigger": { "type": "string", "minLength": 1 }, "evidence": { "type": "array", "minItems": 1, "items": { "type": "string", "pattern": "^evidence\\." } } } } },
-    "workUnits": { "type": "array", "items": { "type": "object", "additionalProperties": false, "required": ["id", "name", "scope", "input", "output", "completion"], "properties": { "id": { "$ref": "#/$defs/id" }, "name": { "type": "string", "minLength": 1 }, "scope": { "const": "template-source" }, "input": { "type": "string", "minLength": 1 }, "output": { "type": "string", "minLength": 1 }, "completion": { "type": "string", "minLength": 1 } } } },
+    "objects": { "type": "array", "items": { "type": "object", "additionalProperties": false, "required": ["id", "name", "stage", "trigger"], "properties": { "id": { "$ref": "#/$defs/id" }, "name": { "type": "string", "minLength": 1 }, "stage": { "type": "string", "pattern": "^stage\\." }, "trigger": { "type": "string", "minLength": 1 }, "evidence": { "type": "array", "minItems": 1, "items": { "type": "string", "pattern": "^evidence\\." } }, "requires_gates": { "type": "array", "uniqueItems": true, "items": { "type": "string", "pattern": "^gate\\." } } } } },
+    "workUnits": { "type": "array", "items": { "type": "object", "additionalProperties": false, "required": ["id", "name", "scope", "input", "output", "completion"], "properties": { "id": { "$ref": "#/$defs/id" }, "name": { "type": "string", "minLength": 1 }, "scope": { "enum": ["template-source", "project-instance"] }, "input": { "type": "string", "minLength": 1 }, "output": { "type": "string", "minLength": 1 }, "completion": { "type": "string", "minLength": 1 } } } },
     "evidence": { "type": "array", "items": { "type": "object", "additionalProperties": false, "required": ["id", "name", "description"], "properties": { "id": { "$ref": "#/$defs/id" }, "name": { "type": "string", "minLength": 1 }, "description": { "type": "string", "minLength": 1 } } } }
   }
 }

package/template/docs/process/templates/frontend-implementation-plan-template.yaml

@@ -0,0 +1,16 @@
+schema_version: 1
+kind: plan
+template: true
+status: draft
+prototype_ref: docs/.scratch/example/design/prototype.html
+spec_ref: docs/.scratch/example/spec.md
+route_and_page_inventory:
+  - route: /example
+    page: ExamplePage
+visual_acceptance_cases:
+  - primary desktop flow
+  - narrow viewport flow
+desktop_viewport: 1440x900
+narrow_viewport: 390x844
+state_cases: [loading, empty, error, permission, selected, key-interaction]
+pnpm_commands: [pnpm lint, pnpm type-check, pnpm test]

package/template/docs/process/templates/frontend-implementation-verification-template.yaml

@@ -0,0 +1,21 @@
+schema_version: 1
+kind: verification
+template: true
+status: draft
+prototype_ref: docs/.scratch/example/design/prototype.html
+spec_ref: docs/.scratch/example/spec.md
+route_and_page_inventory:
+  - route: /example
+    page: ExamplePage
+desktop_visual_evidence: [docs/.scratch/example/verification/desktop.png]
+narrow_view_visual_evidence: [docs/.scratch/example/verification/narrow.png]
+interaction_results: [loading, empty, error, permission, selected, key-interaction]
+console_warning_check: blocked
+pnpm_commands: [pnpm lint, pnpm type-check, pnpm test]
+uncovered_differences: []
+difference_owner: null
+independent_review:
+  reviewer: non-implementer
+  candidate_digest: pending
+  status: pending
+  findings_ref: docs/.scratch/example/verification/ui-fidelity-review.md

package/template/docs/process/templates/lifecycle-checkpoint-template.yaml

@@ -0,0 +1,30 @@
+schema_version: 1
+mode: route
+status: routing
+stage: stage.entry-triage
+artifacts: {}
+gates: {}
+next_work_unit: work-unit.discovery-opportunity
+phase_boundary:
+  decision: continue
+  reason: initial routing
+stage_trace:
+  stage: stage.entry-triage
+  upstream_refs: []
+  artifact_refs: []
+  gate_decisions: []
+  downstream_impacts: []
+ticket_sync:
+  status: pending
+  refs: []
+verification:
+  commands: []
+  evidence_refs: []
+human_review:
+  required: false
+  status: not-applicable
+git_checkpoint:
+  required: false
+  status: not-applicable
+blockers: []
+rollback: []

package/template/docs/process/templates/stage-checkpoint-template.md

@@ -2,14 +2,17 @@
 
 ```yaml
 schema_version: 1
-mode: project-instance
+mode: <route|orchestrate|resume|audit>
+status: <routing|running|paused-human-gate|blocked|completed>
 stage: <lifecycle stage>
 artifacts:
-  - path: <artifact path>
-    status: <draft|ready-for-human|ready-for-agent|completed|blocked|not-applicable>
+  <stable-artifact-id>:
+    status: <missing|draft|ready-for-human|approved|stale|not-applicable>
+    ref: <readable artifact reference>
+    evidence_refs: []
 gates:
-  - name: <gate name>
-    status: <passed|failed|blocked|not-applicable>
+  <stable-gate-id>:
+    status: <not-evaluated|blocked|ready-for-human|approved|stale|not-applicable>
     reason: <why this status applies>
 phase_boundary:
   decision: <continue|clear|handoff|subagent|compact>
@@ -24,6 +27,7 @@ stage_trace:
 ticket_sync:
   status: <pending|synced|not-applicable>
   refs: []
+next_work_unit: <stable work-unit id>
 verification:
   commands: []
   evidence_refs: []

package/template/docs/user-guide//344/272/247/345/223/201/347/240/224/345/217/221/345/205/250/347/224/237/345/221/275/345/221/250/346/234/237/346/234/200/344/275/263/345/256/236/350/267/265.md

@@ -482,7 +482,7 @@ docs/.scratch/data-modeling/design/data-modeling-prototype-review.md
 | 图谱、血缘、流程编排画布 | tldraw / xyflow | 适合数据血缘、任务流、关系图等画布型体验 |
 | 进入高保真前门禁 | `prototype-review` | 未通过则回到原型阶段 |
 
-`product-design-prototype`、`wireframe-prototype`、`high-fidelity-html-prototype` 仅作为历史兼容入口或产物门禁名称保留；新的产品原型产出默认使用 `product-design:index`。
+`product-design-prototype`、`high-fidelity-html-prototype` 仅作为历史兼容入口或产物门禁名称保留；新的产品原型产出默认使用 `product-design:index`，已退休技能不再提供兼容路由。
 
 如果团队使用 Figma、即时设计、Axure 或其它原型工具，可以在 `docs/.scratch/data-modeling/design/data-modeling-interaction-spec.md` 中保存链接、版本、评审记录和关键截图说明。第一版不强制引入 Excalidraw、Figma、Penpot、tldraw 或 xyflow 作为项目依赖。
 

package/template/scripts/lib/lifecycle-registry.mjs

@@ -128,6 +128,11 @@ export function validateRegistry(registry, { baseline = DEFAULT_BASELINE } = {})
       requireReference(ids, reference, `${gate.id}.evidence`);
       if (ids.get(reference) !== "evidence") fail(`${gate.id}.evidence 必须引用 evidence.*`);
     }
+    for (const reference of gate.requires_gates ?? []) {
+      requireReference(ids, reference, `${gate.id}.requires_gates`);
+      if (ids.get(reference) !== "gates") fail(`${gate.id}.requires_gates 必须引用 gate.*`);
+      if (reference === gate.id) fail(`${gate.id}.requires_gates 不得引用自身`);
+    }
   }
   for (const artifact of registry.artifacts) {
     requireReference(ids, artifact.stage, `${artifact.id}.stage`);
@@ -144,8 +149,8 @@ export function renderLifecycleStructure(registry) {
     "## 1. 主阶段", "", "| 稳定 ID | 阶段 | 目标 | 退出标准 |", "|---|---|---|---|"
   ];
   for (const stage of registry.stages) lines.push(`| \`${stage.id}\` | ${stage.name} | ${stage.goal} | ${stage.exit_criteria} |`);
-  lines.push("", "## 2. 生命周期对象", "", "门禁是需要裁决的审查点；产物、工作单元和证据不是门禁的同义词。未命中条件的门禁记录 \`not-applicable\` 及原因，不生成空文档。", "", "### 2.1 条件门禁", "", "| 稳定 ID | 门禁 | 所属阶段 | 触发条件 | 必须留下的证据 |", "|---|---|---|---|---|");
-  for (const gate of registry.gates) lines.push(`| \`${gate.id}\` | ${gate.name} | \`${gate.stage}\` | ${gate.trigger} | ${gate.evidence.map((id) => `\`${id}\``).join("、")} |`);
+  lines.push("", "## 2. 生命周期对象", "", "门禁是需要裁决的审查点；产物、工作单元和证据不是门禁的同义词。未命中条件的门禁记录 \`not-applicable\` 及原因，不生成空文档。", "", "### 2.1 条件门禁", "", "| 稳定 ID | 门禁 | 所属阶段 | 触发条件 | 前置门禁 | 必须留下的证据 |", "|---|---|---|---|---|---|");
+  for (const gate of registry.gates) lines.push(`| \`${gate.id}\` | ${gate.name} | \`${gate.stage}\` | ${gate.trigger} | ${(gate.requires_gates ?? []).map((id) => `\`${id}\``).join("、") || "无"} | ${gate.evidence.map((id) => `\`${id}\``).join("、")} |`);
   lines.push("", "### 2.2 生命周期产物", "", "| 稳定 ID | 产物 | 所属阶段 | 触发条件 |", "|---|---|---|---|");
   for (const artifact of registry.artifacts) lines.push(`| \`${artifact.id}\` | ${artifact.name} | \`${artifact.stage}\` | ${artifact.trigger} |`);
   lines.push("", "### 2.3 执行证据", "", "| 稳定 ID | 证据 | 说明 |", "|---|---|---|");
@@ -155,8 +160,8 @@ export function renderLifecycleStructure(registry) {
 }
 
 export function renderWorkUnits(registry) {
-  const lines = ["<!-- lifecycle-registry:work-units:start -->", "> 此表由 `docs/process/lifecycle-registry.yaml` 生成；它只描述 `template-source` 的 Harness 工作单元。", "", "| 稳定 ID | 工作单元 | 输入 | 输出 | 完成条件 |", "|---|---|---|---|---|"];
-  for (const unit of registry.work_units) lines.push(`| \`${unit.id}\` | ${unit.name} | ${unit.input} | ${unit.output} | ${unit.completion} |`);
+  const lines = ["<!-- lifecycle-registry:work-units:start -->", "> 此表由 `docs/process/lifecycle-registry.yaml` 生成；工作单元按 `scope` 区分模板维护与项目实例流程。", "", "| 稳定 ID | 范围 | 工作单元 | 输入 | 输出 | 完成条件 |", "|---|---|---|---|---|---|"];
+  for (const unit of registry.work_units) lines.push(`| \`${unit.id}\` | ${unit.scope} | ${unit.name} | ${unit.input} | ${unit.output} | ${unit.completion} |`);
   lines.push("<!-- lifecycle-registry:work-units:end -->");
   return `${lines.join("\n")}\n`;
 }