create-yss-spec 3.3.1 → 3.3.4

package/template/docs/agents/digital-human-roles.md

@@ -1,6 +1,6 @@
 # 数字人角色
 
-结构化事实源是 `docs/agents/digital-human-roles.yaml`。角色、技能、协作组和会签级别与运行时无关。Claude Code、Cursor、Codex、Grok Bot 等只通过 YAML `runtimes` 绑定。冲突时以 YAML 为准。
+结构化事实源是 `docs/agents/digital-human-roles.yaml`。角色、技能、协作组和会签级别与运行时无关。Cursor、Codex、Grok Bot 等只通过 YAML `runtimes` 绑定。冲突时以 YAML 为准。
 
 ## 何时读本文
 
@@ -14,27 +14,15 @@
 | 主控数字人 | 生命周期编排器的运行时实例 | 第八个业务职称 |
 | 职能工作单元 | Plan / Spec / Code / Review | 职称 |
 | 执行态 | Explorer / Drafter / Worker / Reviewer / Verifier | 数字人角色 |
-| 运行时绑定 | 如何在 Cursor / Claude / Grok 等落地 | 角色职责本身 |
+| 运行时绑定 | 如何在 Cursor / Codex / Grok 等落地 | 角色职责本身 |
 
 一次数字人任务包同时写明 `task_id`、`work_unit_id`、`actor_id`、数字人角色、执行态、当前 `runtime_id`，以及从角色表复制的 `core_skills` / `forbidden_skills`。可用 `taskPackageDefaults(roleId)`（`scripts/lib/digital-human-roles.mjs`）读取，禁止手写第二套技能包。`role.test-engineer` 的 core_skills 含 YSS / Alibaba 专项 skill，仅作为 `code-review` Standards 只读输入，不得写实现；finding 交实现者修复或回 实现合同编译器，审查者不得当场改代码。任务包 canonical Schema 为 `docs/process/schemas/digital-human-task-package.schema.json`，按 `contract.kind` 选择生命周期、切片实现或模板维护合同。
 
 ## 会签人
 
-`gate_policy.digital_human_review` 与 `dual_digital_human` 是「门禁 × 起草者 × 会签人」规则，不是门禁名单。主控按 `countersigners` 派会签任务。
+正式门禁的会签由 `gate_policy.digital_human_review` / `dual_digital_human` / `biological_human` 定义；内部专业审查由 `check_reviews` 定义，自动检查由 `automatic_checks` 定义。每项的起草者与会签人只读取 YAML，不在本文复制名单。
 
-| 门禁 / 工作单元 | 起草 | 会签 |
-|---|---|---|
-| `gate.prototype-reviewed` | `role.product-manager` | `role.frontend-engineer` |
-| `gate.openapi-draft-reviewed` | `role.backend-engineer` | `role.frontend-engineer` |
-| `gate.engineering-baseline-accepted` | （实现者） | `role.test-engineer` |
-| `gate.frontend-implementation-verified` | `role.frontend-engineer` | `role.test-engineer` |
-| `work-unit.code-review` | 实现者 | `role.test-engineer`（必须不同实例） |
-| `gate.spec-baseline-approved` | `role.requirements-manager` | `role.product-manager` |
-| `gate.openapi-frozen` | `role.backend-engineer` | `role.product-manager`、`role.test-engineer` |
-| `gate.user-confirmation` | 产品数字人提供建议 | 提问者或其明确指定的生物人负责人 |
-| `gate.release-ready` | — | 生物人（`role.biological-human`） |
-
-未列入表的门禁（含 `gate.design-reviewed`、`gate.architecture-reviewed`）走 `default_if_unlisted: biological-human`。
+Plan、产品设计、工程契约统一呈现适用检查后批准。`gate.delivery-accepted` 由测试角色进行交付验收，实际合并或发布仍须另有生物人授权。内部检查不独立请求用户决定；检查失败仍阻断聚合门禁。专业审查可在同一工作单元完成多个检查项，但必须保留逐项结论、资产摘要与独立执行者身份。
 
 会签写入 `docs/.scratch/<feature>/gates/<gate-id>-approval.yaml`，形状见 `docs/templates/approval-record-template.yaml`。恢复前运行 `scripts/verify-approval-record --require-approved`。错误会签只能得到 `blocked`，不能把门禁标成 `approved`。Checkpoint 里会签桶门禁为 `approved` 时必须有可读 `approval_ref`。
 
@@ -57,7 +45,7 @@
 | ID | 覆盖 | 落地方式 |
 |---|---|---|
 | `runtime.generic` | 任何能加载 `core_skills` 并接受任务包的 Agent | 通用会话 / 人设 / system prompt |
-| `runtime.skill-projection` | `yss-skill-registry.yaml` 的 `agent_runtime_roots`（claude、codex、cursor、pi、qoder、trae） | 投影技能 + subagent 任务包 |
+| `runtime.skill-projection` | `yss-skill-registry.yaml` 的 `agent_runtime_roots`（codex、cursor、pi） | 投影技能 + subagent 任务包 |
 | `runtime.grok` | Grok Bot | 持久 Bot、群聊或 1:1 交接；群超过 6 人改 1:1，不改逻辑协作组 |
 
 新增平台：先加 `runtimes` 条目，再写适配说明。不要把平台限制写进 `roles`。
@@ -71,7 +59,7 @@ Grok 专用操作见 `docs/templates/grok-bot-profile-template.md`。通用实
 | 运行时副作用审批 | 发消息、改生产、付款、删数据等工具动作 | 生物人（各平台自己的 Allow / 确认框） |
 | 生命周期会签 | `gate.*` 与独立 code review | 见 YAML `gate_policy` |
 
-会签写入 `docs/templates/approval-record-template.yaml`，带 `runtime_id`、`principal_ref` 与实例引用。起草者不得出现在会签人里。`gate.release-ready`、对外商务合同、运行时外部副作用，以及未列入会签表的 `gate.design-reviewed` / `gate.architecture-reviewed` 仍须生物人。
+会签写入 `docs/templates/approval-record-template.yaml`，带 `runtime_id`、`principal_ref` 与实例引用。起草者不得出现在会签人里。对外商务合同和运行时外部副作用仍须生物人；交付验收不授予这些权限。
 
 ## 实例化
 

package/template/docs/agents/digital-human-roles.yaml

@@ -2,9 +2,7 @@ schema_version: 1
 registry_id: yss.digital-human-roles
 status: active
 description: >-
-  数字人角色、主控、阶段协作组、技能启用/禁止与生命周期会签的单一事实源。
-  角色配置与运行时无关；Claude / Cursor / Codex / Grok 等只通过 runtimes 绑定。
-  Ticket 五态不是数字人角色。
+  数字人角色、主控、阶段协作组、技能启用/禁止与生命周期会签的单一事实源。 角色配置与运行时无关；Cursor / Codex / Grok 等只通过 runtimes 绑定。 Ticket 五态不是数字人角色。
 canonical_path: docs/agents/digital-human-roles.yaml
 runtime_policy:
   overlay_on_lifecycle: true
@@ -18,7 +16,7 @@ runtime_policy:
   biological_veto: true
   implementer_must_differ: true
   write_isolation: task-package-policy
-  dual_hat_split_when: [cross-repo-load, responsibility-conflict]
+  dual_hat_split_when: [ cross-repo-load, responsibility-conflict ]
 
 runtimes:
   - id: runtime.generic
@@ -43,9 +41,7 @@ runtimes:
     shared_workspace_is_not_security_boundary: false
     side_effect_approval: biological-human
     notes: >-
-      覆盖 docs/agents/yss-skill-registry.yaml 的 agent_runtime_roots
-      （claude / codex / cursor / pi / qoder / trae）。
-      技能仍从 .agents/skills 投影，不按职称再维护一份。
+      覆盖 docs/agents/yss-skill-registry.yaml 的 agent_runtime_roots （codex / cursor / pi）。 技能仍从 .agents/skills 投影，不按职称再维护一份。
   - id: runtime.grok
     kind: grok-bot
     instance_kind: durable-bot
@@ -58,25 +54,19 @@ runtimes:
     shared_workspace_is_not_security_boundary: true
     side_effect_approval: biological-human
     notes: >-
-      Grok Bot 适配。群聊 2–6 人；超出则改 1:1 交接，不改逻辑阶段协作组。
-      全部 Bot 共享云计算机，写范围只靠任务包。不新增 agent_runtime_roots.grok。
+      Grok Bot 适配。群聊 2–6 人；超出则改 1:1 交接，不改逻辑阶段协作组。 全部 Bot 共享云计算机，写范围只靠任务包。不新增 agent_runtime_roots.grok。
 
 orchestrator:
   id: role.lifecycle-orchestrator
   name: 主控数字人
   kind: orchestrator
   title: YSS 生命周期主控
-  default_dual_hat: [role.project-manager]
-  stages: [stage.entry-triage, stage.plan, stage.spec-architecture, stage.product-design, stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective]
-  core_skills: [yss-product-lifecycle, yss-implementation-contract-compiler]
-  forbidden_skills: [yss-domain, yss-ui, yss-ui-business-page-generation, yss-web-controller, yss-repository, implement]
+  default_dual_hat: [ role.project-manager ]
+  stages: [ stage.entry-triage, stage.plan, stage.spec-architecture, stage.product-design, stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective ]
+  core_skills: [ yss-product-lifecycle, yss-implementation-contract-compiler ]
+  forbidden_skills: [ yss-domain, yss-ui, yss-ui-business-page-generation, yss-web-controller, yss-repository, implement ]
   description: >-
-    Own YSS lifecycle routing. Read yss-project.yaml and CONTEXT.md first.
-    Select the next unblocked work unit, compile a task package, and assign
-    one owner per stage. Do not implement business code. Do not approve Slice
-    contracts into ready-for-agent without the full formula. Do not announce
-    releasable. Default dual-hat: project manager until a separate instance
-    is required. Authoritative artifacts live in git.
+    Own YSS lifecycle routing. Read yss-project.yaml and CONTEXT.md first. Select the next unblocked work unit, compile a task package, and assign one owner per stage. Do not implement business code. Do not approve Slice contracts into ready-for-agent without the full formula. Do not announce releasable. Default dual-hat: project manager until a separate instance is required. Authoritative artifacts live in git.
 
 roles:
   - id: role.requirements-manager
@@ -84,177 +74,174 @@ roles:
     kind: digital-human
     contract_version: 1
     title: YSS 需求经理
-    stages: [stage.plan, stage.spec-architecture]
-    draft_artifact_ids: [artifact.plan-record, artifact.spec]
-    core_skills: [grilling, domain-modeling, yss-research, competitive-intelligence, grill-with-docs]
-    forbidden_skills: [yss-ui, yss-domain, yss-web-controller, yss-repository, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, yss-frontend-scaffold-generator, implement, tdd]
+    stages: [ stage.plan, stage.spec-architecture ]
+    draft_artifact_ids: [ artifact.plan-record, artifact.spec ]
+    core_skills: [ grilling, domain-modeling, yss-research, competitive-intelligence, grill-with-docs ]
+    forbidden_skills: [ yss-ui, yss-domain, yss-web-controller, yss-repository, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, yss-frontend-scaffold-generator, implement, tdd ]
     description: >-
-      Own Plan language, users, MVP, non-goals, success criteria, test
-      seams, and Spec prose. Propose CONTEXT.md glossary entries. Do not freeze
-      visual prototypes, OpenAPI, or code. Do not guess unconfirmed business
-      rules. Hand off to the orchestrator when the frontier is empty.
+      Own Plan language, users, MVP, non-goals, success criteria, test seams, and Spec prose. Propose CONTEXT.md glossary entries. Do not freeze visual prototypes, OpenAPI, or code. Do not guess unconfirmed business rules. Hand off to the orchestrator when the frontier is empty.
 
   - id: role.product-manager
     name: 产品经理
     kind: digital-human
     contract_version: 1
     title: YSS 产品经理
-    stages: [stage.plan, stage.spec-architecture, stage.product-design, stage.verification-release-retrospective]
-    draft_artifact_ids: [artifact.product-overview, artifact.functional-architecture, artifact.interaction-spec, artifact.state-matrix, artifact.prototype-confirmation]
-    core_skills: [yss-design-system, yss-prototype-stage, prototype-review, yss-antdv-next-design, yss-research, competitive-intelligence]
-    forbidden_skills: [yss-ui, yss-domain, yss-repository, yss-web-controller, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, implement, tdd]
+    stages: [ stage.plan, stage.spec-architecture, stage.product-design, stage.verification-release-retrospective ]
+    draft_artifact_ids: [ artifact.product-overview, artifact.functional-architecture, artifact.interaction-spec, artifact.state-matrix, artifact.prototype-confirmation ]
+    core_skills: [ yss-design-system, yss-prototype-stage, prototype-review, yss-antdv-next-design, yss-research, competitive-intelligence ]
+    forbidden_skills: [ yss-ui, yss-domain, yss-repository, yss-web-controller, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, implement, tdd ]
     description: >-
-      Own priority, product-design impact, interaction, state matrix, prototype
-      confirmation recommendation, and the commercial constraints, delivery
-      commitments, release window, and commercial non-goals for Plan and
-      release. May reject Spec scope. Do not write production code or freeze
-      OpenAPI alone. Do not independently approve external commercial contracts
-      or formal commitments; those require biological-human approval. Frontend
-      implementation uses the frontend-engineer role and yss-ui, not
-      yss-antdv-next-design. Explicit React/AntD compatibility prototypes use
-      yss-antd-design conditionally.
+      Own priority, product-design impact, interaction, state matrix, prototype confirmation recommendation, and the commercial constraints, delivery commitments, release window, and commercial non-goals for Plan and release. May reject Spec scope. Do not write production code or freeze OpenAPI alone. Do not independently approve external commercial contracts or formal commitments; those require biological-human approval. Frontend implementation uses the frontend-engineer role and yss-ui, not yss-antdv-next-design. Explicit React/AntD compatibility prototypes use yss-antd-design conditionally.
 
   - id: role.project-manager
     name: 项目经理
     kind: digital-human
     contract_version: 1
     title: YSS 项目经理
-    stages: [stage.entry-triage, stage.plan, stage.spec-architecture, stage.product-design, stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective]
-    draft_artifact_ids: [artifact.parent-ticket, artifact.vertical-slice-ticket]
-    core_skills: [yss-product-lifecycle, handoff, implementation-repo-onboarding, cross-repo-implementation-routing]
-    forbidden_skills: [yss-domain, yss-ui, implement, tdd, yss-web-controller]
+    stages: [ stage.entry-triage, stage.plan, stage.spec-architecture, stage.product-design, stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective ]
+    draft_artifact_ids: [ artifact.parent-ticket, artifact.vertical-slice-ticket ]
+    core_skills: [ yss-product-lifecycle, handoff, implementation-repo-onboarding, cross-repo-implementation-routing ]
+    forbidden_skills: [ yss-domain, yss-ui, implement, tdd, yss-web-controller ]
     description: >-
-      Own parent Ticket hygiene, checkpoints, handoff, risk, and implementation
-      repo registry. Do not set ready-for-agent; the orchestrator recomputes
-      that formula. Do not approve Spec or OpenAPI Freeze. Do not write business
-      code or serve as independent Reviewer. Default dual-hat on the
-      orchestrator instance until dual_hat_split_when
-      (cross-repo-load or responsibility-conflict) requires a separate instance.
+      Own parent Ticket hygiene, checkpoints, handoff, risk, and implementation repo registry. Do not set ready-for-agent; the orchestrator recomputes that formula. Do not approve Spec or OpenAPI Freeze. Do not write business code or serve as independent Reviewer. Default dual-hat on the orchestrator instance until dual_hat_split_when (cross-repo-load or responsibility-conflict) requires a separate instance.
 
   - id: role.frontend-engineer
     name: 前端工程师
     kind: digital-human
     contract_version: 1
     title: YSS 前端工程师
-    stages: [stage.product-design, stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective]
-    draft_artifact_ids: [artifact.frontend-implementation-plan]
-    core_skills: [yss-ui, yss-ui-business-page-generation, yss-components, yss-formily, formily-foundation, formily-linkage-effects, formily-mode-slot-detail, formily-step-flow, ytable-usage, ytree-usage, yedit-table-usage, yss-api-integration, yss-hook, theme-token-usage, page-skeleton, page-list-module, page-form-module, component-selection-imports, vue3-best-practices, tdd]
-    forbidden_skills: [yss-domain, yss-application, yss-repository, yss-mybatis, yss-web-controller, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, java-backend-commit]
+    stages: [ stage.product-design, stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective ]
+    draft_artifact_ids: [ artifact.frontend-implementation-plan ]
+    core_skills: [ yss-ui, yss-ui-business-page-generation, yss-components, yss-formily, formily-foundation, formily-linkage-effects, formily-mode-slot-detail, formily-step-flow, ytable-usage, ytree-usage, yedit-table-usage, yss-api-integration, yss-hook, theme-token-usage, page-skeleton, page-list-module, page-form-module, component-selection-imports, vue3-best-practices, tdd ]
+    forbidden_skills: [ yss-domain, yss-application, yss-repository, yss-mybatis, yss-web-controller, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, java-backend-commit ]
     description: >-
-      Own Vue page modules, frontend tests, and frontend_implementation_plan.
-      Review OpenAPI Draft for client fit and prototype feasibility. Write only
-      contract-allowed frontend paths. Verify with pnpm. Do not freeze API, own
-      backend domain, or countersign your own merge.
+      Own Vue page modules, frontend tests, and frontend_implementation_plan. Review OpenAPI Draft for client fit and prototype feasibility. Write only contract-allowed frontend paths. Verify with pnpm. Do not freeze API, own backend domain, or countersign your own merge.
 
   - id: role.backend-engineer
     name: 后端工程师
     kind: digital-human
     contract_version: 1
     title: YSS 后端工程师
-    stages: [stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective]
-    draft_artifact_ids: [artifact.openapi-draft, artifact.data-architecture, artifact.technical-design]
-    core_skills: [yss-implementation-contract-compiler, yss-technical-design, yss-tactical-design, yss-mvc-design, yss-domain, yss-application, yss-repository, yss-mybatis, yss-web-controller, yss-dto, mapstruct, lombok, alibaba-java-code-style, yss-exception, yss-validation, tdd, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator]
-    forbidden_skills: [yss-ui, yss-ui-business-page-generation, yss-formily, yss-frontend-scaffold-generator, yss-antd-design, yss-antdv-next-design, page-list-module, page-form-module]
+    stages: [ stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective ]
+    draft_artifact_ids: [ artifact.openapi-draft, artifact.data-architecture, artifact.technical-design ]
+    core_skills: [ yss-implementation-contract-compiler, yss-technical-design, yss-tactical-design, yss-mvc-design, yss-domain, yss-application, yss-repository, yss-mybatis, yss-web-controller, yss-dto, mapstruct, lombok, alibaba-java-code-style, yss-exception, yss-validation, tdd, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator ]
+    forbidden_skills: [ yss-ui, yss-ui-business-page-generation, yss-formily, yss-frontend-scaffold-generator, yss-antd-design, yss-antdv-next-design, page-list-module, page-form-module ]
     description: >-
-      Own OpenAPI Draft, data-architecture contributions, and backend tests.
-      Write only contract-allowed backend paths. Verify with ./mvnw. Do not
-      Freeze OpenAPI, treat UI copy as requirements, or countersign your own
-      implementation.
+      Own OpenAPI Draft, data-architecture contributions, and backend tests. Write only contract-allowed backend paths. Verify with ./mvnw. Do not Freeze OpenAPI, treat UI copy as requirements, or countersign your own implementation.
 
   - id: role.test-engineer
     name: 测试工程师
     kind: digital-human
     contract_version: 1
     title: YSS 测试工程师
-    stages: [stage.spec-architecture, stage.vertical-slice-implementation, stage.verification-release-retrospective]
-    draft_artifact_ids: [artifact.frontend-implementation-verification]
-    owned_evidence_ids: [evidence.fresh-verification, evidence.frontend-implementation-verification]
-    core_skills: [tdd, diagnosing-bugs, code-review, alibaba-java-code-style, yss-ui, yss-design-system, yss-ui-business-page-generation, yss-domain, yss-application, yss-repository, yss-web-controller, yss-dto, mapstruct, lombok]
-    forbidden_skills: [yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, yss-frontend-scaffold-generator, implement, to-spec]
+    stages: [ stage.spec-architecture, stage.vertical-slice-implementation, stage.verification-release-retrospective ]
+    draft_artifact_ids: [ artifact.frontend-implementation-verification ]
+    owned_evidence_ids: [ evidence.fresh-verification, evidence.frontend-implementation-verification ]
+    core_skills: [ tdd, diagnosing-bugs, code-review, alibaba-java-code-style, yss-ui, yss-design-system, yss-ui-business-page-generation, yss-domain, yss-application, yss-repository, yss-web-controller, yss-dto, mapstruct, lombok ]
+    forbidden_skills: [ yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, yss-frontend-scaffold-generator, implement, to-spec ]
     description: >-
-      Own test code, defect records, fresh verification, and frontend
-      implementation verification evidence. Review every implementation slice
-      through the unique code-review skill, loading YSS and Alibaba specialist
-      skills as read-only Standards sources. Recommend release readiness; do
-      not close gate.release-ready. Do not change product scope or write
-      feature implementation. Must be a different instance from the implementer.
+      Own test code, defect records, fresh verification, and frontend implementation verification evidence. Review every implementation slice through the unique code-review skill, loading YSS and Alibaba specialist skills as read-only Standards sources. Recommend release readiness; do not close gate.delivery-accepted. Do not change product scope or write feature implementation. Must be a different instance from the implementer.
 
 stage_groups:
   - id: group.plan
     name: Plan
     stage: stage.plan
-    members: [role.lifecycle-orchestrator, role.requirements-manager, role.product-manager]
+    members: [ role.lifecycle-orchestrator, role.requirements-manager, role.product-manager ]
   - id: group.spec
     name: Spec
     stage: stage.spec-architecture
-    members: [role.lifecycle-orchestrator, role.requirements-manager, role.product-manager, role.test-engineer]
+    members: [ role.lifecycle-orchestrator, role.requirements-manager, role.product-manager, role.test-engineer ]
   - id: group.product-design
     name: 产品设计
     stage: stage.product-design
-    members: [role.lifecycle-orchestrator, role.product-manager, role.requirements-manager, role.frontend-engineer]
+    members: [ role.lifecycle-orchestrator, role.product-manager, role.requirements-manager, role.frontend-engineer ]
   - id: group.contract
     name: 契约
     stage: stage.system-data-engineering
-    members: [role.lifecycle-orchestrator, role.backend-engineer, role.frontend-engineer, role.test-engineer, role.product-manager]
+    members: [ role.lifecycle-orchestrator, role.backend-engineer, role.frontend-engineer, role.test-engineer, role.product-manager ]
   - id: group.tickets
     name: Ticket 正式化
     stage: stage.ticket-formalization
-    members: [role.lifecycle-orchestrator, role.project-manager, role.frontend-engineer, role.backend-engineer, role.test-engineer]
+    members: [ role.lifecycle-orchestrator, role.project-manager, role.frontend-engineer, role.backend-engineer, role.test-engineer ]
   - id: group.implementation
     name: 实现
     stage: stage.vertical-slice-implementation
-    members: [role.lifecycle-orchestrator, role.frontend-engineer, role.backend-engineer, role.test-engineer]
+    members: [ role.lifecycle-orchestrator, role.frontend-engineer, role.backend-engineer, role.test-engineer ]
   - id: group.release
     name: 发布
     stage: stage.verification-release-retrospective
-    members: [role.lifecycle-orchestrator, role.project-manager, role.test-engineer, role.product-manager]
+    members: [ role.lifecycle-orchestrator, role.project-manager, role.test-engineer, role.product-manager ]
 
 gate_policy:
   default_if_unlisted: biological-human
-  unlisted_kept_biological:
-    - gate.design-reviewed
-    - gate.architecture-reviewed
-  evidence_only:
-    - gate.frontend-delivery-inputs-verified
-    - gate.repository-identity-valid
-    - gate.prototype-verified
+  evidence_only: []
   orchestrator:
-    - gate.implementation-repositories-ready
     - gate.slice-contract-approved
-    - gate.slice-ready-for-agent
   digital_human_review:
-    - gate: gate.prototype-reviewed
-      drafter: role.product-manager
-      countersigners: [role.frontend-engineer]
-    - gate: gate.openapi-draft-reviewed
-      drafter: role.backend-engineer
-      countersigners: [role.frontend-engineer]
-    - gate: gate.engineering-baseline-accepted
-      countersigners: [role.test-engineer]
-    - gate: gate.frontend-implementation-verified
-      drafter: role.frontend-engineer
-      countersigners: [role.test-engineer]
+    - gate: gate.delivery-accepted
+      countersigners:
+        - role.test-engineer
   digital_human_review_work_units:
     - work_unit: work-unit.code-review
-      countersigners: [role.test-engineer]
+      countersigners:
+        - role.test-engineer
       implementer_must_differ: true
   dual_digital_human:
-    - gate: gate.spec-baseline-approved
-      drafter: role.requirements-manager
-      countersigners: [role.product-manager]
-    - gate: gate.domain-strategy-approved
+    - gate: gate.plan-approved
       drafter: role.requirements-manager
-      countersigners: [role.product-manager]
-    - gate: gate.stage-decision-package-approved
+      countersigners:
+        - role.product-manager
+    - gate: gate.spec-baseline-approved
       drafter: role.requirements-manager
-      countersigners: [role.product-manager]
-    - gate: gate.openapi-frozen
+      countersigners:
+        - role.product-manager
+    - gate: gate.engineering-contract-approved
       drafter: role.backend-engineer
-      countersigners: [role.product-manager, role.test-engineer]
+      countersigners:
+        - role.product-manager
+        - role.test-engineer
   product_digital_human_with_biological_veto: []
   biological_human:
-    - gate.user-confirmation
-    - gate.release-ready
+    - gate.product-design-approved
+  automatic_checks:
+    - check.repository-identity-valid
+    - check.frontend-delivery-inputs-verified
+    - check.prototype-verified
+    - check.implementation-repositories-ready
+    - check.slice-ready-for-agent
+    - check.openapi-frozen
+  check_reviews:
+    - gate: check.domain-strategy-approved
+      drafter: role.requirements-manager
+      countersigners:
+        - role.product-manager
+    - gate: check.stage-decision-package-approved
+      drafter: role.requirements-manager
+      countersigners:
+        - role.product-manager
+    - gate: check.prototype-reviewed
+      drafter: role.product-manager
+      countersigners:
+        - role.frontend-engineer
+    - gate: check.openapi-draft-reviewed
+      drafter: role.backend-engineer
+      countersigners:
+        - role.frontend-engineer
+    - gate: check.design-reviewed
+      countersigners:
+        - role.backend-engineer
+        - role.test-engineer
+    - gate: check.architecture-reviewed
+      countersigners:
+        - role.backend-engineer
+        - role.test-engineer
+    - gate: check.engineering-baseline-accepted
+      countersigners:
+        - role.test-engineer
+    - gate: check.frontend-implementation-verified
+      drafter: role.frontend-engineer
+      countersigners:
+        - role.test-engineer
   runtime_side_effect_approval: biological-human
   commercial_contract: biological-human
 
@@ -263,29 +250,24 @@ user_decision_policy:
   schema_version: 1
   default_responder: requester
   delegate_requires_requester_evidence: true
-  source_kinds: [platform-message, session-export, user-confirmation-file]
+  source_kinds: [ platform-message, session-export, user-confirmation-file ]
   gates:
-    - gate.domain-strategy-approved
-    - gate.stage-decision-package-approved
+    - gate.plan-approved
     - gate.spec-baseline-approved
-    - gate.user-confirmation
-    - gate.openapi-frozen
-    - gate.design-reviewed
-    - gate.architecture-reviewed
-    - gate.release-ready
+    - gate.product-design-approved
+    - gate.engineering-contract-approved
   work_units:
-    work-unit.plan-requirements: plan-conclusion
     work-unit.service-project-initialization: scaffold-choice
     work-unit.implementation-repository-preparation: scaffold-choice
     work-unit.slice-implementation: implementation-scope
-    work-unit.release-and-retrospective: gate.release-ready
   work_unit_gates:
-    work-unit.domain-strategy-design: [gate.domain-strategy-approved]
-    work-unit.stage-decision: [gate.stage-decision-package-approved]
-    work-unit.spec-synthesis: [gate.spec-baseline-approved]
-    work-unit.prototype-design: [gate.user-confirmation]
-    work-unit.technical-analysis: [gate.design-reviewed, gate.openapi-frozen, gate.architecture-reviewed]
-  conditional_decisions: [scaffold-choice, external-input, new-authorization, risk-acceptance]
+    work-unit.spec-synthesis:
+      - gate.spec-baseline-approved
+    work-unit.prototype-design:
+      - gate.product-design-approved
+    work-unit.technical-analysis:
+      - gate.engineering-contract-approved
+  conditional_decisions: [ scaffold-choice, external-input, new-authorization, risk-acceptance ]
   waiting_allows: independent-work-only
   expiry: basis-change-or-revocation-only
   record_schema: docs/process/schemas/user-decision.schema.json

package/template/docs/agents/yss-skill-registry.yaml

@@ -214,12 +214,9 @@ invocation_contract:
       exclusion_conditions: [prototype-profile:H1, component-basis:not-antdv-next, production-frontend-implementation]
       primary_output: versioned-antdv-next-facts
 agent_runtime_roots:
-  claude: .claude/skills
   codex: .codex/skills
   cursor: .cursor/skills
   pi: .pi/skills
-  qoder: .qoder/skills
-  trae: .trae/skills
 skills:
   - id: alibaba-java-code-style
     layer: specialist

package/template/docs/api/templates/openapi-draft-review-checklist.md

@@ -10,6 +10,7 @@
 |---|---|---|
 | API 影响记录 / 契约草案 | issue note / design note / `docs/.scratch/<feature>/api/<feature>.yaml` |  |
 | OpenAPI Draft | `docs/.scratch/<feature>/api/<feature>.yaml` |  |
+| Draft validation record | `docs/.scratch/<feature>/api/<feature>-validation.yaml`；`scripts/verify-openapi-draft-validation-record` | 必须绑定当前 YAML SHA-256 与锁定 Redocly lint |
 | Spec / 需求冻结 |  |  |
 | 产品总体设计 / 功能架构 |  |  |
 | 交互说明 / 页面清单 | `docs/.scratch/<feature>/design/<feature>-interaction-spec.md` |  |
@@ -28,12 +29,20 @@
 |---|---|---|---|---|---|---|---|---|
 |  |  |  |  |  |  |  |  |  |
 
+## P0 字段级追踪矩阵
+
+> 只覆盖 P0 写模型、配置模型及影响关键交互的读模型。property path 必须落到嵌套字段，例如 `items[].schemaName`。
+
+| Spec / 交互来源 | operationId | Request / Response schema | Property path | 类型 / 嵌套形状 | Create / Update requiredness | Nullable / Default / Enum / Format | Error / Contract Test | 结论 |
+|---|---|---|---|---|---|---|---|---|
+|  |  |  |  |  |  |  |  |  |
+
 ## 门禁检查
 
 | Gate | Pass 条件 | 结论 | 备注 |
 |---|---|---|---|
 | Draft 成熟度 | 明确当前仅为 review-only；实现、生成 client、契约测试固化均等待 OpenAPI Freeze |  |  |
-| OpenAPI 语法 | YAML、`$ref`、path 参数、lint 通过 |  |  |
+| OpenAPI 语法 | validation record verifier 通过且 SHA 与当前 YAML 一致；单一 YAML document、`$ref`、path 参数、operationId、锁定 Redocly lint 均通过 |  | 缺标准 lint 时可做语义预审，但总结果必须 Blocked |
 | YAML 权威性 | 单一 OAS 3.1 document；未混入生命周期 frontmatter / 根字段；`operationId` 稳定 |  |  |
 | P0 覆盖 | 每个 P0 需求有 endpoint/schema/error/test 或明确非目标 |  |  |
 | 产品总体设计完整 | Draft 已依据 Spec 和产品总体设计 / 功能架构；缺产品总体设计时返回上游补齐 |  |  |
@@ -41,6 +50,8 @@
 | DDD 契约边界 | Endpoint/schema 归属的限界上下文清楚；术语与 `CONTEXT.md` 和功能架构一致；契约不直接暴露内部聚合、Repository 或持久化表结构 |  |  |
 | 页面动作覆盖 | 每个按钮 / 抽屉 / 弹窗动作有 endpoint/non-goal、`actionKey` 和错误码；Spec 明确认认证 / 授权变化时同时映射该行为 |  |  |
 | 对象生命周期 | manage/maintain/configure/create/update/archive/retry/cancel/publish/export/create-draft 语义闭环 |  |  |
+| 共享写模型 | create/update 等操作复用 schema 时，逐操作 requiredness 与省略语义一致；凭据明确创建、更新、掩码回显、omit=保留和 clear 语义 |  | 不硬编码所有 password 必填 |
+| P0 字段追踪 | 适用模型逐 property path 对齐来源、形状、requiredness、约束和 error/test seam |  |  |
 | YSS 响应包装 | 单对象 `SingleResult<T>`；列表 `MultiResult<T>`；分页 `PageResult<T>` |  |  |
 | DTO wire shape | `com.yss.cloud.dto.result` 为新契约 canonical；`data` 落成 endpoint-specific schema，Java 泛型文字不得成为 OAS type / `$ref`；响应使用 `x-yss-response-wrapper`、`YssResultMeta` 和 `allOf` |  |  |
 | 公共响应字段 | `success:boolean`；`dataType:string|null`；`code:string|integer|null`；`message/tips` 显式 nullable；不得把全局 `code` 放宽为 arbitrary object |  |  |
@@ -56,6 +67,13 @@
 
 ## 结论
 
+| 子结论 | 结论 | 证据 |
+|---|---|---|
+| Structural Validation | Passed / Blocked | validation record / YAML SHA / Redocly evidence |
+| Semantic Review | Passed / Blocked | P0 与字段级追踪矩阵 |
+
+只有两个子结论均为 `Passed` 时，总结论才能为 `Approved`。
+
 | 结论 | 勾选 |
 |---|---|
 | Approved for Engineering Baseline / Architecture Design |  |

package/template/docs/api/templates/openapi-draft-validation-record-template.yaml

@@ -0,0 +1,23 @@
+schema_version: 1
+kind: openapi-draft-validation
+template: true
+status: draft
+draft:
+  ref: docs/.scratch/example/api/example.yaml
+  sha256: sha256:0000000000000000000000000000000000000000000000000000000000000000
+  oas_version: 3.1.0
+toolchain:
+  package: "@redocly/cli"
+  version: 2.0.0
+  lockfile_ref: pnpm-lock.yaml
+  command: pnpm exec redocly lint docs/.scratch/example/api/example.yaml
+  exit_code: 1
+  executed_at: 2026-01-01T00:00:00Z
+  evidence_ref: docs/.scratch/example/api/example-redocly-lint.txt
+checks:
+  single_document: blocked
+  oas_3_1: blocked
+  ref_resolution: blocked
+  path_parameters: blocked
+  operation_ids: blocked
+  lint: blocked

package/template/docs/design/README.md

@@ -10,13 +10,6 @@
 - `docs/design/tokens/`：随仓库保存的主题、亮色 / 暗色 / 紧凑 token 和 CSS 变量快照，后续实现不得依赖本机 Downloads 目录或原始 Less。
 - 默认工作界面密度：`theme.json` 的 seed 叠加一次 compact algorithm，计算结果以 `tokens.compact.json` 和根 `DESIGN.md` 组件变体为准；暗色紧凑模式组合 dark 与 compact algorithm，禁止重复压缩。
 
-模板源维护工具（仅在 `template-source` 仓库执行）：
-
-```bash
-node .template-source/tooling/node/scripts/design-md.mjs lint DESIGN.md
-node .template-source/tooling/node/scripts/design-md.mjs drift
-```
-
 Token 或组件视觉变体变更必须先修改 `DESIGN.md`，再更新派生快照；治理说明不得复制具体值。业务状态、API、权限和交互验收继续使用 Spec、交互说明及状态矩阵。
 
 产品原型由 `yss-prototype-stage` 持有阶段合同：先评审低保真/状态矩阵，再选择 H1 视觉或 H2 流程，并按需调用 `product-design:index` focused workflow。YSS 生命周期负责校验档位选择、Prototype Evidence schema v4、Visual Baseline schema v1、统一 Design QA、用户确认和 Spec / OpenAPI 回填。原型阶段不得调用生产实现技能 `yss-ui`。

package/template/docs/design/design.md

@@ -9,17 +9,6 @@
 - 本文件：解释 YSS UI / Ant Design 双轨、页面设计约束、原型证据和生命周期门禁，不重新定义规范 token 的具体值。
 - Spec、交互说明和状态矩阵：继续承载业务状态、API、权限、并发、失败恢复和页面验收，不写入 `DESIGN.md`。
 
-## 规范校验
-
-模板源维护者在修改设计令牌后执行（项目实例不包含 `.template-source` 工具目录）：
-
-```bash
-node .template-source/tooling/node/scripts/design-md.mjs lint DESIGN.md
-node .template-source/tooling/node/scripts/design-md.mjs drift
-```
-
-`lint` 固定调用 `@google/design.md@0.4.0`，同时执行本地 frontmatter、章节、组件属性和引用校验；`drift` 检查规范源与全部 token/CSS 派生产物的哈希。任何漂移都必须回写规范源并重新生成投影。
-
 ## 来源与定位
 
 本文件基于本地设计系统包首次分析整理，并在后续用项目 Ant Design 5 Less / `:root` CSS 变量覆盖默认亮色主题。紧凑密度、间距和容器规格同时参考既有 YSS 实现。视觉 token 的规范源改为根目录 `DESIGN.md`；本文件和 `docs/design/tokens/*` 是治理说明与派生视图。外部目录只作为历史输入或实现样本，不作为后续工程依赖，也不作为实现语言。

package/template/docs/design/templates/prototype-review-checklist.md

@@ -58,7 +58,7 @@
 
 ```text
 结论：通过 / 阻断
-生命周期门禁：`gate.prototype-reviewed` 通过 / 不通过
+内部独立审查：`check.prototype-reviewed` 通过 / 不通过
 阻断项：
 - 
 非阻断建议：

package/template/docs/plan/entry-review.md

@@ -1,6 +1,6 @@
 # Plan → Spec 入口审阅
 
-正式 Spec 起草之前必须通过 `node scripts/verify-plan-spec-entry <state.yaml>`；显式 `to-spec`、恢复、任务包派发和下一路由均不得绕过。Plan 不通过时可继续无依赖调研，不创建正式 Spec 草稿。此检查复用 `plan-conclusion` 用户决定，不新增批准阶段，也不授权实现。
+正式 Spec 起草之前必须通过 `node scripts/verify-plan-spec-entry <state.yaml>`；显式 `to-spec`、恢复、任务包派发和下一路由均不得绕过。Plan 不通过时可继续无依赖调研，不创建正式 Spec 草稿。此检查复用 `gate.plan-approved` 用户决定，不新增批准阶段，也不授权实现。
 
 检查 ID 与条件门禁取自 `docs/process/lifecycle-registry.yaml` 的 `stage.plan.spec_entry`。查询 Plan 或相关工作单元自动加载 `planning`、`grill_exit` 和全量检查，初始均为 `pending`。自动加载不代表勾选通过。
 
@@ -10,14 +10,14 @@
 
 `plan_review_ref` 指向 YAML / JSON：
 
-- `schema_version: 1`、`kind: plan-entry-review`、与入口一致的 `feature_id`。
+- `schema_version: 1`、`kind: plan-entry-review`、`gate_id: gate.plan-approved`、与入口一致的 `feature_id`。
 - `plan_ref`：本次 Plan 正文；`context_reconciliation_ref`：本次已通过的 Context 调和记录。
 - `basis`：非空 `{ref, digest}` 列表，digest 为实际文件字节的 `sha256:` 摘要。必须包含 Plan 正文、根 `CONTEXT.md`、生命周期注册表、Context 调和记录及各检查和门禁引用的文件。远程事实先保存可追溯证据快照。
 - `checks`：注册表要求的全部检查 ID，每项包含 `status: pending | passed` 和非空 `evidence_refs`，引用 `basis`。必需检查不接受 `not-applicable`。缺项、未知项、pending 均阻断。
 - `open_items`：显式数组，空数组代表无未决项。每项有 `id`、`critical`、`runnable_blocker`、`status` 和 `evidence_refs`。影响业务边界、关键规则或 MVP 的问题属于 critical。`resolved` 须有解决证据；仅非关键、非可执行阻塞项可 `deferred`，并填写 `noncritical_reason`、`owner`、`resolution_point`、`downstream_recipient`。延期内容随整个审阅包展示并取得用户确认。
 - `impacts`：显式评估 `domain_strategy`（领域边界、词汇、协作或核心规则影响）和 `stage_decision`（需要稳定阶段决策合同）。证据和判断必须呈现给用户；缺值不解释为 false。
-- `gates`：注册表 Plan 门禁全部逐项记录。命中项须 `status: approved`、`approval_ref`、`subject_ref`、`approval_scope`、`evidence_refs`，会签记录及对应资产均加入 `basis`；未命中项须 `status: not-applicable`、`reason`、`evidence_refs`，并由用户确认影响面判断。阶段决策门禁的上游依赖必须批准，不能用 N/A 跳过。
+- `internal_checks`：注册表 `check_impacts` 内部专业审查全部逐项记录。命中项须 `status: approved`、`approval_ref`、`subject_ref`、`approval_scope`、`evidence_refs`，会签记录及对应资产均加入 `basis`；未命中项须 `status: not-applicable`、`reason`、`evidence_refs`，并由用户确认影响面判断。阶段决策检查的上游依赖必须批准，不能用 N/A 跳过。
 
-先固定审阅包及依据，展示当前内容、范围、风险、延期、N/A 理由和下一动作，再取得真实用户回复。`plan_user_decision_ref` 采用 `docs/process/schemas/user-decision.schema.json`：边界为 `plan-conclusion`，subject 为当前 `plan_review_ref`，scope 包含当前 `feature_id`。不得将旧“继续”、数字人会签或合成测试回复当作本次批准。
+先固定审阅包及依据，展示当前内容、范围、风险、延期、N/A 理由和下一动作，再取得真实用户回复。`plan_user_decision_ref` 采用 `docs/process/schemas/user-decision.schema.json`：边界为 `gate.plan-approved`，subject 为当前 `plan_review_ref`，scope 包含当前 `feature_id`。不得将旧“继续”、数字人会签或合成测试回复当作本次批准。
 
 审阅包、注册表、Plan、词汇、依据或批准来源变化均要求重新校验；摘要漂移时重新展示并取得当前确认。检查器保证结构、引用、摘要和回复绑定，不证明业务事实或身份来源绝对真实；主控仍须按证据核查影响面，不能为了放行而填 false 或空问题列表。

package/template/docs/process/MATT-POCOCK-ENGINEERING-SKILLS.md

@@ -4,6 +4,7 @@ Matt Pocock Engineering Skills 提供轻量的澄清、实现、TDD、诊断和
 
 ## 进入与退出
 
+- `triage` 是显式 Issue / PR 兼容入口；普通请求由 `yss-product-lifecycle` 的 `request_triage` 合同处理。其 YSS 适配只回交取证、简报和状态建议；简报不替代批准的切片合同，状态调整由生命周期核验。详细规则见 [请求分诊协议](../../.agents/skills/yss-product-lifecycle/references/request-triage.md)。
 - Matt user-invoked 的 `grill-with-docs`、`to-spec`、`to-tickets` 和 `implement` 必须由用户显式启动，任何 skill 不得自动调用它们；YSS 生命周期只准备、校验和验收其结果。所有 Matt model-invoked skill 仍须遵守 `AGENTS.md` 的阶段、门禁和证据要求，并只能在生命周期允许的工作单元中调用。
 - `code-review` 保持唯一默认审查入口。YSS 适配把 Slice `required_skills`、`alibaba-java-code-style` 与命中的 `yss-ui` / `yss-domain` 等专项 skill 编译为 Standards 检查输入，并要求实现仓已有的 `pnpm` / `./mvnw` 机器检查；禁止再增加第二个通用审查 skill 或专用审查 Cloud 环境来代替这条接线。审查 finding 按编排合同分流：实现者修复后全轴复审，或合同 `stale` 后回 实现合同编译器；审查者不得写实现。
 - `template-source` 只执行模板维护流程，不生成具体产品 Spec、原型、OpenAPI 或垂直切片 Ticket。