create-yss-spec 3.1.0 → 3.2.0

package/src/validation/metadata.js

@@ -0,0 +1,105 @@
+"use strict";
+
+const OWNERSHIP_TYPES = new Set([
+  "managed",
+  "managed-customizable",
+  "generated",
+  "user-owned",
+  "protected",
+]);
+const MERGE_STRATEGIES = new Set(["replace-with-force", "manual"]);
+
+function assertPositiveInteger(value, name) {
+  if (value !== undefined && (!Number.isInteger(value) || value < 1)) {
+    throw new Error(`模板元数据 ${name} 必须是正整数`);
+  }
+}
+
+function assertSha256(value, name) {
+  if (value !== undefined && !/^[0-9a-f]{64}$/.test(value)) {
+    throw new Error(`模板元数据 ${name} 必须是 64 位 sha256`);
+  }
+}
+
+function validateTemplateMetadata(metadata, {
+  currentSchemaVersion = 2,
+  templateName,
+  templateSource,
+} = {}) {
+  if (!metadata || typeof metadata !== "object" || Array.isArray(metadata)) {
+    throw new Error("模板元数据必须是 JSON 对象");
+  }
+  if (metadata.metadataSchemaVersion !== undefined && (!Number.isInteger(metadata.metadataSchemaVersion) || metadata.metadataSchemaVersion < 1)) {
+    throw new Error("模板元数据 metadataSchemaVersion 必须是正整数");
+  }
+  if (metadata.metadataSchemaVersion > currentSchemaVersion) {
+    throw new Error(`不支持的模板元数据版本：${metadata.metadataSchemaVersion}`);
+  }
+  if (metadata.managedFiles !== undefined && (typeof metadata.managedFiles !== "object" || metadata.managedFiles === null || Array.isArray(metadata.managedFiles))) {
+    throw new Error("模板元数据 managedFiles 必须是 JSON 对象");
+  }
+
+  assertPositiveInteger(metadata.ownershipPolicyVersion, "ownershipPolicyVersion");
+  assertSha256(metadata.ownershipPolicyHash, "ownershipPolicyHash");
+  assertPositiveInteger(metadata.customizationPolicyVersion, "customizationPolicyVersion");
+  assertSha256(metadata.customizationPolicyHash, "customizationPolicyHash");
+  assertPositiveInteger(metadata.generatorPolicyVersion, "generatorPolicyVersion");
+  assertSha256(metadata.generatorPolicyHash, "generatorPolicyHash");
+
+  for (const [relativePath, record] of Object.entries(metadata.managedFiles || {})) {
+    if (!record || typeof record !== "object" || Array.isArray(record)) {
+      throw new Error(`模板元数据 managedFiles.${relativePath} 必须是对象`);
+    }
+    if (record.ownership !== undefined && !OWNERSHIP_TYPES.has(record.ownership)) {
+      throw new Error(`模板元数据 managedFiles.${relativePath}.ownership 非法：${record.ownership}`);
+    }
+    if (
+      record.mergeStrategy !== undefined &&
+      !MERGE_STRATEGIES.has(record.mergeStrategy)
+    ) {
+      throw new Error(
+        `模板元数据 managedFiles.${relativePath}.mergeStrategy 非法：${record.mergeStrategy}`,
+      );
+    }
+    if (
+      record.generatorId !== undefined &&
+      !/^[a-z][a-z0-9-]*$/.test(record.generatorId)
+    ) {
+      throw new Error(
+        `模板元数据 managedFiles.${relativePath}.generatorId 非法：${record.generatorId}`,
+      );
+    }
+    if (
+      record.generatorVersion !== undefined &&
+      (!Number.isInteger(record.generatorVersion) || record.generatorVersion < 1)
+    ) {
+      throw new Error(
+        `模板元数据 managedFiles.${relativePath}.generatorVersion 必须是正整数`,
+      );
+    }
+  }
+
+  if (metadata.metadataSchemaVersion === currentSchemaVersion) {
+    if (templateName !== undefined && metadata.templateName !== templateName) {
+      throw new Error("模板元数据 templateName 与当前 CLI 不匹配");
+    }
+    if (typeof metadata.cliVersion !== "string" || !metadata.cliVersion) {
+      throw new Error("模板元数据 cliVersion 缺失或非法");
+    }
+    if (templateSource !== undefined && metadata.templateSource !== templateSource) {
+      throw new Error("模板元数据 templateSource 缺失或非法");
+    }
+    if (!/^[0-9a-f]{40}$/.test(metadata.templateCommit || "")) {
+      throw new Error("模板元数据必须包含 40 位不可变 templateCommit");
+    }
+    if (!/^[0-9a-f]{64}$/.test(metadata.managedFilesManifestVersion || "")) {
+      throw new Error("模板元数据 managedFilesManifestVersion 缺失或非法");
+    }
+    if (typeof metadata.variables !== "object" || metadata.variables === null || Array.isArray(metadata.variables)) {
+      throw new Error("模板元数据 variables 必须是 JSON 对象");
+    }
+  }
+  return metadata;
+}
+
+module.exports = { validateTemplateMetadata };

package/src/validation/security.js

@@ -0,0 +1,67 @@
+"use strict";
+
+const path = require("node:path");
+const { collectGitRoots, inspectCheckoutState } = require("../git/worktree");
+const { isGitSubmoduleMount } = require("../git/submodule");
+
+const DEFAULT_UNMANAGED_USER_PATHS = new Set([".gitmodules"]);
+
+function gitlinkWriteViolation(targetDir, { force = false, packageRoot = null, deps = {} } = {}) {
+  const resolved = path.resolve(targetDir);
+  const roots = (deps.collectGitRoots || collectGitRoots)(resolved);
+  for (const root of roots) {
+    if (packageRoot && path.resolve(root) === path.resolve(packageRoot)) continue;
+    let current = resolved;
+    while (true) {
+      if ((deps.isGitSubmoduleMount || isGitSubmoduleMount)(root, current, deps)) {
+        const checkout = (deps.inspectCheckoutState || inspectCheckoutState)(root, current, deps);
+        if (checkout === "empty-gitlink" || checkout === "uninitialized") {
+          return "空 gitlink 不得当成普通目录写入；gitlink 不得由 CLI 覆盖";
+        }
+        if (checkout === "detached-head") {
+          return "detached HEAD 不得当成普通目录写入；gitlink 不得由 CLI 覆盖";
+        }
+        if (path.resolve(current) === resolved) {
+          return force
+            ? "--force 不得把 git-submodule 挂载点当成普通目录覆盖"
+            : "git-submodule gitlink 不得由 CLI 覆盖；先 git submodule update --init，在子仓附加分支的工作树内操作，或改用独立目录";
+        }
+      }
+      if (path.resolve(current) === path.resolve(root)) break;
+      const parent = path.dirname(current);
+      if (parent === current) break;
+      current = parent;
+    }
+  }
+  return null;
+}
+
+function assertTargetWorkingTreeWritable(targetDir, options = {}) {
+  const violation = gitlinkWriteViolation(targetDir, options);
+  if (violation) throw new Error(violation);
+}
+
+function unmanagedPathReason(targetDir, relativePath, { packageRoot = null, unmanagedPaths = DEFAULT_UNMANAGED_USER_PATHS, deps = {} } = {}) {
+  const normalized = String(relativePath).split(path.sep).join("/");
+  if (unmanagedPaths.has(normalized) || normalized.split("/")[0] === ".gitmodules") {
+    return ".gitmodules 是用户资产，不属于受管模板文件";
+  }
+  const absolutePath = path.resolve(targetDir, normalized);
+  const roots = (deps.collectGitRoots || collectGitRoots)(targetDir);
+  for (const root of roots) {
+    if (packageRoot && path.resolve(root) === path.resolve(packageRoot)) continue;
+    let current = absolutePath;
+    while (true) {
+      if ((deps.isGitSubmoduleMount || isGitSubmoduleMount)(root, current, deps)) {
+        return "gitlink / apps 挂载工作树是用户资产，不属于受管模板文件";
+      }
+      if (path.resolve(current) === path.resolve(root)) break;
+      const parent = path.dirname(current);
+      if (parent === current) break;
+      current = parent;
+    }
+  }
+  return null;
+}
+
+module.exports = { DEFAULT_UNMANAGED_USER_PATHS, gitlinkWriteViolation, assertTargetWorkingTreeWritable, unmanagedPathReason };

package/src/validation/snapshot.js

@@ -0,0 +1,47 @@
+"use strict";
+
+const path = require("node:path");
+
+function normalizeRelativePath(value) {
+  return String(value).split(path.sep).join("/");
+}
+
+function validateTemplateSnapshot(snapshot, { manifestHash, treeHash } = {}) {
+  if (!snapshot || typeof snapshot !== "object" || Array.isArray(snapshot)) {
+    throw new Error("模板快照元数据必须是 JSON 对象");
+  }
+  if (!/^[0-9a-f]{40}$/.test(snapshot.templateCommit || "")) {
+    throw new Error("模板快照必须绑定 40 位不可变 templateCommit");
+  }
+  if (!/^[0-9a-f]{64}$/.test(snapshot.snapshotHash || "")) {
+    throw new Error("模板快照必须包含 64 位 snapshotHash");
+  }
+  if (manifestHash !== undefined && snapshot.manifestHash !== manifestHash) {
+    throw new Error("模板快照与当前 template.manifest.json 不一致，请重新构建 CLI 包");
+  }
+  if (snapshot.encodedPaths !== undefined && (typeof snapshot.encodedPaths !== "object" || snapshot.encodedPaths === null || Array.isArray(snapshot.encodedPaths))) {
+    throw new Error("模板快照 encodedPaths 必须是 JSON 对象");
+  }
+
+  const encodedTargets = new Set();
+  for (const [logicalPath, encodedPath] of Object.entries(snapshot.encodedPaths || {})) {
+    for (const value of [logicalPath, encodedPath]) {
+      const normalized = normalizeRelativePath(value);
+      if (!normalized || normalized === "." || normalized.startsWith("../") || normalized.includes("/../") || path.posix.isAbsolute(normalized)) {
+        throw new Error(`模板快照包含越界路径：${value}`);
+      }
+    }
+    const normalizedTarget = normalizeRelativePath(encodedPath);
+    if (encodedTargets.has(normalizedTarget)) {
+      throw new Error(`模板快照 encodedPaths 存在重复目标：${encodedPath}`);
+    }
+    encodedTargets.add(normalizedTarget);
+  }
+
+  if (treeHash !== undefined && snapshot.snapshotHash !== treeHash) {
+    throw new Error("模板快照内容 hash 不匹配，请重新构建 CLI 包");
+  }
+  return snapshot;
+}
+
+module.exports = { validateTemplateSnapshot, normalizeRelativePath };

package/template/.agents/skills/.strategic-design-skills-manifest.json

@@ -3,7 +3,7 @@
   "source": "iloveZzz/yss-harness-design-agent",
   "source_type": "git-submodule",
   "source_root": ".agents/skills",
-  "source_revision": "31189d2b4b78821ea8bef202d8516ac85b7a3c79",
+  "source_revision": "8a67e0f5a56aa5085d18c2b42bb540c8f36c2fab",
   "adaptation_ref": "docs/agents/strategic-design-skills-integration.md",
   "skills": [
     {

package/template/.agents/skills/yss-domain/SKILL.md

@@ -5,7 +5,7 @@ description: 用于构建或重构 YSS 领域层代码。当用户要求设计
 
 # yss-domain
 
-这是一个领域实现 skill。核心目标是消费已批准的战术模型，将领域行为落实为代码；战术模型的设计与批准由 `yss-tactical-design` 和 `yss-product-lifecycle` 负责。
+这是一个领域实现 skill。核心目标是消费已批准的战术模型，将领域行为落实为代码；`yss-technical-design` 组织 DDD 分支，由 `yss-tactical-design` 设计、`yss-product-lifecycle` 维护批准。
 
 本 skill 在新脚手架链路只支持 `domain-driven` / `target-domain-model`。`layered-mvc-service` 与 `mvc-data-analysis-v1` 是独立 MVC Profile，不是失败的 DDD 工程；它们不加载本 skill，也不生成 Domain Gateway。既有旧架构不在本链路内迁移。
 
@@ -23,7 +23,7 @@ description: 用于构建或重构 YSS 领域层代码。当用户要求设计
 
 ## 工作方式
 
-1. 先读取批准且版本当前的 tactical-design contract 和 Slice Implementation Contract。
+1. 先读取批准且版本当前的 Technical Design Contract 的 DDD `design` 分支和 Slice Implementation Contract；旧 v1 tactical-design contract 只按 DDD 显式兼容读取。
 2. 数据库字段只做补充，不直接决定领域对象结构。
 3. 按合同实现领域行为、状态机、不变量和 Gateway 边界。
 4. 规则不清晰或模型需要扩展时，返回 `new_impacts` / `drift` 并停止，不要静默猜测。
@@ -64,7 +64,7 @@ description: 用于构建或重构 YSS 领域层代码。当用户要求设计
 ## 阶段 7 合同
 
 - 只消费生命周期已批准的 `Slice Implementation Contract` 和当前 `work_unit`；不得扩大 `allowed_write_paths`。
-- `Slice Implementation Contract` 必须引用批准且版本当前的 `tactical_design_ref`；不得在实现阶段重新批准或替换聚合、不变量和一致性策略。
+- `Slice Implementation Contract` 必须引用批准且版本当前的 `technical_design` 绑定（旧 DDD 显式兼容 `tactical_design_ref`）；不得在实现阶段重新批准或替换聚合、不变量和一致性策略。
 - 领域规则、状态机和不变量必须使用 `behavior-tdd`，先形成失败测试，再实现最小行为。
 - 完成后按 `yss-implementation-contract-compiler/references/yss-skill-execution-result.md` 返回统一 `YSS Skill Execution Result`：changed files、领域/测试证据、实际验证结果、偏离和新增影响。
 - 发现新 API、权限、状态机、数据模型或架构影响时填入 `new_impacts` 并暂停，不得静默扩张切片。

package/template/.agents/skills/yss-frontend-scaffold-generator/SKILL.md

@@ -30,6 +30,8 @@ branch: template
 
 ## Workflow
 
+采用专职前端 profile 或显式 `frontend_delivery` 绑定时，先按 `docs/process/frontend-backend-delivery.md` 实际核验战略与后端联合交付。缺任一输入只能诊断和回交；输入通过后准备计划/合同，正式实现、生成和恢复仍须当前批准的 Slice Contract 冻结接收摘要。接口或部署版本漂移时重新接收，不复用旧成功输出。
+
 1. 确认当前任务已经通过 Harness 入口分诊，且实现位置已记录在 proposal、design、build entry review、实施计划或实现路由记录中。
 2. 确认目标是外部实现仓库；只有用户明确选择时才输出到 Harness 仓库的 `apps/frontend/<project>/`。`apps/frontend/` 只能作为项目容器，`app/frontend/`、`app/backend/` 及其子路径禁止作为输出位置。`git-submodule` 只能在已初始化且附加分支的子仓工作树生成；空 gitlink、detached HEAD、`--force` 覆盖挂载点不得当成普通目录。
 3. 只读检查模板分支是否可访问：`git ls-remote --heads <repo> template`。

package/template/.agents/skills/yss-implementation-contract-compiler/SKILL.md

@@ -26,12 +26,14 @@ description: Use when a YSS vertical slice is entering implementation, spans mul
 
 ## 硬规则
 
+采用专职前端 profile 或显式 `frontend_delivery` 绑定时，先按 `docs/process/frontend-backend-delivery.md` 实际核验战略与后端联合交付。缺任一输入只能诊断和回交；输入通过后准备计划/合同，正式实现、生成和恢复仍须当前批准的 Slice Contract 冻结接收摘要。接口或部署版本漂移时重新接收，不复用旧成功输出。
+
 - 编译器不得输出 `approved`、`ready-for-agent` 或 `completed`。
 - Registry、Slice Contract 或编译器合同 schema v1 一律拒绝并给出迁移到 v2 的提示；不自动升级，不提供旧技能名兼容。
 - `required_capabilities` 与 `required_skills` 必须同时冻结；Registry 或编译器摘要变化后合同立即 `stale`，重新编译后仍须交生命周期重新批准。
 - UI 影响缺少正式原型确认、批准且 digest 当前的 Visual Baseline manifest 或当前切片 `case_id` 时，不得路由页面实现。模型必须先读 manifest 与语义引用，再查看对应 PNG；禁止目录 glob 和图片独立猜义。
 - Repository/数据模型影响缺少数据架构时，不得路由持久化实现。
-- 领域影响缺少批准且版本当前的 tactical-design contract 时，不得路由 Domain 实现；无领域影响必须记录 `not-applicable`。
+- 后端技术设计由 `yss-technical-design` 先行组织。消费批准且版本当前的 Technical Design Contract，核对其架构与工程基线一致；DDD 才消费聚合、Gateway 等战术字段并路由 `yss-domain`，MVC 消费用例、分层、规则和事务设计并按 Profile 路由。旧 v1 战术合同只按 DDD 显式兼容读取。无相关影响记录带原因的 `not-applicable`。
 - API 变化必须回到生命周期 Draft/Review/Freeze；半成品 backend 不得冒充稳定 source of truth。
 - 后端端到端切片必须包含 Application；对象/POJO 影响按契约自动补 `mapstruct`、`lombok`、`alibaba-java-code-style`。
 - Harness 内实现路径必须落在 `apps/backend/<project>/` 或 `apps/frontend/<project>/` 的具体项目目录；`apps/backend/`、`apps/frontend/` 只能作为容器，`app/backend/`、`app/frontend/` 及其子路径一律阻断。外部实现仓库使用其登记的真实项目根路径。`git-submodule` 使用 `implementation_path_policy: git-submodule-harness-apps`，空 gitlink、detached HEAD 或 `--force` 覆盖挂载点不得脚手架；`inspectWorkingTreeScope.writable` 必须为显式布尔值。
@@ -58,4 +60,4 @@ description: Use when a YSS vertical slice is entering implementation, spans mul
 
 跨仓交接使用 `scripts/strategic-handoff export / verify / import`。正式导出前补齐源战略的稳定规则 ID、关键场景和当前批准绑定；源资产原字节冻结、包内路径通过清单解析。目标导入只产生快照和对账/承接草案，正式 reconciliation 通过后才能进入战术设计。流程与字段见 `docs/process/strategic-handoff-package.md`。
 
-战术合同必须绑定 `strategic_handoff` 导入收据、包摘要、正式目标对账及逐条承接 rows。来自导入包时禁止仅填 `upstream_current: true`。批准前执行 `scripts/verify-strategic-handoff-consumption --root <target> <tactical>`；存在受控延期时按切片执行 `--slice <slice-id>`，实际核验通过且合同批准后才可继续相关切片。最新源规则、关键场景或资产变化使依赖项 stale；未知依赖扩大阻断，业务冲突回交战略方。结果绑定当前包与战术摘要，不能复用旧输出宣布 ready-for-agent。
+来自战略交接包的技术设计合同（DDD / MVC）必须绑定 `strategic_handoff` 导入收据、包摘要、正式目标对账及逐条承接 rows。来自导入包时禁止仅填 `upstream_current: true`。批准前执行 `scripts/verify-strategic-handoff-consumption --root <target> <tactical>`；存在受控延期时按切片执行 `--slice <slice-id>`，实际核验通过且合同批准后才可继续相关切片。最新源规则、关键场景或资产变化使依赖项 stale；未知依赖扩大阻断，业务冲突回交战略方。结果绑定当前包与战术摘要，不能复用旧输出宣布 ready-for-agent。

package/template/.agents/skills/yss-implementation-contract-compiler/references/boundaries.md

@@ -18,6 +18,8 @@
 
 | Capability | Primary skill | Task modes |
 | --- | --- | --- |
+| `architecture.technical-design` | `yss-technical-design` | `guidance`, `integration`, `review-input` |
+| `architecture.mvc-design` | `yss-mvc-design` | `guidance`, `integration`, `review-input` |
 | `layer.mvc-service` | `yss-application` | `guidance`, `integration`, `slice-implementation`, `troubleshooting`, `review-input` |
 | `layer.mvc-persistence` | `yss-repository` | `guidance`, `integration`, `slice-implementation`, `troubleshooting`, `review-input` |
 | `layer.mvc-web` | `yss-web-controller` | `guidance`, `integration`, `slice-implementation`, `troubleshooting`, `review-input` |
@@ -112,6 +114,9 @@
 | `yss-domain` | `domain-modeling` | `coordination-only` | — |
 | `yss-domain` | `yss-tactical-design` | `context-conditional` | `tactical-domain` |
 | `yss-domain` | `lombok` | `context-conditional` | `pojo` |
+| `yss-technical-design` | `yss-tactical-design` | `coordination-only` | `domain-driven` |
+| `yss-technical-design` | `yss-mvc-design` | `coordination-only` | `layered-mvc` |
+| `yss-mvc-design` | `yss-openapi-draft-review` | `review-only` | `api-impact` |
 | `yss-tactical-design` | `domain-modeling` | `coordination-only` | — |
 | `yss-tactical-design` | `yss-openapi-draft-review` | `review-only` | `api-impact` |
 | `yss-tactical-design` | `yss-repository` | `component-dependency` | `data-impact` |

package/template/.agents/skills/yss-implementation-contract-compiler/references/compiler-contract.yaml

@@ -61,6 +61,12 @@ readiness:
   data_impact: [data_architecture]
   backend_impact: [engineering_baseline, backend_repository, maven_wrapper]
   cross_repo: [repository_registry, delivery_order, integration_verification, rollback_order]
+  frontend_delivery:
+    when: specialized-frontend-profile-or-explicit-frontend-delivery-binding
+    source: docs/process/frontend-backend-delivery.md
+    verifier: scripts/verify-frontend-delivery
+    output_binding: frontend.delivery
+    inputs_verified_is_implementation_approval: false
 
 compiler_input_required:
   - slice_id
@@ -77,7 +83,7 @@ exclusive_flags:
 
 slice_contract_required:
   root: [schema_version, contract_id, contract_version, slice_id, status, lifecycle_refs, readiness, resolution, common, frontend, backend, contract, cross_repo, work_units]
-  lifecycle_refs: [spec, ticket, requirement_freeze, low_fidelity_review, prototype_review, prototype_profile_decision, prototype_deliverable, prototype_deliverable_verification, visual_baseline, prototype_confirmation, openapi_freeze_or_no_impact, architecture_review, data_architecture, tactical_design, engineering_baseline, build_architecture_checklist, implementation_repository, frontend_repository, backend_repository, maven_wrapper]
+  lifecycle_refs: [spec, ticket, requirement_freeze, low_fidelity_review, prototype_review, prototype_profile_decision, prototype_deliverable, prototype_deliverable_verification, visual_baseline, prototype_confirmation, openapi_freeze_or_no_impact, architecture_review, data_architecture, technical_design, tactical_design, engineering_baseline, build_architecture_checklist, implementation_repository, frontend_repository, backend_repository, maven_wrapper]
   readiness: [blockers, stale_inputs, not_applicable]
   resolution: [required_capabilities, required_skills, recipe_ids, conditions, reason_chains, registry_digest, compiler_contract_digest, compiled_at, freshness]
   common: [impacted_areas, implementation_path_policy, project_roots, required_capabilities, required_skills, optional_skills, unavailable_skills, allowed_write_paths, forbidden_patterns, expected_evidence_files, verification_commands, human_review_points, full_reroute_triggers, quality_baseline_ref, context_plan, doubt_driven_review]
@@ -103,6 +109,7 @@ lifecycle_ref_by_readiness:
   openapi_freeze: openapi_freeze_or_no_impact
   no_api_impact_record: openapi_freeze_or_no_impact
   data_architecture: data_architecture
+  technical_design: technical_design
   tactical_design: tactical_design
   engineering_baseline: engineering_baseline
   backend_repository: backend_repository
@@ -227,7 +234,14 @@ applicable_subcontract_nonempty:
   backend:
     scalar: [application_boundary, transaction_boundary, persistence_strategy]
     array: [affected_layers, required_skills, allowed_write_paths, forbidden_patterns, expected_evidence_files, verification_commands]
+    conditional_technical_design:
+      when: backend-technical-design-impact
+      binding: resolution.technical_design
+      scalar: [ref, version, digest]
+      architecture_match: resolution.architecture_identity.architecture_family
+      verification: node .agents/skills/yss-technical-design/scripts/validate-technical-design.mjs <contract> --root <target> --slice <slice-id>
     conditional_tactical_ddd:
+      architecture_family: domain-driven
       when: [aggregate-impact, state-machine-impact, invariant-impact, consistency-impact, domain-event-impact, gateway-boundary-impact, persistence-mapping-impact]
       scalar: [tactical_design_ref, tactical_design_version, gateway_boundary_ref]
       array: [aggregate_refs, invariant_refs, state_behavior_refs, domain_test_seams, application_test_seams]
@@ -360,7 +374,7 @@ unavailable_skill_required: [skill, provider, fallback, resolution]
 strategic_handoff_consumption:
   when: upstream-source-is-imported-strategic-handoff
   required: [import_receipt_ref, bundle_digest, context_reconciliation_ref, rows]
-  verification: scripts/verify-strategic-handoff-consumption --root <target> --slice <slice-id> <approved-tactical-contract>
+  verification: scripts/verify-strategic-handoff-consumption --root <target> --slice <slice-id> <approved-technical-design-contract>
   require_actual_exit_code: 0
   stale_policy: latest-imported-source-digest-and-dependent-slices
   unknown_dependency: block-all

package/template/.agents/skills/yss-implementation-contract-compiler/references/slice-implementation-contract.md

@@ -4,6 +4,8 @@
 
 `yss-implementation-contract-compiler` 生成草案；`yss-product-lifecycle` 核验、批准并持久化。合同缺少必填字段时状态为 `blocked`。schema v1 已停止支持，必须重新编译为 v2，不提供自动升级。
 
+采用专职前端 profile 时，`frontend.delivery` 绑定 `{acceptance_ref, digest}`，来自 `scripts/verify-frontend-delivery` 的当前结果；也可由 `resolution.frontend_delivery` 承载，两处并存时必须一致。正式执行从持久化合同读取并重验输入。细则见 `docs/process/frontend-backend-delivery.md`。
+
 ```yaml
 slice_contract:
   schema_version: 2
@@ -26,7 +28,8 @@ slice_contract:
     architecture_review:
     data_architecture:
     engineering_baseline:
-    tactical_design:
+    technical_design: # 阅读引用；与 resolution.technical_design.ref 指向同一文件
+    tactical_design: # 旧 DDD 引用兼容
     build_architecture_checklist:
     implementation_repository:
     frontend_repository:
@@ -39,6 +42,10 @@ slice_contract:
       - item:
         reason:
   resolution:
+    technical_design: # 有技术设计影响时由编译器绑定，DDD / MVC 共用
+      ref:
+      version:
+      digest: # 已持久化合同原始字节摘要
     required_capabilities: []
     required_skills: []
     recipe_ids: []
@@ -199,3 +206,5 @@ work_unit:
 `work_units` 中的前端、后端和测试任务是切片级子任务，不是新的生命周期阶段。每个子任务必须引用独立任务包；任务包只能消费同一份已批准且版本当前的 Slice Contract。`workflow_status` 追踪执行过程，不能替代生命周期状态；`contract_id`、`contract_version` 或 resolution digest 不一致时必须阻断并回到实现合同编译器。
 
 一个切片可以组合多个窄 Recipe，但只计算一次闭包。Recipe 只能引用 capability；合同同时冻结 `required_capabilities`、`required_skills`、完整原因链和 Registry/Compiler digest。任一 digest 或 Visual Baseline 版本 / digest 改变时，当前合同标记 `stale`，重新编译后仍须由 `yss-product-lifecycle` 再批准。UI 切片只消费 `visual_baseline_case_ids` 指定的图片，并先读取 manifest 与语义引用，禁止按目录 glob 猜测图片含义。
+
+技术设计编译绑定使用 `technical_design: {ref, version, digest}` 与 `slice_id`，校验器规则见 `yss-technical-design/references/technical-design-contract.md`。`backend.tactical_ddd` 仅适用于 `domain-driven`；MVC 消费共同技术设计绑定与 `design` 的用例、规则、事务和测试 seam，不填聚合或 Gateway 字段。

package/template/.agents/skills/yss-mvc-design/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: yss-mvc-design
+description: 为已确认 layered-mvc 的 YSS 项目设计分层职责、用例、业务规则、事务和持久化映射，不生成代码。
+---
+
+# YSS MVC 技术设计
+
+由 `yss-technical-design` 在 `layered-mvc` 分支调用，输入和批准边界由通用技术设计合同持有。既有工程按已登记 Profile 设计，不重选架构。
+
+必须说明模块职责与依赖方向、用例流程、业务规则、状态转换、事务边界、失败回滚、幂等与并发、持久化映射、外部集成与公开测试 seam。无状态流转或外部集成时记录有原因的不适用，不硬造对象。
+
+分层边界消费 `docs/agents/backend-architecture-profiles.md`：Controller 处理 HTTP 边界；service/core 承载用例、规则与事务；Repository 负责持久化；适用时 Adapter 承接外部集成。不得为 MVC 加载 `yss-domain` 或生成 DDD Gateway。
+
+输出 Technical Design Contract 的 `design` 分支，结构见 `references/mvc-design.schema.json`。业务规则和关键场景必须关联具体用例与测试 seam；关键场景覆盖成功和失败。与 DDD 使用同一承接和审查要求，不能因采用 MVC 省略规则、一致性或测试设计。
+
+由通用入口校验整个合同并回交生命周期独立审查。本技能不自行批准、不创建 Ticket、不设置 `ready-for-agent`，不生成 Java、SQL 或生产 API。实现由编译器按批准的架构 Profile 和最小技能闭包路由。

package/template/.agents/skills/yss-mvc-design/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "YSS MVC 技术设计"
+  short_description: "设计 MVC 用例、分层、事务和测试边界"
+  default_prompt: "基于当前批准输入和已确认架构，设计 MVC 用例、分层、事务和测试边界，返回待生命周期审查的结果。"