create-yss-spec 3.0.1 → 3.1.0

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

@@ -1,21 +1,41 @@
-schema_version: 1
+schema_version: 2
 kind: verification
 template: true
 status: draft
-prototype_ref: docs/.scratch/example/design/prototype.html
+prototype_ref: docs/.scratch/example/design/prototypes/index.html
 spec_ref: docs/.scratch/example/spec.md
+visual_baseline:
+  baseline_id: visual-baseline.example
+  version: v1
+  digest: sha256:0000000000000000000000000000000000000000000000000000000000000000
+  manifest_ref: docs/.scratch/example/handoff/visual-baseline-v1/visual-baseline.yaml
+  status: approved
+  case_ids: [primary-desktop, primary-narrow]
 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]
+    case_ids: [primary-desktop, primary-narrow]
+case_results:
+  - case_id: primary-desktop
+    baseline_image_ref: docs/.scratch/example/handoff/visual-baseline-v1/images/primary-desktop.png
+    implementation_image_ref: docs/.scratch/example/verification/images/primary-desktop.png
+    diff_ref: docs/.scratch/example/verification/diffs/primary-desktop.png
+    mask_ref: not-applicable
+    result: blocked
+    uncovered_difference: false
+    explanation: <difference-or-not-applicable>
 interaction_results: [loading, empty, error, permission, selected, key-interaction]
 console_warning_check: blocked
 pnpm_commands: [pnpm lint, pnpm type-check, pnpm test]
+actual_verification:
+  - command: pnpm test
+    exit_code: 0
+    executed_at: <iso-8601>
+    evidence_ref: docs/.scratch/example/verification/pnpm-test.txt
 uncovered_differences: []
 difference_owner: null
 independent_review:
   reviewer: non-implementer
-  candidate_digest: pending
+  candidate_digest: sha256:0000000000000000000000000000000000000000000000000000000000000000
   status: pending
   findings_ref: docs/.scratch/example/verification/ui-fidelity-review.md

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

@@ -1,9 +1,15 @@
 schema_version: 1
+repository_mode: project-instance
 mode: route
 status: routing
 stage: stage.entry-triage
 artifacts: {}
 gates: {}
+context_reconciliation:
+  status: pending
+  ref: null
+  reason: 等待当前工作单元完成稳定术语回写与核对
+  evidence_refs: []
 next_work_unit: work-unit.discovery-opportunity
 phase_boundary:
   decision: continue
@@ -21,6 +27,9 @@ verification:
   commands: []
   evidence_refs: []
 human_review:
+  user_decisions: []
+  required_decisions: []
+  not_applicable: []
   required: false
   status: not-applicable
 git_checkpoint:

package/template/docs/process/templates/scaffold-architecture-decisions-template.yaml

@@ -0,0 +1,32 @@
+schema_version: 1
+kind: scaffold-architecture-decisions
+template: true
+status: draft
+decisions:
+  - decision_id: scaffold-decision.main-service
+    project_id: main-service
+    parent_project_id: null
+    status: awaiting-user-decision
+    recommended_architecture: domain-driven
+    recommendation_reasons:
+      - 存在聚合不变量或复杂状态转换
+    confirmed_architecture: null
+    override_reason: null
+    inheritance_mode: root-default
+    inherited_from: null
+    platform_profile: spring-boot-2.7-jdk8
+    architecture_profile: target-domain-model
+    verification_database: h2
+    production_database: not-bound
+    requested_capabilities: []
+    resolved_modules: [domain, application, infrastructure, adapter, bootstrap]
+    resolution_version: 1
+    user_confirmation:
+      user_decision_ref: null
+      decision_subject_ref: null
+      confirmed_by: null
+      channel: null
+      confirmation_ref: null
+      confirmed_at: null
+      normalized_text: null
+    decision_inputs_digest: sha256:0000000000000000000000000000000000000000000000000000000000000000

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

@@ -2,6 +2,7 @@
 
 ```yaml
 schema_version: 1
+repository_mode: <template-source|project-instance>
 mode: <route|orchestrate|resume|audit>
 status: <routing|running|paused-human-gate|blocked|completed>
 stage: <lifecycle stage>
@@ -16,6 +17,10 @@ gates:
     reason: <why this status applies>
     evidence_refs: []
     approval_ref: <docs/.scratch/<feature>/gates/<gate-id>-approval.yaml when approved countersign gate>
+context_reconciliation:
+  status: <pending|reconciled|not-applicable|blocked>
+  ref: <docs/.scratch/<feature>/evidence/context-reconciliation-<work-unit>.yaml>
+  evidence_refs: [CONTEXT.md]
 phase_boundary:
   decision: <continue|clear|handoff|subagent|compact>
   reason: <decision evidence>

package/template/docs/process/templates/user-decision-template.yaml

@@ -0,0 +1,30 @@
+# 待填写模板；不是批准证据。原始来源字段必须由真实消息提取。
+schema_version: 1
+kind: user-decision
+request:
+  id: <request-id>
+  requester_ref: <提问者原始身份>
+  requester_source:
+    kind: session-export
+    ref: <原始请求捕获文件>
+    digest: <sha256>
+    message_id: <原始消息ID>
+  items:
+    - id: <item-id>
+      boundary: <引用 user_decision_policy 中的门禁或决定类型>
+      title: <可审阅决定>
+      subject: {ref: <资产正文或冻结快照>, version: <version>, digest: <sha256>}
+      basis: []
+      scope: [<批准范围>]
+      changes: <关键变化>
+      risks: []
+      recommendation: <推荐方案>
+      next_actions: [<批准后将执行的动作>]
+      responder_ref: <提问者或其明确指定的负责人>
+      # 指定其他负责人时追加 delegation_source，与 requester_source 同形状。
+  presented_source:
+    kind: session-export
+    ref: <完整展示请求的原始消息捕获>
+    digest: <sha256>
+    message_id: <原始消息ID>
+responses: [] # 收到真实回复后追加；无回复永不预填 approved。

package/template/docs/templates/approval-record-template.yaml

@@ -12,3 +12,7 @@ countersigner_role_ids:
 evidence_refs: []
 biological_veto: false
 notes: 会签必须可读取；起草者不得出现在 countersigner_role_ids。运行时表情/reaction 无效。
+# 关键门禁正式放行时必填；模板/历史结构校验不构成批准。
+subject_ref: null
+approval_scope: []
+user_decision_ref: null

package/template/docs/templates/build-architecture-checklist-template.md

@@ -19,7 +19,7 @@ owner: ai
 | 系统 / 数据架构设计 |  |  |
 | 风险 / 回滚约束 | `AGENTS.md` |  |
 | Slice Implementation Contract |  | 填写 contract_id / contract_version / 生命周期批准状态 |
-| 后端脚手架策略 | `orchestration-contract.yaml` / `yss-ddd-scaffold-generator` |  | backend `scaffold_status=required` 时填写结构化合同身份、批准/持久化引用、生成器输入、预期文件、实际 `./mvnw` 结果和后置 实现合同编译器 重编译 |
+| 后端脚手架策略 | `orchestration-contract.yaml` / DDD 或 Layered MVC 生成器 |  | backend `scaffold_status=required` 时填写 architecture decision、schema v3 合同身份、批准/持久化引用、生成器输入、Manifest v3、实际 `./mvnw` 结果和后置实现合同编译器重编译 |
 | 工程项目路径策略 | `docs/process/implementation-repo-integration.md` / 实现合同编译器 Contract |  | Harness 内必须是 `apps/backend/<project>/` 或 `apps/frontend/<project>/`；`apps/backend/`、`apps/frontend/` 仅为容器，`app/backend/`、`app/frontend/` 及其子路径阻断 |
 | 垂直切片工作单元 |  |  |
 | YSS Skill Execution Result |  | 每个 skill / work_unit 的结果文件引用 |
@@ -32,7 +32,7 @@ owner: ai
 | 后端切片必须回勾 `Backend Slice Implementation Contract`：required skills、允许写范围、禁止模式、证据文件、延期 seam 和验证命令完整 | implementation routing / 垂直切片 Ticket / `AGENTS.md` |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 缺合同或合同不完整时暂停并记录替代方案 |
 | 统一合同版本：实现消费的 contract_id / contract_version 与生命周期批准并持久化的版本一致，实现合同编译器 未自行批准合同或推进 `ready-for-agent` | Slice Implementation Contract / 生命周期证据 |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 版本不一致时将工作单元标记 `stale` 并暂停 build |
 | 合同子项闭环：Common、Frontend、Backend、Contract、Cross-repo 子合同按影响面填写，不适用项有原因 | Slice Implementation Contract |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 缺失适用子合同时回到 实现合同编译器 |
-| 原型确认后的后端脚手架顺序：工程基线 → 实现合同编译器 脚手架合同 draft / 生命周期批准 → `yss-ddd-scaffold-generator` → `yss-backend-scaffold-parent` → 实现合同编译器 重编译；脚手架不得生成业务行为 | `yss-product-lifecycle` / `yss-ddd-scaffold-generator` |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 顺序缺失、生成器混入业务行为或缺 Execution Result 时阻断 |
+| 后端脚手架顺序：工程基线与 Agent 推荐 → 用户确认并持久化 architecture decision → schema v3 合同 draft / 生命周期批准 → DDD 或 Layered MVC 生成器 → 对应基线与 Manifest v3 校验 → 实现合同编译器重编译；生成器无交互且不得生成业务行为 | `yss-product-lifecycle` / `yss-ddd-scaffold-generator` / `yss-layered-mvc-scaffold-generator` |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 选择缺失、digest 漂移、顺序缺失、生成器混入业务行为或缺 Execution Result 时阻断 |
 | 写路径与证据：Execution Result 的 changed_files 均位于 allowed_write_paths，expected_evidence_files 已实际生成 | Slice Implementation Contract / YSS Skill Execution Result |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 路径越界或证据缺失标记 `violation` 并阻断 build |
 | TDD 模式：每个工作单元唯一选择 `behavior-tdd` 或 `controlled-generation`；生成器未承载状态、权限、业务过滤、事务、错误映射或用户可见交互 | Slice Implementation Contract / 垂直切片 Ticket / Execution Result |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 模式不匹配时拆分工作单元并完整重路由 |
 | 所有后续生成代码：必须消费当前批准合同、主 YSS skill、依赖闭包、允许写路径、预期证据和 YSS Skill Execution Result；业务行为使用 `behavior-tdd` | `post_scaffold_generated_code_policy` |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 缺任一条件或以时间压力豁免时阻断 build |
@@ -42,7 +42,7 @@ owner: ai
 | Application：负责用例编排、事务边界和跨聚合协调，不承载核心领域规则 | `yss-application` / 系统架构 |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 领域规则下沉 Domain，事务边界留在 Application |
 | Infrastructure：需要持久化的切片必须有 PO / Repository / Convertor / GatewayImpl；`InMemory*Gateway` 只能作为显式 `seam-deferred` | `yss-repository` / 数据架构 |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 未补齐时不得声称生产持久化完成 |
 | POJO / Convertor：DTO / VO / CMD / Query / PO / Domain Model 样板代码默认使用 Lombok；对象转换默认使用 MapStruct，禁止 `BeanUtils.copyProperties`、反射拷贝和重复手写字段赋值 | `lombok` / `mapstruct` / `AGENTS.md` |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 未加载 skill、缺注解处理器配置、缺 Convertor 或无例外说明时标记 `violation` |
-| 后端工程工具链：构建、测试、运行、OpenAPI 生成、CI 和 Release 命令必须使用项目根目录 `./mvnw ...`；裸 `mvn ...` 必须有受控例外记录 | `yss-ddd-scaffold-generator` / `yss-backend-scaffold-parent` / implementation routing |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 无例外记录时改为 `./mvnw ...`，否则不得进入完成 / 可合并结论 |
+| 后端工程工具链：构建、测试、运行、OpenAPI 生成、CI 和 Release 命令必须使用项目根目录 `./mvnw ...`；裸 `mvn ...` 必须有受控例外记录 | DDD / Layered MVC 生成器及 implementation routing |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 无例外记录时改为 `./mvnw ...`，否则不得进入完成 / 可合并结论 |
 | 工程项目路径：每个 Harness 内项目必须有具体项目段，禁止直接写入容器根或单数 `app/...` | `docs/process/implementation-repo-integration.md` / implementation path validator |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 路径违规时停止 build，并回到实现路由 |
 | 文档语言：持久化生命周期文档、实施记录、审查报告、发布说明和 Git checkpoint 正文必须使用中文，英文 skill / 模板不得原样落地 | `AGENTS.md` / `yss-product-lifecycle` |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 仅保留必要英文技术标识、命令和 metadata |
 | 高风险变更：按已批准的普通影响面结论记录验证证据、责任人和回滚约束 | `AGENTS.md` / Spec / 架构记录 |  | `implemented` / `seam-deferred` / `drift` / `violation` / `not-applicable` |  | 缺验证证据或责任人时不得发布或合并 |

package/template/docs/templates/implementation-repo-registry-template.md

@@ -28,7 +28,9 @@ owner: ai
 | superproject_git_url | 父仓远端；必须与 `git_url` 不同 |
 | checkout_state | attached-branch / detached-head / uninitialized / empty-gitlink / 不适用 |
 | scaffold_status | existing / required / initialized |
-| scaffold_skill | `yss-ddd-scaffold-generator` / `yss-frontend-scaffold-generator` / none |
+| scaffold_architecture | `domain-driven` / `layered-mvc` / 不适用；required 时必须由用户确认 |
+| scaffold_decision_ref | `scaffold-architecture-decisions.yaml` 的 decision_id + digest |
+| scaffold_skill | `yss-ddd-scaffold-generator` / `yss-layered-mvc-scaffold-generator` / `yss-frontend-scaffold-generator` / none |
 | scaffold_target_confirmed | 是 / 否 / 不适用 |
 | target_git_url_or_output_dir |  |
 | owner |  |

package/template/docs/templates/implementation-routing-template.md

@@ -142,6 +142,8 @@ owner: ai
 | required_skills |  |
 | approved_prototype_ref |  |
 | state_matrix_ref |  |
+| visual_baseline_ref | `visual-baseline.yaml` 路径、版本与 digest |
+| visual_baseline_case_ids | 当前切片实际消费的 case_id；禁止目录 glob |
 | generated_api_client_ref |  |
 | allowed_write_paths |  |
 | component_test_seams | loading / empty / error / permission / 其他公开 seam |
@@ -224,7 +226,7 @@ owner: ai
 
 | 受影响端 | 是否已有可用工程 | scaffold_status | 目标是否确认 | 处理结论 | 使用 skill | 输出位置 / 仓库 | 备注 |
 |---|---|---|---|---|---|---|---|
-| backend | 是 / 否 / 不适用 | existing / required / initialized / not-applicable | 是 / 否 / 不适用 | 复用现有 / 初始化 / 阻塞 | `yss-ddd-scaffold-generator` / none |  |  |
+| backend | 是 / 否 / 不适用 | existing / required / initialized / not-applicable | 是 / 否 / 不适用 | 复用现有 / 初始化 / 阻塞 | `yss-ddd-scaffold-generator` / `yss-layered-mvc-scaffold-generator` / none |  | 填写 architecture_family、decision_id 与 digest |
 | frontend | 是 / 否 / 不适用 | existing / required / initialized / not-applicable | 是 / 否 / 不适用 | 复用现有 / 初始化 / 阻塞 | `yss-frontend-scaffold-generator` / none |  |  |
 
 脚手架输出位置必须回指具体项目根：后端为 `apps/backend/<project>/`，前端为 `apps/frontend/<project>/`；不得把 `apps/backend/`、`apps/frontend/` 容器根或任何 `app/backend/`、`app/frontend/` 路径作为生成目标。
@@ -238,18 +240,18 @@ owner: ai
 
 ### 4.3 后端脚手架工作单元
 
-当 backend `scaffold_status=required` 时，先登记一个 `controlled-generation` 工作单元：`primary_skill=yss-ddd-scaffold-generator`，并在后续追加 `yss-backend-scaffold-parent` 基线校验和 `yss-implementation-contract-compiler` 合同重编译。`existing` / `initialized` 不重复全量生成，但必须提供等价基线和 Wrapper 证据。
+当 backend `scaffold_status=required` 时，生命周期先按领域复杂度推荐 DDD/MVC，并以批量决策表反问用户确认本体默认与子项目覆盖。选择写入 `scaffold-architecture-decisions.yaml`；缺失、未确认或 stale 时阻断。随后登记一个 `controlled-generation` 工作单元：`domain-driven` 使用 `primary_skill=yss-ddd-scaffold-generator`，`layered-mvc` 使用 `primary_skill=yss-layered-mvc-scaffold-generator`。生成后执行对应基线校验和 `yss-implementation-contract-compiler` 合同重编译。`existing` / `initialized` 不重复生成，架构转换另立迁移工作单元。
 
 | 项 | 内容 |
 |---|---|
-| 前置 | `prototype_confirmation`、工程基线、实现仓库和脚手架目标已确认；实现合同编译器 脚手架合同 draft 已经生命周期批准并持久化为结构化 JSON，生成器通过 `--contract-file` 消费 |
-| 生成器 | `yss-ddd-scaffold-generator` |
+| 前置 | `prototype_confirmation`、工程基线、实现仓库和脚手架目标已确认；`scaffold-architecture-decisions.yaml` 已由用户确认且 digest 当前；实现合同编译器 schema v3 脚手架合同 draft 已经生命周期批准并持久化为结构化 JSON，生成器通过 `--contract-file` 消费 |
+| 生成器 | `domain-driven` → `yss-ddd-scaffold-generator`；`layered-mvc` → `yss-layered-mvc-scaffold-generator` |
 | 模式 | `controlled-generation` |
 | Java / Maven 身份 | `base_package` 与 Maven `group_id` 分开登记；项目版本、父 POM GAV、`yss-components.version` 进入批准合同并原样传给 CLI |
-| 允许生成 | Domain / Application / Infrastructure / Adapter / Bootstrap 目录骨架、POM、配置、Wrapper 和非业务机械模板 |
+| 允许生成 | DDD 的 Domain / Application / Infrastructure / Adapter / Bootstrap，或 MVC 的 server / service / repository 与能力解析出的 adapter / client / feign-client；以及 POM、配置、Wrapper 和非业务机械模板 |
 | 禁止生成 | 业务规则、状态机、权限、事务、复杂查询、错误映射、业务字段和用户可见行为 |
 | 生成选项 | 关闭 `--with-example`；生成器严格 initialize-only，非空目录、`--force`、旧项目迁移和当前模板升级均为 `unsupported` |
-| Profile | `target-domain-model` / `mybatis-plus` / `mysql` / `spring-boot-2.7-jdk8` / `javax` / `web` / `yss-internal`；其他组合须先通过独立 fixture |
+| Profile | DDD：`target-domain-model` + MySQL；MVC：`layered-mvc` + MySQL/Oracle/OceanBase Oracle；共同固定 Spring Boot 2.7 / Java 8 / `javax` / MyBatis-Plus，其他组合须先通过独立 fixture |
 | 验证 | 使用一键生成验证入口，实际执行项目根目录 `./mvnw validate`、`./mvnw test`、`./mvnw package`；通过后仅为 `empty-scaffold-verified`，golden first slice 通过后才是 `first-slice-verified` |
 | 后置 | `yss-backend-scaffold-parent`、`yss-implementation-contract-compiler` 业务合同重编译、YSS Skill Execution Result |
 

package/template/docs/templates/requirement-freeze-template.md

@@ -17,7 +17,7 @@ owner: ai
 | Spec 初稿 |  |  |  |
 | 产品总体设计 / 功能架构 |  |  | 必需 |
 | 产品设计 / 交互说明 |  |  |  |
-| 原型交付物 | `docs/.scratch/<feature>/design/prototypes/index.html` 或稳定 URL |  | 有产品设计影响时必需；按 H1/H2 档位提供 schema v3 浏览器、Design QA 与条件 AntD 事实；真实组件待验事项进入前端实现计划 |
+| 原型交付物 | `docs/.scratch/<feature>/design/prototypes/index.html` 或稳定 URL |  | 有产品设计影响时必需；按 H1/H2 档位提供 Prototype Evidence schema v4、Visual Baseline schema v1、浏览器、Design QA 与条件 AntD 事实；真实组件待验事项进入前端实现计划 |
 | Prototype Review |  |  |  |
 | CONTEXT 术语 |  |  | 业务术语须含 PascalCase `英文标识` |
 

package/template/docs/templates/review-report-template.md

@@ -88,7 +88,7 @@ rg -n "class (SingleResult|MultiResult|PageResult|Result)<|public static class .
 | 检查项 | 结论 | 证据 |
 |---|---|---|
 | `yss-ui` 组件路由已落实：YSS `required` 封装（如 `YTable` / `YTree` / `YFormily`）未被 AntDV 裸组件或其他重型方案绕过；受控回退有能力缺口记录 | pass / violation / not-applicable |  |
-| `yss-ui-business-page-generation` 页面生成与 `yss-page-module-development` 生命周期编排已落实：`index.vue` 只编排，请求与分页不堆在页面根组件 | pass / violation / not-applicable |  |
+| `yss-ui-business-page-generation` 页面生成与生命周期编排已落实：`index.vue` 只编排，请求与分页不堆在页面根组件 | pass / violation / not-applicable |  |
 | 切片合同 `required_skills` 中的 Formily / 表格 / 树 / 高度 / 主题 / API 专项 skill 已按影响面引用规则；未命中项有 `not-applicable` 原因 | pass / violation / not-applicable |  |
 | 前端验证使用项目根 `pnpm ...`；实际退出码已记录。只做 type-check 或声称“已对齐”不算通过 | pass / violation / not-applicable |  |
 | 机器检查（`pnpm lint` / `pnpm type-check` 等已存在脚本）已执行，或缺失工具已写 `not-applicable` 及原因 | pass / violation / not-applicable |  |

package/template/docs/templates/spec-template.md

@@ -67,16 +67,16 @@ owner: ai
 |---|---|---|
 | | | |
 
-## DDD 影响判断
+## 业务边界与规则影响判断
 
-> 仅做轻量判断，不新增流程阶段。若均为“否”，后续不需要单独 DDD 设计；若触发边界、模型或一致性变化，在产品总体设计 / 系统概要设计中补齐对应小节。
+> 仅做轻量判断，不新增流程阶段。若均为“否”，后续不需要单独补充业务边界或复杂技术模型设计；若触发责任边界、关键规则、状态或一致性变化，在产品总体设计 / 系统概要设计中补齐对应小节。
 
 | 检查项 | 是 / 否 | 说明 / 处理 |
 |---|---|---|
-| 是否新增或改变统一语言 / 核心术语 |  | 需要回写 `CONTEXT.md` 的中文术语和 PascalCase `英文标识` |
-| 是否新增或改变限界上下文 / 模块边界 |  | 需要在产品总体设计中完成 Strategic DDD Check |
+| 是否新增或改变统一业务词汇 / 核心术语 |  | 需要回写 `CONTEXT.md` 的中文术语、PascalCase `英文标识` 和适用业务责任区 |
+| 是否新增或改变业务责任区 / 模块边界 |  | 需要在产品总体设计中完成业务边界与协作检查 |
 | 是否改变上下文间协作关系 |  | 说明上游 / 下游 / 防腐层 / 共享内核关系 |
-| 是否新增或改变聚合、不变量、状态机 |  | 需要在系统概要设计 / 数据架构中完成 Tactical DDD Check |
+| 是否新增或改变关键业务对象、不可违反规则或状态机 |  | 需要在系统概要设计 / 数据架构中完成技术模型检查 |
 | 是否影响 API、权限、数据、审计或风险 / 回滚约束 |  | 进入对应契约、架构或人工审查门禁 |
 
 ## 测试决策

package/template/docs/user-guide//346/210/230/346/234/257/350/256/276/350/256/241/345/255/220/351/241/271/347/233/256/347/224/250/346/210/267/346/211/213/345/206/214.md

@@ -44,8 +44,9 @@ Strategic Design 解决“业务应该怎样分工和划边界”；Tactical Des
 - Spec、原型或业务级 Ticket 的版本引用；
 - 交给 Tactical Design 裁决的问题，例如聚合边界、状态、一致性和持久化；
 - 未决问题、责任人和后续验证计划。
+- `source_context_snapshot` 与包含术语定义的 `context_delta`，以及“目标仓在 Tactical Design 前完成 `context_reconciliation`”的约束。
 
-如果交接包缺失、过期或与当前 Spec 不一致，先回到上游处理，不要凭经验补写模型。
+先把 `context_delta` 对账到当前项目根目录唯一 `CONTEXT.md`，生成目标侧 reconciliation，并运行 `scripts/verify-strategic-context-import --root . --reconciliation <record> <handoff>`。如果交接包缺失、仍为 v1、过期、摘要漂移或与当前 Spec / 目标词汇不一致，先回到上游处理，不要凭经验补写模型。
 
 ### 确认项目实例
 
@@ -197,6 +198,7 @@ Strategic Design 解决“业务应该怎样分工和划边界”；Tactical Des
 ## 评审前自检
 
 - [ ] 输入来自批准且版本当前的 `Strategic Design Handoff`。
+- [ ] Strategic Design Handoff 为 schema v2，目标根 `CONTEXT.md` 已完成 context delta 对账，`strategic_context_import_ref` 与 `context_reconciliation_ref` 均通过校验。
 - [ ] 统一语言与 `CONTEXT.md` 一致，没有临时创造同义词。
 - [ ] 聚合根、Entity、Value Object 的身份和边界有理由。
 - [ ] 每个聚合的不变量和允许的状态转换都写清楚。

package/template/docs/user-guide//347/224/250/346/210/267/346/211/213/345/206/214.md

@@ -398,7 +398,7 @@ Draft 只是草案。评审通过后才能 Freeze。Freeze 可以理解为“接
 前端：
 
 - 让 `yss-implementation-contract-compiler` 选择当前页面需要的专项 skill。
-- 以 `yss-ui`、`yss-page-module-development` 和 `tdd` 为主。
+- 以 `yss-ui`、`yss-ui-business-page-generation` 和 `tdd` 为主。
 - 只修改合同允许的路径。
 - 实际运行已登记的 `pnpm` 命令。
 

package/template/scripts/fixtures/strategic-handoff/base-stage.json

@@ -0,0 +1,91 @@
+{
+  "schema_version": 2,
+  "stage_decision_id": "stage-decision.supplier-admission",
+  "package_version": "v2",
+  "status": "approved",
+  "problem_statement": "合规准入决定分散，采购无法稳定判断当前有效资格。",
+  "target_users": [
+    "采购专员、合规专员"
+  ],
+  "mvp": [
+    "提交供应商申请、合规准入决定、采购侧有效性校验"
+  ],
+  "non_goals": [
+    "供应商结算、采购付款、通用工作流平台"
+  ],
+  "success_criteria": [
+    "新采购订单 100% 校验当前有效准入决定"
+  ],
+  "test_seams": [
+    "supplier-application-submit",
+    "admission-validity-check"
+  ],
+  "confirmed_decisions": [
+    "ComplianceReview 拥有准入规则语义，ProcurementExecution 只消费决定"
+  ],
+  "assumptions": [
+    "供应商已有唯一 subject_ref"
+  ],
+  "constraints": [
+    "保留现有采购订单流程"
+  ],
+  "unresolved_items": [
+    {
+      "item": "供应商历史资料迁移范围",
+      "type": "deferred",
+      "owner": "role.product-manager",
+      "next_action": "在 Spec synthesis 前完成数据盘点",
+      "target_version": "2026-Q4"
+    }
+  ],
+  "context_snapshot": {
+    "context_ref": "CONTEXT.md",
+    "context_schema_version": 1,
+    "document_digest": "<document-digest>",
+    "referenced_terms_digest": "<referenced-terms-digest>",
+    "term_refs": [
+      "Global/Supplier",
+      "ComplianceReview/AdmissionDecision"
+    ]
+  },
+  "domain_strategy_ref": {
+    "domain_strategy_id": "domain-strategy.supplier-admission",
+    "domain_version": "v2",
+    "digest": "<domain-strategy-digest>",
+    "status": "approved",
+    "persisted_ref": "domain-strategy.yaml"
+  },
+  "impact_assessment": {
+    "ui": true,
+    "api": true,
+    "data": true,
+    "backend": true,
+    "frontend": true,
+    "cross_repo": false,
+    "high_risk": false
+  },
+  "downstream_mapping": [
+    {
+      "domain_change": "admission-decision-validity",
+      "consumer": "spec-synthesis",
+      "propagation": "direct",
+      "reapproval_condition": "领域策略版本或有效性规则变化"
+    },
+    {
+      "domain_change": "admission-decision-validity",
+      "consumer": "ticket-decomposition",
+      "propagation": "transitive",
+      "reapproval_condition": "Spec 基线变更"
+    }
+  ],
+  "evidence_refs": [
+    "evidence.discovery.supplier",
+    "evidence.domain-strategy-review.supplier"
+  ],
+  "approval": {
+    "approval_ref": ".agents/skills/yss-stage-decision/tests/fixtures/stage-decision-approval.yaml",
+    "approver": "role.product-manager",
+    "persisted_ref": "docs/.scratch/supplier/stage-decision/stage-decision-package-v1.yaml",
+    "current_version": "v2"
+  }
+}

package/template/scripts/fixtures/strategic-handoff/base-strategy.json

@@ -0,0 +1,205 @@
+{
+  "schema_version": 2,
+  "domain_strategy_id": "domain-strategy.supplier-admission",
+  "domain_version": "v2",
+  "status": "approved",
+  "contexts": [
+    {
+      "context_id": "SupplierManagement",
+      "name": "供应商管理",
+      "responsibilities": [
+        "供应商申请、资料生命周期"
+      ],
+      "non_responsibilities": [
+        "合规决定、采购订单"
+      ],
+      "subdomain_type": "Supporting Subdomain",
+      "owner": "requirements-manager",
+      "status": "confirmed"
+    },
+    {
+      "context_id": "ComplianceReview",
+      "name": "合规审查",
+      "responsibilities": [
+        "资质审查、准入决定、有效期"
+      ],
+      "non_responsibilities": [
+        "供应商主档、采购订单"
+      ],
+      "subdomain_type": "Core Domain",
+      "owner": "product-manager",
+      "status": "confirmed"
+    },
+    {
+      "context_id": "ProcurementExecution",
+      "name": "采购执行",
+      "responsibilities": [
+        "采购选择、采购订单履行"
+      ],
+      "non_responsibilities": [
+        "合规规则、供应商申请"
+      ],
+      "subdomain_type": "Supporting Subdomain",
+      "owner": "project-manager",
+      "status": "confirmed"
+    }
+  ],
+  "subdomains": [
+    {
+      "subdomain_id": "subdomain.supplier-management",
+      "name": "Supplier Management",
+      "type": "Supporting Subdomain",
+      "rationale": "管理申请与资料生命周期，不承载差异化合规决策。",
+      "evidence_refs": [
+        "evidence.discovery.supplier"
+      ]
+    },
+    {
+      "subdomain_id": "subdomain.compliance-review",
+      "name": "Compliance Review",
+      "type": "Core Domain",
+      "rationale": "核心价值候选是企业自有的合规判断和风险规则。",
+      "evidence_refs": [
+        "evidence.discovery.compliance"
+      ]
+    }
+  ],
+  "relationships": [
+    {
+      "relationship_id": "relationship.supplier-to-compliance",
+      "from_context": "SupplierManagement",
+      "to_context": "ComplianceReview",
+      "relationship_pattern": "Customer/Supplier",
+      "semantic_upstream": "SupplierManagement",
+      "semantic_downstream": "ComplianceReview",
+      "business_authority": "SupplierManagement owns applicant facts",
+      "model_change_impact": "applicant schema changes require review adaptation",
+      "transport_direction": "SubmitSupplierForComplianceReview command",
+      "translation_responsibility": "ComplianceReview ACL",
+      "direction_explanation": "申请资料由 SupplierManagement 拥有，但技术请求方向不代表合规规则所有权。"
+    },
+    {
+      "relationship_id": "relationship.compliance-to-procurement",
+      "from_context": "ComplianceReview",
+      "to_context": "ProcurementExecution",
+      "relationship_pattern": "Published Language",
+      "semantic_upstream": "ComplianceReview",
+      "semantic_downstream": "ProcurementExecution",
+      "business_authority": "ComplianceReview owns admission validity",
+      "model_change_impact": "decision validity changes invalidate procurement acceptance",
+      "transport_direction": "admission decision events",
+      "translation_responsibility": "ProcurementExecution local projection",
+      "direction_explanation": "合规决定是语义上游；采购侧可通过事件接收并在下单时实时校验。"
+    }
+  ],
+  "scenarios": [
+    {
+      "scenario_id": "scenario.supplier-submits",
+      "actor": "supplier",
+      "preconditions": [
+        "供应商资料可编辑"
+      ],
+      "commands": [
+        "SubmitSupplierApplication"
+      ],
+      "rules": [
+        "申请材料必须完整"
+      ],
+      "events": [
+        "SupplierApplicationSubmitted"
+      ],
+      "failure_results": [
+        "材料不完整时拒绝提交"
+      ],
+      "responsible_context": "SupplierManagement",
+      "consumers": [
+        "ComplianceReview"
+      ],
+      "status": "confirmed"
+    },
+    {
+      "scenario_id": "scenario.admission-expires",
+      "actor": "compliance-officer",
+      "preconditions": [
+        "批准决定存在"
+      ],
+      "commands": [
+        "EvaluateAdmissionValidity"
+      ],
+      "rules": [
+        "过期决定不得支持新采购订单"
+      ],
+      "events": [
+        "SupplierAdmissionExpired"
+      ],
+      "failure_results": [
+        "采购下单时资格校验失败"
+      ],
+      "responsible_context": "ComplianceReview",
+      "consumers": [
+        "SupplierManagement",
+        "ProcurementExecution"
+      ],
+      "status": "confirmed"
+    }
+  ],
+  "concept_candidates": [
+    {
+      "concept_id": "domain-concept.admission-decision",
+      "name": "AdmissionDecision",
+      "context_id": "ComplianceReview",
+      "identity_features": [
+        "decision_id、subject_ref、rule_version"
+      ],
+      "lifecycle": [
+        "proposed、approved、rejected、expired、revoked"
+      ],
+      "possible_tactical_role": "Entity candidate",
+      "confidence": "high",
+      "status": "confirmed"
+    }
+  ],
+  "invariants": [
+    {
+      "invariant_id": "invariant.current-admission-required",
+      "statement": "新采购订单必须引用当前有效的准入决定。",
+      "responsible_context": "ComplianceReview",
+      "scenario_refs": [
+        "scenario.admission-expires"
+      ],
+      "verification_method": "领域场景测试和事件版本校验"
+    }
+  ],
+  "context_snapshot": {
+    "context_ref": "CONTEXT.md",
+    "context_schema_version": 1,
+    "document_digest": "<document-digest>",
+    "referenced_terms_digest": "<referenced-terms-digest>",
+    "term_refs": [
+      "Global/Supplier",
+      "ComplianceReview/AdmissionDecision"
+    ]
+  },
+  "downstream_mapping": [
+    {
+      "domain_change": "admission-decision-validity",
+      "impacts": [
+        "spec",
+        "openapi",
+        "procurement-acceptance-tests"
+      ],
+      "propagation": "stale",
+      "reapproval_condition": "ComplianceReview 决定和有效期重新批准"
+    }
+  ],
+  "evidence_refs": [
+    "evidence.discovery.supplier",
+    "evidence.discovery.compliance"
+  ],
+  "approval": {
+    "approval_ref": ".agents/skills/yss-stage-decision/tests/fixtures/domain-strategy-approval.yaml",
+    "approver": "role.product-manager",
+    "persisted_ref": "docs/.scratch/supplier/domain/domain-strategy-v1.yaml",
+    "current_version": "v2"
+  }
+}