create-yss-spec 3.0.0 → 3.1.0

package/template/DESIGN.md

@@ -1,24 +1,30 @@
 ---
 version: alpha
 name: YSS Enterprise Design System
-description: A machine-readable visual design contract for YSS enterprise applications. It complements the product lifecycle and does not define product behavior, API contracts, permissions, or business states.
+description: A machine-readable compact visual contract for YSS enterprise applications, aligned with Ant Design v6 semantic tokens and the experimental Antdv Next provider. It complements the product lifecycle and does not define product behavior, API contracts, permissions, or business states.
 
 colors:
   primary: "#3371ff"
-  primary-hover: "#5c8dff"
-  primary-active: "#245bdb"
-  on-primary: "#000000"
+  primary-control: "#245bdb"
+  primary-control-hover: "#2f68eb"
+  primary-active: "#0958d9"
+  primary-bg: "#e6f4ff"
+  on-primary: "#ffffff"
   text: "rgba(0, 0, 0, 0.88)"
   text-secondary: "rgba(0, 0, 0, 0.65)"
   text-tertiary: "rgba(0, 0, 0, 0.45)"
   canvas-layout: "#f0f2f5"
   surface: "#ffffff"
+  surface-elevated: "#ffffff"
   surface-subtle: "#fafafa"
   border-secondary: "#f0f0f0"
   success: "#52c41a"
+  success-bg: "#f6ffed"
   warning: "#faad14"
+  warning-bg: "#fffbe6"
   error: "#f5222d"
-  selected: "#e6f4ff"
+  error-bg: "#fff2f0"
+  info-bg: "#e6f4ff"
 
 typography:
   body:
@@ -70,134 +76,172 @@ spacing:
 
 components:
   button-primary:
-    backgroundColor: "{colors.primary}"
+    backgroundColor: "{colors.primary-control}"
     textColor: "{colors.on-primary}"
     typography: "{typography.button}"
     rounded: "{rounded.md}"
-    padding: "{spacing.xs} {spacing.md}"
-    height: 32px
+    padding: "{spacing.xxs} {spacing.sm}"
+    height: 28px
   button-primary-hover:
-    backgroundColor: "{colors.primary-hover}"
+    backgroundColor: "{colors.primary-control-hover}"
     textColor: "{colors.on-primary}"
     typography: "{typography.button}"
     rounded: "{rounded.md}"
-    padding: "{spacing.xs} {spacing.md}"
-    height: 32px
+    padding: "{spacing.xxs} {spacing.sm}"
+    height: 28px
   button-primary-disabled:
     backgroundColor: "{colors.border-secondary}"
     textColor: "{colors.text-tertiary}"
     typography: "{typography.button}"
     rounded: "{rounded.md}"
-    padding: "{spacing.xs} {spacing.md}"
-    height: 32px
+    padding: "{spacing.xxs} {spacing.sm}"
+    height: 28px
   button-default:
     backgroundColor: "{colors.surface}"
     textColor: "{colors.text}"
     typography: "{typography.button}"
     rounded: "{rounded.md}"
-    padding: "{spacing.xs} {spacing.md}"
-    height: 32px
+    padding: "{spacing.xxs} {spacing.sm}"
+    height: 28px
   input-default:
     backgroundColor: "{colors.surface}"
     textColor: "{colors.text}"
     typography: "{typography.body}"
     rounded: "{rounded.md}"
-    padding: "{spacing.xs} {spacing.sm}"
-    height: 32px
+    padding: "{spacing.xxs} {spacing.xs}"
+    height: 28px
   input-error:
     backgroundColor: "{colors.surface}"
     textColor: "{colors.text}"
     typography: "{typography.body}"
     rounded: "{rounded.md}"
-    padding: "{spacing.xs} {spacing.sm}"
-    height: 32px
+    padding: "{spacing.xxs} {spacing.xs}"
+    height: 28px
   table-header:
     backgroundColor: "{colors.surface-subtle}"
     textColor: "{colors.text}"
     typography: "{typography.body-strong}"
     padding: "{spacing.xs} {spacing.sm}"
   table-row-selected:
-    backgroundColor: "{colors.selected}"
+    backgroundColor: "{colors.primary-bg}"
     textColor: "{colors.text}"
     typography: "{typography.body}"
     padding: "{spacing.xs} {spacing.sm}"
   modal-default:
-    backgroundColor: "{colors.surface}"
+    backgroundColor: "{colors.surface-elevated}"
     textColor: "{colors.text}"
     typography: "{typography.body}"
     rounded: "{rounded.lg}"
     padding: "{spacing.md}"
   button-primary-active:
     backgroundColor: "{colors.primary-active}"
-    textColor: "#ffffff"
+    textColor: "{colors.on-primary}"
     typography: "{typography.button}"
     rounded: "{rounded.md}"
-    padding: "{spacing.xs} {spacing.md}"
-    height: 32px
+    padding: "{spacing.xxs} {spacing.sm}"
+    height: 28px
   page-shell:
     backgroundColor: "{colors.canvas-layout}"
     textColor: "{colors.text}"
     typography: "{typography.body}"
     padding: "{spacing.md}"
   alert-success:
-    backgroundColor: "{colors.success}"
-    textColor: "#000000"
+    backgroundColor: "{colors.success-bg}"
+    textColor: "{colors.text}"
     typography: "{typography.body}"
     rounded: "{rounded.sm}"
     padding: "{spacing.xs} {spacing.sm}"
   alert-warning:
-    backgroundColor: "{colors.warning}"
-    textColor: "#000000"
+    backgroundColor: "{colors.warning-bg}"
+    textColor: "{colors.text}"
     typography: "{typography.body}"
     rounded: "{rounded.sm}"
     padding: "{spacing.xs} {spacing.sm}"
   alert-error:
-    backgroundColor: "{colors.error}"
-    textColor: "#000000"
+    backgroundColor: "{colors.error-bg}"
+    textColor: "{colors.text}"
+    typography: "{typography.body}"
+    rounded: "{rounded.sm}"
+    padding: "{spacing.xs} {spacing.sm}"
+  alert-info:
+    backgroundColor: "{colors.info-bg}"
+    textColor: "{colors.text}"
     typography: "{typography.body}"
     rounded: "{rounded.sm}"
     padding: "{spacing.xs} {spacing.sm}"
+  badge-processing-solid:
+    backgroundColor: "{colors.primary}"
+    textColor: "#000000"
+    typography: "{typography.caption}"
+    rounded: "{rounded.sm}"
+    padding: "{spacing.xxs} {spacing.xs}"
+  badge-success-solid:
+    backgroundColor: "{colors.success}"
+    textColor: "#000000"
+    typography: "{typography.caption}"
+    rounded: "{rounded.sm}"
+    padding: "{spacing.xxs} {spacing.xs}"
+  badge-warning-solid:
+    backgroundColor: "{colors.warning}"
+    textColor: "#000000"
+    typography: "{typography.caption}"
+    rounded: "{rounded.sm}"
+    padding: "{spacing.xxs} {spacing.xs}"
+  badge-error-solid:
+    backgroundColor: "{colors.error}"
+    textColor: "#000000"
+    typography: "{typography.caption}"
+    rounded: "{rounded.sm}"
+    padding: "{spacing.xxs} {spacing.xs}"
   secondary-copy:
     textColor: "{colors.text-secondary}"
     typography: "{typography.caption}"
+  card-compact:
+    backgroundColor: "{colors.surface}"
+    textColor: "{colors.text}"
+    typography: "{typography.body}"
+    rounded: "{rounded.lg}"
+    padding: "{spacing.md}"
 
 ---
 
-# Overview
+## Overview
 
 YSS is an enterprise UI system for dense, scannable work surfaces: tables, forms, filters, workflows and operational feedback. This file is the normative source for visual tokens and component visual variants. Product behavior remains in Spec, interaction specifications and state matrices.
 
-The visual baseline is Ant Design semantic tokens mapped to YSS UI. Production applications use Vue 3 + YSS UI / Ant Design Vue 4.x; high-fidelity prototypes use React + Ant Design 6.x. Both tracks consume the same semantic intent.
+The visual baseline is Ant Design v6 semantic tokens mapped to YSS UI. Production applications use Vue 3 + YSS UI / Ant Design Vue 4.x; high-fidelity React prototypes use Ant Design 6.x, while experimental Vue prototypes may use the draft Antdv Next provider against an exact-version fact pack. These tracks share visual intent, not framework APIs.
 
-# Colors
+## Colors
 
 Use semantic roles (`primary`, `text`, `surface`, `border`, `success`, `warning`, `error`) instead of literal values in product pages. Keep a single primary action per decision area. State colors must be paired with readable text or an icon and must meet WCAG 2.2 AA.
 
-# Typography
+## Typography
 
 Use the system font stack, 14px body text and 400/600 weights. Use `caption` only for supporting information; do not encode business status through weight alone.
 
-# Layout
+## Layout
 
-Use a 4px spacing grid and the spacing tokens above. Default controls are 32px high. Page, container and overlay surfaces form the base three-layer model. On narrow screens, toolbars and filters reflow or collapse; table overflow is restricted to the table container.
+Use a 4px spacing grid and the spacing tokens above. Keep the Ant Design seed `controlHeight` at 32px, then apply the compact algorithm once; the default prototype and dense-work-surface result is 28px. Never seed 28px and apply compact again. Page, container and overlay surfaces form the base three-layer model. On narrow screens, toolbars and filters reflow or collapse; table overflow is restricted to the table container.
 
-# Elevation & Depth
+## Elevation & Depth
 
 Prefer surface and border changes over decorative shadows. Use the component library elevation tokens when available. Shadow values remain an implementation detail until the upstream DESIGN.md schema provides a stable structured elevation contract.
 
-# Shapes
+## Shapes
 
 Controls use `rounded.md` (6px); cards and overlays use `rounded.lg` (8px); compact tags may use `rounded.sm` or `rounded.pill`. A container radius must not be smaller than the radius of its child controls.
 
-# Components
+## Components
 
-The component keys above describe visual variants, not business states. Required implementation states include hover, focus, active, disabled, loading, error, empty, readonly, no-permission, conflict and success. Define those behavior and acceptance details in the lifecycle state-matrix and prototype evidence assets.
+The component keys above describe compact visual variants, not business states. Controls use a 28px computed height, 14px body type, pale semantic feedback surfaces and visible focus rings. Required implementation states include hover, focus, active, disabled, loading, error, empty, readonly, no-permission, conflict and success. Define those behavior and acceptance details in the lifecycle state-matrix and prototype evidence assets.
 
-# Do’s and Don’ts
+## Do's and Don'ts
 
 - Do consume tokens through ConfigProvider, CSS variables or the target component library theme.
+- Do compose `compactAlgorithm` with `darkAlgorithm` for dark compact work surfaces.
 - Do verify desktop (`1440x900`), mobile (`390x844`) and impacted intermediate viewports.
 - Do provide visible feedback for save, submit, publish, export and retry actions.
 - Don’t use marketing hero layouts, large gradients or decorative cards in operational pages.
 - Don’t hard-code colors, arbitrary spacing or duplicate controls that already exist in YSS UI.
+- Don’t target component-library internal DOM or generated class names; v6 internal markup is not a stable contract.
 - Don’t use a Tag as the only representation of an error, permission or approval state.

package/template/README.md

@@ -13,7 +13,6 @@
 ├── .claude/                 ← Claude skills 投影与平台专属 skills
 ├── .codex/                  ← Codex skills 投影与平台专属 skills
 ├── .cursor/                 ← Cursor skills 投影
-├── .hermes/                 ← Hermes skills 投影与平台专属 skills
 ├── .pi/                     ← Pi skills 投影与平台专属 skills
 ├── .qoder/                  ← Qoder skills 投影与平台专属 skills
 ├── .trae/                   ← Trae skills 投影与平台专属 skills

package/template/__yss_dotfile__.gitignore

@@ -41,3 +41,4 @@ output
 docs/process/presentations/
 docs/process/yss-product-lifecycle-team-guide.md
 docs/graphify-out
+docs/.scratch/

package/template/docs/agents/backend-architecture-profiles.md

@@ -0,0 +1,25 @@
+# 后端架构 Profile 执行约定
+
+Profile、模块闭包、生成器、成熟度和 Recipe 的权威映射见 `yss-skill-registry.yaml`。本文件只定义分层执行边界，不从目录名推断架构。
+
+执行前比较工程基线、仓库登记、Manifest 与当前合同的 `architecture_identity`。缺失、digest 漂移、Profile 不匹配或越界写路径均停止；既有工程不能自动重选架构。新 Profile 的真实编译及首切片验证未通过前保持 `draft`，不能设置 `ready-for-agent`。
+
+## MVC 分层
+
+- `layered-mvc-service` 的用例层为 `service`；`mvc-data-analysis-v1` 的用例层为 `core`。后者是薄应用层，不是合并 Domain 的容器。MVC 不加载 `yss-domain`，不生成 DDD Gateway。
+- 用例层拥有事务、业务规则、幂等和内部 Command / Query / Result；可依赖 Spring Context / `spring-tx`，不依赖 Spring MVC、HTTP client DTO 或数据库驱动。Controller 不直连 Repository。
+- Repository 拥有 PO、MyBatis-Plus Repository / XML 及持久化转换；不得反向依赖 service/core/server/client。数据库操作的因果异常应保留，禁止把内部错误原文输出给客户端。
+- Adapter 拥有外部系统适配，Feign client 只承载远程调用契约。不得把 Repository 当作对外集成层。
+- 私有 HTTP DTO 在 server；启用 published-client 时公开 DTO 可在 client；数据分析 Profile 的公开 DTO 固定在 client。client 不依赖 service/core/repository/server。server 用 MapStruct 在 wire DTO 与内部模型之间转换；core 不依赖 client。
+- Bean Validation 在 server/client 的输入边界；业务校验及稳定错误语义在 service/core；HTTP 状态、包装和脱敏在 server。事务回滚、校验失败、已知/未知异常和序列化必须有行为测试。
+
+## 数据库与 Java 基线
+
+- 新脚手架统一 `verification_database=h2`、`production_database=not-bound`。仅测试和显式 `scaffold-local` 使用 H2；普通配置不设置数据库或默认激活 Profile。不另加生产驱动、第三方数据源或 Mock 服务。
+- 生产数据库、DDL、索引和方言在后续批准的存储工作单元接入；H2 测试不能证明生产方言兼容。脚手架不包含业务 SQL、schema/data 占位或业务 API。
+- 三种新 Profile 使用 `spring-boot-2.7-jdk8` / `javax`。组件 Skill 消费工程基线，不擅自升级 Java、Boot、处理器版本或替换依赖。MapStruct + Lombok 必须验证 binding 与生成代码编译。
+- 对 SQL 注入、敏感信息、权限和事务的规则不因 H2 或模板而豁免。MySQL 专属语法规则仅适用于批准的 MySQL 存储工作单元；框架命名/返回包装等差异须记录明确的 YSS 基线例外。
+
+## 验证含义
+
+结构测试只证明分流/生成约束。三种 Profile 各自需要临时 `CompatibilityProbe` 的真实 Maven validate/test/package 与首切片端到端证据才能声明受支持。Probe 不进入分发骨架。用户工程空骨架验证成功最多为 `empty-scaffold-verified`，不能替代自身批准的首切片验证。

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

@@ -1,6 +1,6 @@
 # 数字人角色
 
-结构化事实源是 `docs/agents/digital-human-roles.yaml`。角色、技能、协作组和会签级别与运行时无关。Claude Code、Cursor、Codex、Hermes、Grok Bot 等只通过 YAML `runtimes` 绑定。冲突时以 YAML 为准。
+结构化事实源是 `docs/agents/digital-human-roles.yaml`。角色、技能、协作组和会签级别与运行时无关。Claude Code、Cursor、Codex、Grok Bot 等只通过 YAML `runtimes` 绑定。冲突时以 YAML 为准。
 
 ## 何时读本文
 
@@ -16,7 +16,7 @@
 | 执行态 | Explorer / Drafter / Worker / Reviewer / Verifier | 数字人角色 |
 | 运行时绑定 | 如何在 Cursor / Claude / 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 交实现者修复或回 Router，审查者不得当场改代码。任务包 canonical Schema 为 `docs/process/schemas/digital-human-task-package.schema.json`，按 `contract.kind` 选择生命周期、切片实现或模板维护合同。
+一次数字人任务包同时写明 `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` 选择生命周期、切片实现或模板维护合同。
 
 ## 会签人
 
@@ -31,14 +31,14 @@
 | `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` | — | `role.product-manager`；生物人可否决 |
+| `gate.user-confirmation` | 产品数字人提供建议 | 提问者或其明确指定的生物人负责人 |
 | `gate.release-ready` | — | 生物人（`role.biological-human`） |
 
 未列入表的门禁（含 `gate.design-reviewed`、`gate.architecture-reviewed`）走 `default_if_unlisted: biological-human`。
 
-会签写入 `docs/.scratch/<feature>/gates/<gate-id>-approval.yaml`，形状见 `docs/templates/approval-record-template.yaml`。恢复前运行 `scripts/verify-approval-record`。错误会签只能得到 `blocked`，不能把门禁标成 `approved`。Checkpoint 里会签桶门禁为 `approved` 时必须有可读 `approval_ref`。
+会签写入 `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`。
 
-`paused-human-gate` 表示等待上述指定会签人，不是「必须是生物人」。
+`paused-human-gate` 表示等待指定会签人；`user_decision_policy` 命中的关键决定同时强制真实用户回复，数字人审查不能代答。请求展示、原始回复证据、复用和恢复规则见 [用户决定协议](../../.agents/skills/yss-product-lifecycle/references/user-decisions.md)。
 
 主控默认兼任项目经理，直到 `dual_hat_split_when`（`cross-repo-load` 或 `responsibility-conflict`）要求分体。
 
@@ -57,7 +57,7 @@
 | ID | 覆盖 | 落地方式 |
 |---|---|---|
 | `runtime.generic` | 任何能加载 `core_skills` 并接受任务包的 Agent | 通用会话 / 人设 / system prompt |
-| `runtime.skill-projection` | `yss-skill-registry.yaml` 的 `agent_runtime_roots`（claude、codex、cursor、hermes、pi、qoder、trae） | 投影技能 + subagent 任务包 |
+| `runtime.skill-projection` | `yss-skill-registry.yaml` 的 `agent_runtime_roots`（claude、codex、cursor、pi、qoder、trae） | 投影技能 + subagent 任务包 |
 | `runtime.grok` | Grok Bot | 持久 Bot、群聊或 1:1 交接；群超过 6 人改 1:1，不改逻辑协作组 |
 
 新增平台：先加 `runtimes` 条目，再写适配说明。不要把平台限制写进 `roles`。

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

@@ -44,7 +44,7 @@ runtimes:
     side_effect_approval: biological-human
     notes: >-
       覆盖 docs/agents/yss-skill-registry.yaml 的 agent_runtime_roots
-      （claude / codex / cursor / hermes / pi / qoder / trae）。
+      （claude / codex / cursor / pi / qoder / trae）。
       技能仍从 .agents/skills 投影，不按职称再维护一份。
   - id: runtime.grok
     kind: grok-bot
@@ -68,8 +68,8 @@ orchestrator:
   title: YSS 生命周期主控
   default_dual_hat: [role.project-manager]
   stages: [stage.entry-triage, stage.discovery, 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-router]
-  forbidden_skills: [yss-domain, yss-ui, yss-page-module-development, yss-web-controller, yss-repository, implement]
+  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
@@ -87,7 +87,7 @@ roles:
     stages: [stage.discovery, stage.spec-architecture]
     draft_artifact_ids: [artifact.discovery-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-frontend-scaffold-generator, implement, tdd]
+    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 Discovery language, users, MVP, non-goals, success criteria, test
       seams, and Spec prose. Propose CONTEXT.md glossary entries. Do not freeze
@@ -101,8 +101,8 @@ roles:
     title: YSS 产品经理
     stages: [stage.discovery, 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-antd-design, yss-research, competitive-intelligence]
-    forbidden_skills: [yss-ui, yss-domain, yss-repository, yss-web-controller, yss-ddd-scaffold-generator, implement, tdd]
+    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
@@ -111,7 +111,8 @@ roles:
       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-antd-design.
+      yss-antdv-next-design. Explicit React/AntD compatibility prototypes use
+      yss-antd-design conditionally.
 
   - id: role.project-manager
     name: 项目经理
@@ -137,8 +138,8 @@ roles:
     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-page-module-development, 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, java-backend-commit]
+    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
@@ -152,8 +153,8 @@ roles:
     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]
-    core_skills: [yss-router, yss-tactical-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]
-    forbidden_skills: [yss-ui, yss-page-module-development, yss-formily, yss-frontend-scaffold-generator, yss-antd-design, page-list-module, page-form-module]
+    core_skills: [yss-implementation-contract-compiler, yss-tactical-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
@@ -168,8 +169,8 @@ roles:
     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-page-module-development, yss-domain, yss-application, yss-repository, yss-web-controller, yss-dto, mapstruct, lombok]
-    forbidden_skills: [yss-ddd-scaffold-generator, yss-frontend-scaffold-generator, implement, to-spec]
+    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
@@ -248,9 +249,41 @@ gate_policy:
     - gate: gate.openapi-frozen
       drafter: role.backend-engineer
       countersigners: [role.product-manager, role.test-engineer]
-  product_digital_human_with_biological_veto:
-    - gate.user-confirmation
+  product_digital_human_with_biological_veto: []
   biological_human:
+    - gate.user-confirmation
     - gate.release-ready
   runtime_side_effect_approval: biological-human
   commercial_contract: biological-human
+
+# 用户决定是关键业务/授权条件；不替代数字人专业审查，不新增 gate。
+user_decision_policy:
+  schema_version: 1
+  default_responder: requester
+  delegate_requires_requester_evidence: true
+  source_kinds: [platform-message, session-export, user-confirmation-file]
+  gates:
+    - gate.domain-strategy-approved
+    - gate.stage-decision-package-approved
+    - gate.spec-baseline-approved
+    - gate.user-confirmation
+    - gate.openapi-frozen
+    - gate.design-reviewed
+    - gate.architecture-reviewed
+    - gate.release-ready
+  work_units:
+    work-unit.discovery-requirements: discovery-conclusion
+    work-unit.service-project-initialization: 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]
+  waiting_allows: independent-work-only
+  expiry: basis-change-or-revocation-only
+  record_schema: docs/process/schemas/user-decision.schema.json
+  verifier: scripts/verify-user-decision

package/template/docs/agents/domain.md

@@ -1,10 +1,10 @@
-# 领域文档
+# 业务词汇与决策文档
 
-本文规定 Engineering Skills 在探索仓库、起草 Ticket、设计架构或实施代码前，如何读取和使用领域文档。
+本文规定 Engineering Skills 在探索仓库、起草 Ticket、设计架构或实施代码前，如何读取和使用业务词汇与决策文档。
 
 ## 文档布局
 
-本仓库采用单上下文布局：
+本仓库只维护一份根业务词汇表：
 
 ```text
 /
@@ -17,14 +17,15 @@
 
 根据任务影响范围读取：
 
-- `CONTEXT.md`：领域术语和统一语言。
+- 根目录唯一的 `CONTEXT.md`：流程术语、业务术语和统一业务词汇；禁止按业务责任区重复创建。
 - `docs/adr/`：与当前任务相关的架构决策。
 
-如果文件尚不存在，继续执行即可，不需要将缺失本身报告为问题。`domain-modeling` skill 会在形成稳定术语或架构决策时按需创建或更新领域文档。
+`CONTEXT.md` 缺失时必须先恢复该合同；`domain-modeling` skill 会在形成稳定术语或关键决策时按需更新业务词汇或 ADR。
 
 ## 使用规则
 
 - 在 Spec、Ticket 标题、测试、架构说明和实施总结中使用 `CONTEXT.md` 定义的中文术语。
 - 业务术语必须同时有 PascalCase `英文标识`；代码类型 / 字段与契约 property 使用该词干按 `CONTEXT.md` 文首规则变形。不把具体类全名、表名或接口路径写入词汇表。
-- `CONTEXT.md` 是领域词汇表，不是需求或实现规格；临时计划和未确认猜测不写入。
+- `CONTEXT.md` 是业务词汇表，不是需求或实现规格；临时计划和未确认猜测不写入。
+- 业务术语身份固定为 `<ContextId>/<EnglishIdentifier>`；`ContextId` 来自已确认的业务责任区，跨责任区共享才使用 `Global`。生命周期资产只保存结构化 snapshot 与双摘要，不使用 Markdown 标题锚点冒充可解析引用。
 - 如果提案与现有 ADR 或已冻结术语冲突，必须在继续执行前明确指出冲突。

package/template/docs/agents/skill-migrations.md

@@ -2,15 +2,46 @@
 
 本文记录已退役技能入口的迁移路径。退役技能不保留物理目录、投影或 lock 条目；本文件是历史名称的唯一持久兼容说明。
 
+## 技能面收敛与前端入口合并（2026-09-05）
+
+以下 Skill 已一次性硬退役，不保留 alias、兼容目录、投影或 lock 条目：
+
+- 通用路由与维护工具：`ask-matt`、`dispatching-parallel-agents`、`loop-me`、`migrate-to-shoehorn`、`scaffold-exercises`、`setup-pre-commit`、`setup-ts-deep-modules`、`teach`、`writing-beats`、`writing-fragments`、`writing-shape`。
+- 前端重复或失效入口：`prototype-page-acceptance`、`yss-page-module-development`（及旧名 `page-module-development`）、`yss-microapp-commit`（及旧名 `microapp-commit`）。
+
+新工作迁移到：
+
+- 通用生命周期路由直接使用 `yss-product-lifecycle`；并行执行遵循 `docs/process/subagent-collaboration.md` 和运行时原生协调能力。
+- 前端业务页面统一使用 `yss-ui` + `yss-ui-business-page-generation`，按影响面加载组件、Formily、表格、树、API、主题和高度专项 Skill。
+- 原型还原使用批准且摘要当前的 Visual Baseline、`frontend_implementation_plan` 与 `frontend_implementation_verification`；只做 type-check 不构成还原通过。
+- 前端与微应用提交统一使用 `frontend-commit`，scope 以仓库真实规则和业务模块为准，不再按目录机械映射。
+- 已退役的个人工作流、教学、练习、写作实验和 Shoehorn 专项迁移能力不再随 YSS 模板分发；需要时由使用者在目标仓库单独安装。
+
+历史冻结证据和候选快照继续只读保留。活跃 Registry、Recipe、任务包、模板、脚本和文档不得再把这些 ID 作为正向输入。
+
+## 实现合同与源码索引技能硬替换（2026-09-04）
+
+`yss-router` 已由 `yss-implementation-contract-compiler` 硬替换；`yss-source-index` 已由 `yss-skill-source-index-refresh` 硬替换。两个旧 ID 不保留 alias、兼容目录、投影或 lock 条目，也不能作为 Recipe、合同、模板或脚本的正向输入。
+
+同步升级内容：
+
+- 技能注册表和调用者使用新 canonical ID；Registry、编译器合同、Slice Implementation Contract 与 YSS Skill Execution Result 使用 schema v2。
+- Recipe 只引用 dotted capability；类型化依赖只由 `docs/agents/yss-skill-registry.yaml` 持有。
+- 旧 schema v1 输入明确拒绝并返回迁移提示，不自动升级。
+- 历史冻结证据和不可变候选快照不改写。旧 ID 仅可继续出现在本迁移记录、`OBSOLETE` 阻断集合及负向测试中。
+
 ## high-fidelity-html-prototype
 
-`high-fidelity-html-prototype` 已退役，不再作为 Router alias、默认发现入口或独立物理技能存在。
+`high-fidelity-html-prototype` 已退役，不再作为 实现合同编译器 alias、默认发现入口或独立物理技能存在。
 
-迁移到：
+新工作迁移到：
 
 - 阶段合同：`yss-prototype-stage`
-- Codex 产品设计主入口：`product-design:index`
-- Ant Design v6 事实与 CLI 证据：`yss-antd-design`
+- 原型档位与主入口：`yss-prototype-stage` 的 H1/H2 路由
+- Codex 产品设计能力：按档位条件使用 `product-design:index`
+- Antdv Next 精确版本事实：默认 H2 使用 `yss-antdv-next-design`
+- Ant Design v6 事实与 CLI：仅显式 React 兼容 H2 使用 `yss-antd-design`
+- 真实组件核验：不属于原型档位；进入已批准切片后由 `yss-ui` 基于目标 lockfile 执行，并写入前端实现验证
 - 独立低保真评审：`prototype-review`
 
-迁移时保留原型评审记录、AntD CLI 验证、浏览器验证和用户确认，并由 `yss-product-lifecycle` 裁决 `gate.prototype-reviewed`、`gate.prototype-verified` 和 `gate.user-confirmation`。不得创建同名兼容目录。
+已关闭的 Prototype Evidence schema v1/v2/v3、旧 artifact ID、AntD CLI、浏览器验证和确认记录只读保留。在途 UI 工作迁移到 Prototype Evidence schema v4、Visual Baseline schema v1 与 `artifact.prototype-deliverable` 后再关闭门禁；无 UI 影响不创建空包。不得创建同名兼容目录或删除历史证据。

package/template/docs/agents/skills-maintenance.md

@@ -5,9 +5,9 @@
 ## 权威内容与投影
 
 - `.agents/skills` 是跨 Agent 共享技能的唯一权威内容。
-- `.claude/skills`、`.codex/skills`、`.cursor/skills`、`.hermes/skills`、`.pi/skills`、`.qoder/skills`、`.trae/skills` 中的同名共享技能是生成投影，不得分别手工修改。
+- `.claude/skills`、`.codex/skills`、`.cursor/skills`、`.pi/skills`、`.qoder/skills`、`.trae/skills` 中的同名共享技能是生成投影，不得分别手工修改。
 - Cursor 的契约运行时入口是 `.cursor/skills`。若客户端同时枚举 `.claude/skills`，仍以 `.cursor/skills` 为 Cursor 投影契约，不得把两套同名 skill 解释为两个来源。
-- 分层、别名和默认可发现性以 `docs/agents/yss-skill-registry.yaml` 为准；当前 registry 为 `active`，Router、生命周期编排器和实例发现面必须消费通过校验的 canonical 技能及其 alias 解析结果。
+- 分层、别名和默认可发现性以 `docs/agents/yss-skill-registry.yaml` 为准；当前 registry 为 `active`，实现合同编译器、生命周期编排器和实例发现面必须消费通过校验的 canonical 技能及其 alias 解析结果。
 - 只属于某个平台的 skill 继续保留在对应 root，并由 `skills-lock.json` 的 `platform` 分组记录。
 - 共享技能投影可以是指向权威目录的符号链接，也可以是完整同步副本；`scripts/sync-skills --check` 会检查链接目标或完整目录哈希。
 
@@ -29,9 +29,9 @@
 
 项目允许按 YSS 流程适配上游 skill，但必须同时保留可追溯的上游信息和适配后的有效哈希。
 
-当前 Matt 快照为 `0ab1b63a410a03d3627979a109c8695de27af954`。`ask-matt` 的关联入口包括 `to-questionnaire`、`wait-what`、`writing-for-agents` 和 `PHASE-BOUNDARIES.md`；这些支持文件随共享 skill 目录一起计算 `effectiveHash`，不得单独投影或维护。
+当前 Matt 快照为 `0ab1b63a410a03d3627979a109c8695de27af954`。模板按 YSS capability 白名单收录上游 Skill；已退役的通用路由、个人工作流、教学、练习、写作实验和专项迁移 Skill 不再随 project-instance 分发。
 
-本轮升级还将生命周期适配固定为：阶段边界只写可选 `phase_boundary` 证据；`to-questionnaire` 使用 `external-input-required` 暂停并在答案回流后重新分类影响面；Matt `prototype` 使用 `prototype/<name>` 分支和单文件 HTML，YSS 高保真原型继续执行 Prototype Review、AntD CLI 校验和用户确认。人工 checkpoint 与 `diagnosing-bugs` 的输出必须脱敏，`wait-what` 不改变生命周期状态。
+本轮升级还将生命周期适配固定为：阶段边界只写可选 `phase_boundary` 证据；`to-questionnaire` 使用 `external-input-required` 暂停并在答案回流后重新分类影响面；Matt `prototype` 的单文件 HTML 只作为回流输入，YSS 原型仍须完成低保真评审、H1/H2 档位路由、Prototype Evidence schema v4、Visual Baseline schema v1 验证和用户确认。人工 checkpoint 与 `diagnosing-bugs` 的输出必须脱敏，`wait-what` 不改变生命周期状态。
 
 ## 维护流程
 
@@ -94,7 +94,7 @@ YSS 技能的公开发布仓库为 `iloveZzz/yss-spec-dev-skills`，它是本模
 - 发布顺序为：同步 canonical projections → 更新 lock → `scripts/verify-template` → 导出并检查 → 独立审查 → 在 `yss-spec-dev-skills` 提交人工 PR。不得从目标仓库反向覆盖 `.agents/skills`。
 - skills.sh 通过 `npx skills add iloveZzz/yss-spec-dev-skills` 的安装遥测自动发现技能，不需要手工注册；遥测可用 `DISABLE_TELEMETRY=1` 或 `DO_NOT_TRACK` 关闭。
 
-已退休、personal 或由 YSS 有意排除的条目（`design-an-interface`、`qa`、`request-refactor-plan`、`ubiquitous-language`、`edit-article`、`obsidian-vault`、`writing-great-skills`、`web-design-engineer`、`web-video-presentation`、`wireframe-prototype`、`wizard`、`git-guardrails-claude-code`、`claude-handoff`、`batch-grill-me`）不再进入 `.agents/skills`、六个共享投影根或 `skills-lock.json`。其中 `wizard` 是最新上游仍存在但 YSS 当前有意排除的人工步骤技能，不应描述为上游已退休。迁移时使用 `codebase-design`、`triage + to-tickets`、`to-spec + improve-codebase-architecture`、`domain-modeling`、`product-design:index`、普通人工 checkpoint 或 `handoff` 等现行路由，不创建兼容目录。
+已退休、personal 或由 YSS 有意排除的条目不再进入 `.agents/skills`、六个共享投影根或 `skills-lock.json`。退役 ID、日期和替代路径只在 [`skill-migrations.md`](./skill-migrations.md) 持久化，其他活跃文档不得重复维护清单或创建兼容目录。其中 `wizard` 是最新上游仍存在但 YSS 当前有意排除的人工步骤技能，不应描述为上游已退休。
 
 ## 外部工作流工具
 

package/template/docs/agents/strategic-design-skills-integration.md

@@ -0,0 +1,46 @@
+# 战略设计技能集成合同
+
+`iloveZzz/yss-harness-design-agent` 是以下公共技能 ID 的上游业务 profile：
+
+- `prototype-review`
+- `yss-prototype-stage`
+- `yss-design-system`
+- `yss-antd-design`
+- `yss-antdv-next-design`
+- `yss-stage-decision`
+
+父模板通过 `.agents/skills/.strategic-design-skills-manifest.json` 固定上游 Git revision、路径和 tree hash。公共 ID 不因 profile 改名；共享规则先在战略设计源仓演进，再由父模板同步。
+
+## 父模板薄适配
+
+父模板承载完整产品研发生命周期，只允许在以下位置保留最小语境差异：
+
+| 技能 | 父模板适配 |
+|---|---|
+| `prototype-review` | 将评审结论回交 `yss-product-lifecycle`，通过后可进入实现合同编译准备 |
+| `yss-prototype-stage` | 用户确认后由完整生命周期判断 API 影响和实现准备 |
+| `yss-stage-decision` | 门禁状态由 `yss-product-lifecycle` 维护 |
+
+`yss-design-system`、`yss-antd-design` 与 `yss-antdv-next-design` 当前不需要父模板内容适配，必须与锁定的上游 tree hash 一致。任何有效内容差异都必须保留本文件为 `adaptationRef`，不得复制成第二套公共技能身份。
+
+## 更新与验证
+
+1. 先在战略设计源仓形成并推送固定 commit。
+2. 更新 manifest 的 `source_revision` 和每项 `upstream_hash`。
+3. 同步父模板 canonical 内容，仅重放上表允许的薄适配。
+4. 运行 `scripts/update-skill-lock`、`scripts/sync-skills`。
+5. 运行：
+
+   ```bash
+   scripts/verify-upstream-skill-source \
+     --source=iloveZzz/yss-harness-design-agent \
+     --source-root=submodules/yss-harness-design-agent
+   scripts/verify-skill-governance
+   scripts/verify-template-fast
+   ```
+
+父模板、战略设计源仓与 CLI 快照必须按源仓 → 父模板 → CLI 顺序固定 revision；旧实例不回填，也不提供迁移检查器。
+
+## 真实用户决定适配
+
+模板生命周期的关键决定统一消费 `docs/agents/digital-human-roles.yaml.user_decision_policy`。本地原型确认与阶段决策批准追加真实回复、当前资产和范围校验；数字人审查保留。记录协议见 [用户决定协议](../../.agents/skills/yss-product-lifecycle/references/user-decisions.md)。此适配只更新 effective hash，不改写已锁定的上游 revision/hash，也不发布外部技能源。