create-yss-spec 3.3.7 → 3.4.1

package/template/.pi/skills/yss-technical-design/scripts/validate-technical-design.mjs

@@ -1,5 +1,8 @@
 #!/usr/bin/env node
 import { readFileSync } from 'node:fs';
+import { validateEngineeringDesign } from './engineering-design.mjs';
+import { createApprovedExecutionContext, assertApprovedExecutionContext } from '../../../../scripts/lib/approved-execution-context.mjs';
+import { verifyArchitectureEvidence } from '../../../../scripts/lib/backend-architecture.mjs';
 import path from 'node:path';
 import { fileURLToPath, pathToFileURL } from 'node:url';
 import { parseArgs } from 'node:util';
@@ -39,7 +42,8 @@ function validateMvc(design) {
   if (!design.integration_catalog.length) ensure(text(design.integration_not_applicable_reason), '无外部集成必须说明原因');
 }
 
-export function verifyArchitecture(data, root) {
+export function verifyArchitecture(data, root, {execution,sliceRef}={}) {
+  if(execution)assertApprovedExecutionContext(execution,{root,technicalDesign:data,sliceId:sliceRef});
   const binding = data.architecture;
   const file = safe(root, binding.decision_ref);
   ensure(hash(readFileSync(file)) === binding.decision_digest, '架构来源摘要漂移');
@@ -57,6 +61,10 @@ export function verifyArchitecture(data, root) {
     const entry = record.repositories?.find(item => item.project_id === binding.project_id) ?? record;
     ensure(entry.project_id === binding.project_id && entry.architecture_identity?.architecture_family === binding.family, '技术设计与既有工程登记架构不匹配');
     ensure(!['stale','blocked'].includes(record.status) && !['stale','blocked'].includes(entry.status), '工程登记已失效');
+    if (entry.architecture_identity?.schema_version === 2) {
+      ensure(entry.architecture_evidence?.engineering_baseline && entry.architecture_evidence?.manifest, '既有工程登记缺少原始工程证据引用');
+      verifyArchitectureEvidence(entry.architecture_identity, { ...entry.architecture_evidence, repository_registration: { ref: binding.decision_ref, digest: binding.decision_digest } }, { root, execution });
+    }
   }
 }
 
@@ -87,14 +95,14 @@ function validateLocalTraceability(data, root, sliceRef) {
   }
 }
 
-export async function validateTechnicalDesign(data, { root = process.cwd(), sliceRef, legacyDdd = false } = {}) {
+export async function validateTechnicalDesign(data, { root = process.cwd(), sliceRef, legacyDdd = false, readOnly = false, execution } = {}) {
   if (data?.schema_version === 1) {
     ensure(legacyDdd, '旧 v1 合同需要显式 --legacy-ddd，仅按 DDD 兼容读取');
     const errors = validateDdd(data);
     ensure(!errors.length, errors.join('; '));
     if (sliceRef) ensure(data.status === 'approved', '切片只能消费 approved 设计');
     if (data.strategic_handoff || data.strategic_context_import_ref || data.upstream_impact?.source_kind === 'strategic-handoff') {
-      const result = await verifyConsumption(data, { root, sliceRef });
+      const result = await verifyConsumption(data, { root, sliceRef, readOnly });
       ensure(result.result === 'verified', JSON.stringify(result));
     }
     return { result: 'legacy-ddd-read-only', architecture_family: 'domain-driven', status: data.status };
@@ -103,12 +111,13 @@ export async function validateTechnicalDesign(data, { root = process.cwd(), slic
   ensure(data.digest === technicalDigest(data), '技术设计合同摘要不匹配');
   ensure(!['stale','blocked','drift','new_impacts'].includes(data.status), '设计状态不可消费');
   if (sliceRef) ensure(data.status === 'approved', '切片只能消费 approved 设计');
-  verifyArchitecture(data, root);
+  verifyArchitecture(data, root, {execution,sliceRef});
   ensure(data.inputs.some(item => item.kind === 'context' && item.ref === 'CONTEXT.md') && data.inputs.some(item => item.kind === 'spec'), '共同输入缺少根 CONTEXT.md 或 Spec');
   for (const input of data.inputs) ensure(hash(readFileSync(safe(root, input.ref))) === input.digest, `输入摘要漂移: ${input.ref}`);
   for (const ref of data.evidence_refs) safe(root, ref);
   if (data.status === 'approved') ensure(data.evidence_refs.length > 0, '已批准设计缺少评审证据');
-  if (data.architecture.family === 'domain-driven') {
+  if(data.design_scope==='engineering-only')validateEngineeringDesign(data,{root});
+  else if (data.architecture.family === 'domain-driven') {
     const errors = validateDdd(data.design);
     ensure(!errors.length, errors.join('; '));
     ensure(data.design.status === data.status, 'DDD 分支状态与共同合同不一致');
@@ -119,16 +128,19 @@ export async function validateTechnicalDesign(data, { root = process.cwd(), slic
   for (const seam of seams.values()) ensure(ids.has(seam.subject_ref), `测试 seam 设计对象悬空: ${seam.seam_id}`);
   validateLocalTraceability(data, root, sliceRef);
   if (data.strategic_handoff) {
-    const result = await verifyConsumption(data, { root, sliceRef });
+    const result = await verifyConsumption(data, { root, sliceRef, readOnly });
     ensure(result.result === 'verified', JSON.stringify(result));
   }
   return { result: 'ready-for-lifecycle-review', technical_design_id: data.technical_design_id, architecture_family: data.architecture.family, status: data.status, digest: data.digest };
 }
 
 async function main() {
-  const { values, positionals } = parseArgs({ allowPositionals: true, options: { root: { type: 'string', default: process.cwd() }, slice: { type: 'string' }, 'legacy-ddd': { type: 'boolean', default: false } } });
+  const { values, positionals } = parseArgs({ allowPositionals: true, options: { root: { type: 'string', default: process.cwd() }, slice: { type: 'string' }, 'legacy-ddd': { type: 'boolean', default: false }, 'read-only': {type:'boolean',default:false}, 'approved-slice': {type:'string'}, 'approved-slice-digest': {type:'string'}, 'approved-slice-approval': {type:'string'} } });
   ensure(positionals.length === 1, '用法: validate-technical-design.mjs <合同> --root <项目根> [--slice <ID>] [--legacy-ddd]');
-  const result = await validateTechnicalDesign(read(path.resolve(positionals[0])), { root: values.root, sliceRef: values.slice, legacyDdd: values['legacy-ddd'] });
+  const approvedOptions=['approved-slice','approved-slice-digest','approved-slice-approval'];
+  ensure(!approvedOptions.some(key=>values[key])||approvedOptions.every(key=>values[key]),'执行增量必须完整给出持久化 Slice、字节摘要及本地批准引用');
+  const execution=values['approved-slice']?createApprovedExecutionContext({ref:values['approved-slice'],digest:values['approved-slice-digest'],approval_ref:values['approved-slice-approval']},{root:values.root}):undefined;
+  const result = await validateTechnicalDesign(read(path.resolve(positionals[0])), { root: values.root, sliceRef: values.slice, legacyDdd: values['legacy-ddd'], readOnly:values['read-only'], execution });
   process.stdout.write(`${JSON.stringify(result, null, 2)}\n`);
 }
 if (process.argv[1] && import.meta.url === pathToFileURL(process.argv[1]).href) main().catch(error => { process.stderr.write(`${JSON.stringify({ result: 'blocked', errors: [error.message] })}\n`); process.exitCode = 1; });

package/template/.pi/skills/yss-technical-design/tests/engineering-scenarios.mjs

@@ -0,0 +1,12 @@
+import test from 'node:test';import assert from 'node:assert/strict';import fs from 'node:fs';import path from 'node:path';
+import {fixture} from '../../../../scripts/fixtures/existing-backend/fixture.mjs';
+import {validateTechnicalDesign,technicalDigest} from '../scripts/validate-technical-design.mjs';
+import {enforceTechnicalDesign} from '../../../../scripts/lib/technical-design-boundary.mjs';
+function design(f){
+ f.write('spec.md','只增加默认关闭的工程诊断；不改业务领域或数据。');f.write('api.json',{openapi:'3.1.0',paths:{'/internal/identity':{get:{operationId:'identity'}}}});
+ const binding=ref=>({ref,version:'v1',digest:f.write(ref,fs.readFileSync(path.join(f.root,ref),'utf8')).digest});
+ const data={schema_version:2,technical_design_id:'technical-design.engineering',version:'v1',status:'ready-for-human',context_ref:'CONTEXT.md',design_scope:'engineering-only',architecture:{family:f.identity.architecture_family,source_kind:'existing-registration',project_id:f.identity.project_id,decision_ref:f.bindings.repository_registration.ref,decision_digest:f.bindings.repository_registration.digest},inputs:[{kind:'context',...f.write('CONTEXT.md','# 业务上下文\n'),version:'v1'},{kind:'spec',...binding('spec.md')},{kind:'api',...binding('api.json')},{kind:'engineering',...f.bindings.engineering_baseline,version:'v1'}],source_items:[{source_id:'scenario.identity',kind:'scenario',critical:true,source_ref:'spec.md'}],traceability:[{source_id:'scenario.identity',disposition:'implemented',tactical_refs:['component.build'],test_seam_refs:['test-seam.ok','test-seam.fail'],evidence_refs:['spec.md'],dependency_status:'known',dependent_slice_refs:['slice.identity'],scenario_tests:[{outcome:'success',seam_ref:'test-seam.ok'},{outcome:'failure',seam_ref:'test-seam.fail'}]}],design:{scope_reason:'仅工程配置',impact_assessment:Object.fromEntries(['domain_model','business_state','business_rules','business_persistence','schema_migration','ui_change','architecture_boundary_change'].map(k=>[k,'none'])),component_catalog:[{component_id:'component.build',responsibility:'工程诊断资源',build_unit_ref:'app',write_paths:['pom.xml'],depends_on:[]}],allowed_write_paths:['pom.xml'],read_dependencies:[{...f.bindings.engineering_baseline,purpose:'固定构建图'}],flow:['核验固定资源','缺失时失败'],failure_handling:'503',consistency_policy:{read_only:'read-only',transaction_boundary:'no write',concurrency:'bounded',idempotency:'read',cross_database_limit:'no atomic claim',timeouts:'5seconds',recovery:'restore original'},test_seams:[{seam_id:'test-seam.ok',kind:'engineering',subject_ref:'component.build',assertion:'当前资源返回身份'},{seam_id:'test-seam.fail',kind:'engineering',subject_ref:'component.build',assertion:'坏资源拒绝'}]},evidence_refs:['spec.md']};data.digest=technicalDigest(data);return data;
+}
+for(const family of ['domain-driven','layered-mvc'])test(`${family} engineering-only preserves real architecture without invented domain models`,async t=>{const f=fixture(family);t.after(f.cleanup);const data=design(f);await validateTechnicalDesign(data,{root:f.root});assert.equal(data.design.aggregate_catalog,undefined);});
+test('engineering branch rejects domain/catalog/path/unit/write-mode/evidence/seam bypasses',async t=>{const f=fixture();t.after(f.cleanup);for(const fault of ['domain','catalog','path','unit','write','api','seam']){const data=design(f);if(fault==='domain')data.design.impact_assessment.domain_model='changed';if(fault==='catalog')data.design.aggregate_catalog=[];if(fault==='path'){data.design.component_catalog[0].write_paths=['src/main/java/application'];data.design.allowed_write_paths=['src/main/java/application'];}if(fault==='unit')data.design.component_catalog[0].build_unit_ref='missing';if(fault==='write')data.design.consistency_policy.read_only='read-write';if(fault==='api')data.inputs=data.inputs.filter(x=>x.kind!=='api');if(fault==='seam')data.traceability[0].scenario_tests=data.traceability[0].scenario_tests.slice(0,1);data.digest=technicalDigest(data);await assert.rejects(()=>validateTechnicalDesign(data,{root:f.root}),undefined,fault);}});
+test('compiler cannot downgrade domain impact to engineering-only',t=>{const f=fixture();t.after(f.cleanup);const data=design(f);data.status='approved';data.digest=technicalDigest(data);const binding={...f.write('technical.json',data),version:'v1'};assert.throws(()=>enforceTechnicalDesign({technical_design:binding,architecture_identity:f.identity,slice_id:'slice.identity',conditions:['aggregate-impact']},{root:f.root}),/engineering|工程/);});

package/template/.pi/skills/yss-ui/SKILL.md

@@ -32,7 +32,7 @@ pnpm why vue @yss-ui/components @yss-ui/hooks ant-design-vue vxe-table
 
 记录实际版本、lockfile、验证命令和环境阻塞。完整策略见 `references/antdv-compatibility.md`。
 
-产品设计使用的 Antdv Next 或 Ant Design v6 视觉/token 语义，不等于 Vue 生产实现 API。生产代码必须使用项目安装的 Ant Design Vue 4.x API，禁止把原型 props、events、slots、hook 或组件写法当作生产合同。`yss-antdv-next-design` 只用于默认 H2 Vue 原型，`yss-antd-design` 只用于显式 React 兼容原型；原型阶段不得调用本技能。只有进入前端实现计划、已批准切片的生产实现或实现还原验证后，才从目标 lockfile、类型、本地文档和既有用法取得真实组件事实。
+产品设计使用的 Antdv Next 或 Ant Design v6 视觉/token 语义，不等于 Vue 生产实现 API。生产代码必须使用项目安装的 Ant Design Vue 4.x API，禁止把原型 props、events、slots、hook 或组件写法当作生产合同。原型统一使用 HTML/CSS/JavaScript；原型阶段不得调用本技能。只有进入前端实现计划、已批准切片的生产实现或实现还原验证后，才从目标 lockfile、类型、本地文档和既有用法取得真实组件事实。
 
 ## 3. 组件选型门禁
 
@@ -56,7 +56,7 @@ pnpm why vue @yss-ui/components @yss-ui/hooks ant-design-vue vxe-table
 | 任务 | 必须路由 |
 |---|---|
 | 新建或改造完整业务页面 | `yss-ui-business-page-generation` |
-| 页面布局、组件和交互 | `yss-components` |
+| 页面布局与无独立 Skill 的专项组件 | `page-skeleton`、`component-selection-imports`、`references/specialized-components.md` |
 | 请求、分页、参数、树数据映射 | `yss-hook` |
 | Formily schema、联动、校验、详情态 | `yss-formily` |
 | 表格高度 | `yss-use-table-height` |
@@ -153,6 +153,7 @@ verification: pnpm type-check
 ## 10. 按需读取
 
 - 组件路由：`references/component-routing.md`
+- 无独立 Skill 的专项组件：`references/specialized-components.md`
 - 版本兼容：`references/antdv-compatibility.md`
 - 主题/locale/浮层：`references/theme-locale-overlay.md`
 - 可访问性与性能：`references/accessibility.md`

package/template/.pi/skills/yss-ui/references/component-routing.md

@@ -6,17 +6,18 @@
 |---|---|---|---|---|
 | 普通按钮、权限按钮 | `YButton` | AntDV Button | required | 权限、主题和统一动作语义；不得直接导入 Button |
 | 卡片 | `YCard` | AntDV Card | required | YSS 布局与间距扩展 |
-| 数据表格 | `YTable` | VXE Table + AntDV Pagination | specialized | 使用 `yss-components`、`field/type`、字段插槽 |
-| 编辑表格 | `YEditTable` | VXE Table | specialized | 对照 edit-table docs/demo |
-| 树 | `YTree` | AntDV Tree | specialized | 搜索、Tooltip、动作和高度路由 |
+| 数据表格 | `YTable` | VXE Table + AntDV Pagination | specialized | 使用 `ytable-usage`；远程分页交给 `page-list-module`，高度交给 `yss-use-table-height` |
+| 编辑表格 | `YEditTable` | VXE Table | specialized | 使用 `yedit-table-usage`，不要把编辑与普通展示表格混为一套 API |
+| 树 | `YTree` | AntDV Tree | specialized | 使用 `ytree-usage`；高度交给 `yss-use-tree-height` |
 | Schema 表单 | `YFormily` | Formily + AntDV | specialized | `YFormily` 为 canonical；`YssFormily` 仅为历史兼容名；加载 `yss-formily` |
-| 分栏布局 | `YSplitPane` | YSS layout | required | 统一主从页面与容器高度 |
-| 文件导入 | `YFileImport` | Upload/业务适配 | required | 使用 YSS 上传结果和表单适配 |
-| 条件构建 | `YConditionBuilder` | YSS domain component | required | 使用对应 docs/demo |
-| Cron | `YCron` | YSS domain component | required | 底层 Popover 可 fallback |
-| 图表 | `YEcharts` | ECharts | required | 主题、resize、darkMode 使用 YSS API |
-| 编辑器 | `YMonaco` | Monaco | required | 按需加载和尺寸治理 |
-| Sheet | `YSheet` | Univer | required | locale 与资源包按 YSS 文档 |
+| 分栏布局 | `YSplitPane` | YSS layout | required | 页面骨架使用 `page-skeleton`；组件边界见 `specialized-components.md` |
+| 文件导入 | `YFileImport` | Upload/业务适配 | required | 两步导入边界见 `specialized-components.md` |
+| 条件构建 | `YConditionBuilder` | YSS domain component | required | 标准模型与校验边界见 `specialized-components.md` |
+| 月历 | `YMonthCalendar` | YSS domain component | required | 日期、月份、高度与事件边界见 `specialized-components.md` |
+| Cron | `YCron` | YSS domain component | required | 七段表达式边界见 `specialized-components.md` |
+| 图表 | `YssEcharts` | ECharts | required | 主题、更新和尺寸边界见 `specialized-components.md` |
+| 编辑器 | `YMonaco` / `YMonacoDiff` | Monaco | required | 按需加载和尺寸治理见 `specialized-components.md` |
+| Sheet | `YSheet` | Univer | required | Facade、释放和依赖边界见 `specialized-components.md` |
 | 输入、选择、日期 | 无独立通用 Wrapper | AntDV Input/Select/DatePicker 等 | fallback | 读取实际 AntDV 版本；服从 theme/locale/popup 规则 |
 | 浮层反馈 | 无统一 Wrapper | Modal/Drawer/Popover/Tooltip/Alert | fallback | 服从容器、焦点、销毁、z-index 规则 |
 | 服务式反馈 | 无统一 Wrapper | message/notification | fallback | 检查 App/ConfigProvider 上下文 |

package/template/.pi/skills/yss-ui/references/specialized-components.md

@@ -0,0 +1,52 @@
+# YSS 专项组件契约
+
+本文件只承载尚无独立 Skill 的组件边界。页面编排使用 `yss-ui-business-page-generation`，表格、树、Formily、请求和高度分别加载对应专项 Skill。
+
+## YSplitPane
+
+- 轻内容可使用实时拖拽；树、宽表、编辑器、图表等重内容优先 `resize-mode="deferred"` 与 `collapse-animation="transform"`。
+- 尺寸受控时使用 `v-model:left-width`，纵向使用 `v-model:top-height`；`storage-key` 只保存尺寸，不替代页面状态。
+- 折叠默认保留内容状态。只有允许丢失展开、勾选、滚动等内部状态时才启用销毁。
+
+## YConditionBuilder
+
+- 根值是 `ConditionGroup`；叶子保持字段、操作符和值的标准模型。接口 DSL 的序列化、恢复与错误兜底放入 Hook。
+- 字段切换需要动态操作符或候选值时使用组件公开的加载入口；提交前执行公开校验。
+- 默认严格校验，只有明确允许未完成草稿时才关闭；展示态使用 `disabled`，不使用已废弃的 `readonly`。
+- 组件资料见 `../assets/component-docs/condition-builder-*`，实现前仍须核对目标项目安装版本。
+
+## YMonthCalendar
+
+- `v-model` 管理选中日期，`v-model:month` 管理展示月份，不把二者当作日期范围。
+- `valid-range` 限制范围，`disabled-date` 表达业务禁用日期；业务层仍需规范化起止输入。
+- 自定义日期单元格应保留 today、selected、disabled 等状态语义。
+- `fill-height` 仅用于父容器已有明确高度的场景；键盘、右键和双击动作使用公开事件，不覆盖默认焦点行为。
+
+## YFileImport
+
+- 文件选择、预检、结果回显和最终确认组成两步流程；业务上传与校验由 `nextStep` / `finalImport` 接入。
+- 默认 `beforeUpload=false`，不能期待 `action` 自动上传；直传只通过 `upload-props.customRequest`。
+- `importResult` 展示结果，失败数据通过 `exportErrorData` 下载。弹窗配置与上传器配置保持分离。
+- 组件资料见 `../assets/component-docs/file-import-*`。
+
+## YMonaco / YMonacoDiff
+
+- 分栏折叠或 Drawer 打开等容器尺寸变化后确认已重新布局。
+- 日志增量使用 `appendContent()`，避免频繁重设超大完整字符串。
+- 编辑器必须按需加载并在页面卸载时释放相关资源。
+
+## YCron
+
+- 业务值是七段表达式：秒、分、时、天、月、周、年。
+- 页面只负责双向绑定和禁用态；时区、后端模型转换和生效校验属于 API/Hook 层。
+
+## YSheet
+
+- 必须提供明确容器高度。
+- 初始化后只通过公开 Facade API 修改工作簿，并通过公开保存入口取值；不得直接修改工作簿原始数据对象。
+- 卸载时释放实例，接入前确认 Univer、React、RxJS 等可选依赖及包体影响。
+
+## YssEcharts
+
+- option、更新策略和容器尺寸以目标版本手册与项目已验证实践为准。
+- 不在页面层重复原生 ECharts 初始化、销毁或 ResizeObserver 管理。

package/template/.pi/skills/yss-web-controller/SKILL.md

@@ -7,7 +7,7 @@ description: Use when generating or refactoring YSS Web Adapter Controllers, req
 
 ## 架构分流（先执行）
 
-读取当前合同的 architecture_identity 并与工程基线、仓库登记及 Manifest 核对；再且只读取 `references/profiles/<architecture_profile>.md`。支持的分支为 target-domain-model、layered-mvc-service、mvc-data-analysis-v1；成熟度以注册表为准，不能把 draft 称为受支持。MVC 不执行下文 DDD 专属规则，也不加载其旧分层 guide；组件、安全、批准合同、允许路径及执行证据规则仍共用。
+读取当前合同的 architecture_identity 并与工程基线、仓库登记及 Manifest 核对；再且只读取 `references/profiles/<architecture_profile>.md`。生成式分支为 target-domain-model、layered-mvc-service、mvc-data-analysis-v1；既有工程分支为 existing-domain-driven-maven、existing-layered-mvc-maven。成熟度以注册表为准，不能把 draft 称为受支持。MVC 不执行下文 DDD 专属规则，也不加载其旧分层 guide；组件、安全、批准合同、允许路径及执行证据规则仍共用。
 
 以下 Application / Domain Gateway / Infrastructure / Web module 叙述仅适用于 target-domain-model；MVC 的 service/core/repository/server/client 所有权由所选 Profile 引用定义。
 

package/template/.pi/skills/yss-web-controller/references/profiles/existing-domain-driven-maven.md

@@ -0,0 +1,5 @@
+# existing-domain-driven-maven
+
+只用于 `source_kind=existing-registration` 且 `architecture_family=domain-driven` 的受支持身份。先核验登记、工程基线、独立观测 manifest 和边界审查的当前摘要，再以工程基线中的实际 build unit、source root、package 与 architecture responsibility 映射确定 Web 落点；不得要求模板模块名、数量或生成器 manifest。
+
+Controller 只暴露冻结接口并调用合同指定的 Application 或 engineering-only orchestration seam。若批准合同将只读工程探针放在实际 Web build unit 内且没有 Application 源码写路径，保持该边界，不为满足生成式目录结构新建模块、聚合、Gateway 或业务服务。请求参数、Result 包装、错误脱敏、允许路径和真实 Maven/JAR 验证仍按共用规则执行。实际映射不清、越出登记源码根或改变业务架构时返回 `blocked`。

package/template/.pi/skills/yss-web-controller/references/profiles/existing-layered-mvc-maven.md

@@ -0,0 +1,5 @@
+# existing-layered-mvc-maven
+
+只用于 `source_kind=existing-registration` 且 `architecture_family=layered-mvc` 的受支持身份。以登记、工程基线、独立观测 manifest 与边界审查中的实际 build unit、source root、package 和 responsibility 映射确定 Controller/server 落点；模块名和数量可以与模板不同，不补造生成器或脚手架合同。
+
+Controller 只调用已登记的 service/use-case seam，保持公开 DTO、私有 DTO、错误脱敏和事务责任的实际映射。批准合同若只允许现有 build unit 内的 engineering-only seam，不得为套用生成式结构新建 client/server/service 模块。映射不清、Controller 直连 Repository、越界路径或业务架构变化均返回 `blocked`。

package/template/.pi/skills/yss-web-controller/scripts/generate_controller.mjs

@@ -158,12 +158,13 @@ async function validateContract(contract, args) {
   if (manifestPath !== path.resolve(contract.scaffold_manifest_ref)) throw new Error("--scaffold-manifest-file does not match the approved web generation contract");
   if (!await exists(manifestPath)) throw new Error(`scaffold manifest not found: ${manifestPath}`);
   const manifest = JSON.parse(await readFile(manifestPath, "utf8"));
-  if (![2, 3].includes(manifest.schema_version)) throw new Error("scaffold manifest must use historical schema_version=2 or current schema_version=3");
-  if (mvc && manifest.schema_version !== 3) throw new Error("MVC requires schema v3 scaffold identity");
+  if (![2, 3, 4].includes(manifest.schema_version)) throw new Error("scaffold manifest must use supported schema_version=2/3/4");
+  if (manifest.schema_version === 3 && manifest.legacy_reconciliation?.status !== "approved") throw new Error("historical schema v3 scaffold requires approved legacy reconciliation before business generation");
+  if (mvc && ![3, 4].includes(manifest.schema_version)) throw new Error("MVC requires schema v3/v4 scaffold identity");
   if (manifest.architecture_identity || mvc) {
     assertArchitectureAgreement(contract.architecture_identity, { manifest });
     if (contract.architecture_identity.architecture_profile !== contract.architecture_profile) throw new Error("Web architecture profile differs from its identity");
-  } else if (manifest.schema_version === 3 && (manifest.architecture_family !== "domain-driven" || manifest.generator_skill !== "yss-ddd-scaffold-generator")) throw new Error("schema v3 scaffold manifest must bind the domain-driven generator for Web adapter generation");
+  } else if (manifest.schema_version >= 3 && (manifest.architecture_family !== "domain-driven" || manifest.generator_skill !== "yss-ddd-scaffold-generator")) throw new Error("schema v3/v4 scaffold manifest must bind the domain-driven generator for Web adapter generation");
   if (!["empty-scaffold-verified", "first-slice-verified"].includes(manifest.completion_level)) throw new Error("scaffold manifest must be empty-scaffold-verified before Web generation");
   const scaffoldRoot = path.dirname(path.dirname(manifestPath));
   if (implementationRoot !== scaffoldRoot) throw new Error("implementation_project_root does not match the scaffold manifest project root");

package/template/.pi/skills/yss-web-controller/scripts/generate_controller.test.mjs

@@ -20,7 +20,7 @@ for (const [profile, module, placement, modules, generator] of [
   const identity = { architecture_family: "layered-mvc", architecture_profile: profile, generator_skill: generator, requested_capabilities: [], resolved_modules: modules, contract_digest: "a".repeat(64), verification_database: "h2", production_database: "not-bound" };
   const project = path.join(data.root, "demo-service");
   const manifestFile = path.join(project, ".yss/scaffold-generation.json");
-  const manifest = { schema_version: 3, project_name: "demo-service", base_package: "com.yss.demo", completion_level: "empty-scaffold-verified", architecture_identity: identity, profiles: { platform: "spring-boot-2.7-jdk8", validation_namespace: "javax" } };
+  const manifest = { schema_version: 4, project_name: "demo-service", base_package: "com.yss.demo", completion_level: "empty-scaffold-verified", architecture_identity: identity, profiles: { platform: "spring-boot-2.7-jdk8", validation_namespace: "javax" } };
   await mkdir(path.dirname(manifestFile), { recursive: true });
   await writeFile(manifestFile, JSON.stringify(manifest));
   const contract = webContract(project, { architecture_profile: profile, architecture_identity: identity, dto_placement: placement, integration_mode: "scaffold-v2", scaffold_manifest_ref: manifestFile, platform_profile: "spring-boot-2.7-jdk8", validation_namespace: "javax", application_service_package: `com.yss.demo.${module}.service` });

package/template/CONTEXT.md

@@ -46,6 +46,7 @@ context_schema_version: 1
 | `ready-for-agent` | 表示垂直切片已通过必要门禁并具备直接实现条件的流程状态。 | — | 不得用于 Spec 初稿、原型、OpenAPI Draft 或其他未冻结资产。 |
 | OpenAPI Draft | review-only 的 OpenAPI 3.1 契约草案。 | — | Freeze 前不得作为前后端稳定实现契约。 |
 | OpenAPI Freeze | 已通过评审、可作为前后端实现和契约测试输入的 OpenAPI 3.1 契约。 | — | Freeze 后变更必须回到 API 影响分析和设计审查。 |
+| API Contract Decision | 以原始字节摘要记录 API 影响结论；有影响时闭包绑定 OpenAPI Draft、Validation、独立 Review 与 Freeze，无影响时绑定评估、原因和证据。 | — | 与 Technical Design、Data Architecture Decision 一起由 `gate.engineering-contract-approved` 原子批准；不得用空 OpenAPI 或字符串自证代替。 |
 | YSS 响应包装 | 对外 API 使用 `Result` 基础字段及 `SingleResult`、`MultiResult`、`PageResult` 表达单对象、非分页列表和分页查询结果的统一返回结构。 | — | Java 泛型记法是语义简称；公开 schema 必须落成具体 endpoint wire shape。 |
 | DTO wire shape | DTO 在 HTTP/JSON 边界实际暴露的字段、类型、可空性和方向性；与 Java 字段、getter 或内部协作字段区分。 | — | 以目标 mapper / contract evidence 为准，不从 getter、Lombok 或 `@JsonIgnore` 机械推断。 |
 | UI 影响 | 会改变用户可见页面、导航、交互流程、状态呈现或权限体验的功能影响。 | — | 纯后端、API、批处理或数据变更不自动构成 UI 影响。 |

package/template/DESIGN.md

@@ -1,7 +1,7 @@
 ---
 version: alpha
-name: YSS Enterprise Design System
-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.
+name: YSS Data Quality Design System
+description: A machine-readable Data Quality default visual contract for YSS enterprise applications, aligned with YSS enterprise visual semantics and framework-independent HTML prototypes. It complements the product lifecycle and does not define product behavior, API contracts, permissions, or business states.
 
 colors:
   primary: "#3371ff"
@@ -17,6 +17,7 @@ colors:
   surface: "#ffffff"
   surface-elevated: "#ffffff"
   surface-subtle: "#fafafa"
+  border: "#d9d9d9"
   border-secondary: "#f0f0f0"
   success: "#52c41a"
   success-bg: "#f6ffed"
@@ -70,53 +71,57 @@ spacing:
   xs: 8px
   sm: 12px
   md: 16px
+  card: 20px
   lg: 24px
   xl: 32px
   xxl: 48px
 
 components:
+  separator:
+    backgroundColor: "{colors.border}"
+    height: 1px
   button-primary:
     backgroundColor: "{colors.primary-control}"
     textColor: "{colors.on-primary}"
     typography: "{typography.button}"
     rounded: "{rounded.md}"
     padding: "{spacing.xxs} {spacing.sm}"
-    height: 28px
+    height: 32px
   button-primary-hover:
     backgroundColor: "{colors.primary-control-hover}"
     textColor: "{colors.on-primary}"
     typography: "{typography.button}"
     rounded: "{rounded.md}"
     padding: "{spacing.xxs} {spacing.sm}"
-    height: 28px
+    height: 32px
   button-primary-disabled:
     backgroundColor: "{colors.border-secondary}"
     textColor: "{colors.text-tertiary}"
     typography: "{typography.button}"
     rounded: "{rounded.md}"
     padding: "{spacing.xxs} {spacing.sm}"
-    height: 28px
+    height: 32px
   button-default:
     backgroundColor: "{colors.surface}"
     textColor: "{colors.text}"
     typography: "{typography.button}"
     rounded: "{rounded.md}"
     padding: "{spacing.xxs} {spacing.sm}"
-    height: 28px
+    height: 32px
   input-default:
     backgroundColor: "{colors.surface}"
     textColor: "{colors.text}"
     typography: "{typography.body}"
     rounded: "{rounded.md}"
     padding: "{spacing.xxs} {spacing.xs}"
-    height: 28px
+    height: 32px
   input-error:
     backgroundColor: "{colors.surface}"
     textColor: "{colors.text}"
     typography: "{typography.body}"
     rounded: "{rounded.md}"
     padding: "{spacing.xxs} {spacing.xs}"
-    height: 28px
+    height: 32px
   table-header:
     backgroundColor: "{colors.surface-subtle}"
     textColor: "{colors.text}"
@@ -139,7 +144,7 @@ components:
     typography: "{typography.button}"
     rounded: "{rounded.md}"
     padding: "{spacing.xxs} {spacing.sm}"
-    height: 28px
+    height: 32px
   page-shell:
     backgroundColor: "{colors.canvas-layout}"
     textColor: "{colors.text}"
@@ -196,6 +201,18 @@ components:
   secondary-copy:
     textColor: "{colors.text-secondary}"
     typography: "{typography.caption}"
+  card-default:
+    backgroundColor: "{colors.surface}"
+    textColor: "{colors.text}"
+    typography: "{typography.body}"
+    rounded: "{rounded.lg}"
+    padding: "{spacing.card}"
+  button-compact:
+    height: 28px
+  button-small:
+    height: 24px
+  button-large:
+    height: 40px
   card-compact:
     backgroundColor: "{colors.surface}"
     textColor: "{colors.text}"
@@ -209,11 +226,11 @@ components:
 
 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 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.
+The default theme adopts Data Quality global tokens on the Ant Design v6 design foundation: light mode, primary #3371ff, body 14px, controls 32/24/40px, radii 6/4/8px and card padding 20px. Compact and dark modes are opt-in. Data Quality runs Vue 3 + Ant Design Vue 4.2.6 + YSS UI; that runtime version is distinct from the design foundation. Client-specific JSP themes and page-local glass effects are not defaults. Prototypes use HTML/CSS/JavaScript with local token CSS. Production applications use the target implementation contract and lockfile; prototype visuals do not establish production component API compatibility.
 
 ## 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.
+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. The brand seed remains Data Quality #3371ff; primary-control #245bdb and its hover variant are deliberate YSS accessibility adaptations for white small text, not values copied from Data Quality. State colors must be paired with readable text or an icon and must meet WCAG 2.2 AA.
 
 ## Typography
 
@@ -221,7 +238,7 @@ Use the system font stack, 14px body text and 400/600 weights. Use `caption` onl
 
 ## Layout
 
-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.
+Use a 4px spacing grid and the spacing tokens above. Use the default 32px control variant directly in HTML prototypes. The explicit compact variant uses 28px; small and large controls use 24px and 40px. When production uses an Ant Design theme algorithm, keep its seed `controlHeight` at 32px and apply compact once; never seed 28px and 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
 
@@ -233,12 +250,12 @@ Controls use `rounded.md` (6px); cards and overlays use `rounded.lg` (8px); comp
 
 ## Components
 
-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.
+The component keys above describe default visual variants and explicitly named optional sizes, not business states. Default controls use a 32px 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 consume tokens through ConfigProvider, CSS variables or the target component library theme.
-- Do compose `compactAlgorithm` with `darkAlgorithm` for dark compact work surfaces.
+- Do use the verified derived dark/compact token snapshot for HTML; production theme algorithms remain implementation-specific.
 - 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.

package/template/README.md

@@ -42,15 +42,15 @@
 4. `project-instance` 默认从 `yss-product-lifecycle` 的 `route` 模式开始，再由原生 `work-unit.*` 推进 Plan、Spec、产品设计、工程契约和 Ticket 正式化；`grill-with-docs`、`to-spec`、`to-tickets`、`implement` 仅作为用户显式调用的兼容入口。
 5. 实现仓库接入、YSS 路由、独立审查、fresh verification 和 Git checkpoint 以 `AGENTS.md` 的硬门禁为准。
 
-YSS skills 的公开发布投影维护在 [iloveZzz/yss-spec-dev-skills](https://github.com/iloveZzz/yss-spec-dev-skills)，发布清单和导出命令见 [skills 维护说明](./docs/agents/skills-maintenance.md)。
 
 YSS UI 组件知识同时通过项目级 MCP 配置提供；支持的客户端、Codex 全局安装和自检方法见 [YSS UI MCP 接入](./docs/user-guide/yss-ui-mcp.md)。
 
 ## 模板初始化 CLI
 
-`create-yss-spec` 的目标维护位置是独立 GitHub 仓库 [iloveZzz/create-yss-spec](https://github.com/iloveZzz/create-yss-spec)。本仓库不再包含 CLI 源码、测试、发布配置或开发过程记录。CLI 的使用方法已经合并到统一用户手册：
+`create-yss-spec` 的发布仓库是 [iloveZzz/create-yss-spec](https://github.com/iloveZzz/create-yss-spec)。用户从统一手册选择家族；CLI 源码、测试、打包和发布仍在各自仓库维护：
 
-- [YSS 用户手册：创建、接管和更新项目](./docs/user-guide/用户手册.md#创建接管和更新项目)
+- [YSS 用户手册：CLI 能力与写入方式](./docs/user-guide/用户手册.md#cli-能力与写入方式)
+- [YSS 用户手册：接管、同步与恢复](./docs/user-guide/用户手册.md#接管同步与恢复)
 
 推荐入口：
 
@@ -106,11 +106,9 @@ scripts/verify-template-fast
 | [docs/process/MATT-POCOCK-ENGINEERING-SKILLS.md](./docs/process/MATT-POCOCK-ENGINEERING-SKILLS.md) | Matt Pocock Engineering Skills 集成与使用 |
 | [docs/process/lifecycle-registry.yaml](./docs/process/lifecycle-registry.yaml) | 生命周期结构事实源：主阶段、门禁、产物、工作单元、证据与稳定 ID |
 | [docs/process/harness-process-tailoring.md](./docs/process/harness-process-tailoring.md) | 小改动 / 中等变更 / 新模块的流程裁剪指南 |
-| [docs/process/template-engineering-overview.md](./docs/process/template-engineering-overview.md) | 模板工程定位、产品线、控制平面、分发边界与维护工作流 |
 | [docs/process/harness-executive-blueprint.md](./docs/process/harness-executive-blueprint.md) | 面向业务方和管理者的 Harness 一页式蓝图 |
 | [docs/process/implementation-repo-integration.md](./docs/process/implementation-repo-integration.md) | 外部前端 / 后端实现仓库接入与跨仓库切片绑定 |
 | [docs/agents/README.md](./docs/agents/README.md) | Agent 协作文档目录说明 |
-| [docs/agents/skills-maintenance.md](./docs/agents/skills-maintenance.md) | Agent skills 安装与维护 |
 | [docs/user-guide/yss-ui-mcp.md](./docs/user-guide/yss-ui-mcp.md) | YSS UI MCP 项目配置、全局安装边界与自检 |
 | [docs/plan/IDEATION.md](./docs/plan/IDEATION.md) | 机会构想方法 |
 | [docs/architecture/README.md](./docs/architecture/README.md) | 架构设计 + 审查清单 |
@@ -130,4 +128,4 @@ scripts/verify-template-fast
 
 ## 按职责使用与升级
 
-[五类项目用户手册](docs/user-guide/用户手册.md)提供选型、初始化及升级；[设备借用贯穿案例](docs/user-guide/设备借用贯穿案例.md)演示战略、后端、前端与统一验收。[全部手册](docs/user-guide/用户手册索引.md)区分日常使用与维护入口。GitHub 当前能力与 npm 发布快照分别核对。
+[四个现行家族用户手册](docs/user-guide/用户手册.md)提供选型、初始化及升级；[设备借用贯穿案例](docs/user-guide/设备借用贯穿案例.md)演示战略、后端、前端与统一验收。[全部手册](docs/user-guide/用户手册索引.md)给出本体和子项目入口。GitHub 当前能力、npm 发布版本与实例模板快照分别核对。

package/template/__yss_dotfile__.gitignore

@@ -20,6 +20,10 @@ dist/
 .env
 .env.*
 !.env.example
+# Public scaffold mode files (no credentials)
+!**/yss-frontend-scaffold-generator/assets/data-quality-v1/packages/.env.development
+!**/yss-frontend-scaffold-generator/assets/data-quality-v1/packages/.env.production
+!**/yss-frontend-scaffold-generator/assets/data-quality-v1/packages/.env.production.standalone
 *.pem
 
 # Database

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

@@ -4,6 +4,10 @@ Profile、模块闭包、生成器、成熟度和 Recipe 的权威映射见 `yss
 
 执行前比较工程基线、仓库登记、Manifest 与当前合同的 `architecture_identity`。缺失、digest 漂移、Profile 不匹配或越界写路径均停止；既有工程不能自动重选架构。新 Profile 的真实编译及首切片验证未通过前保持 `draft`，不能设置 `ready-for-agent`。
 
+## 既有工程适配
+
+`existing_project_profiles` 与下述生成器 Profile 独立维护。首版两个 Maven 适配器通过真实 Git/POM 三方核验、对应架构的成功/失败行为测试与 Maven test/package 后标记 supported；依据见 `.template-source/evidence/maintenance/2026-09-12-existing-project-delivery/maven-adapters-04.json`。这是适配协议支持证据，不是实际产品批准、数据库兼容或真实跨仓 S0 结论。每个工程仍须自己的固定来源、架构边界审查和执行证据，详见 `docs/process/existing-backend-architecture.md`。生成器原有 draft 和首切片要求保持。
+
 ## MVC 分层
 
 - `layered-mvc-service` 的用例层为 `service`；`mvc-data-analysis-v1` 的用例层为 `core`。后者是薄应用层，不是合并 Domain 的容器。MVC 不加载 `yss-domain`，不生成 DDD Gateway。

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

@@ -88,10 +88,10 @@ roles:
     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 ]
+    core_skills: [ yss-design-system, yss-prototype-stage, prototype-review, 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. Prototypes use offline HTML/CSS/JavaScript and project DESIGN.md; production component facts remain downstream.
 
   - id: role.project-manager
     name: 项目经理
@@ -112,7 +112,7 @@ 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-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 ]
+    core_skills: [ yss-ui, yss-ui-business-page-generation, yss-formily, 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.
@@ -125,7 +125,7 @@ roles:
     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 ]
+    forbidden_skills: [ yss-ui, yss-ui-business-page-generation, yss-formily, yss-frontend-scaffold-generator, 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.
 

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

@@ -2,6 +2,20 @@
 
 本文记录已退役技能入口的迁移路径。退役技能不保留物理目录、投影或 lock 条目；本文件是历史名称的唯一持久兼容说明。
 
+## DDD 分层包装与前端组件总入口收敛（2026-09-15）
+
+以下入口已硬退役，不保留 alias、物理目录、投影或 lock 条目：
+
+- DDD 嵌套包装：`yss-backend-scaffold-adapter`、`yss-application-layer-reference`、`yss-domain-layer-reference`、`yss-infrastructure-layer-reference`、`yss-web-layer-reference`。
+- 旧数据分析初始化器：`yss-mvc-scaffold-generator`，新工作使用 `yss-mvc-data-analysis-project-initializer`；通用 MVC 使用 `yss-layered-mvc-scaffold-generator`。
+- 前端组件总入口：`yss-components`。
+
+DDD 脚手架只保留已登记并被生成合同消费的 `yss-backend-scaffold-parent`。生成后的 Application、Domain、Infrastructure、Web 和 Adapter 实现从 `yss-ddd-scaffold-generator/references/layer-skill-routing.md` 路由到顶层权威 Skill，不再把普通参考目录暴露为可发现 Skill。
+
+前端页面统一从 `yss-ui` 路由：页面骨架使用 `page-skeleton`，组件选型使用 `component-selection-imports`，表格、树、Formily、Hook 和高度使用各自专项 Skill；没有独立 Skill 的复杂组件契约集中在 `yss-ui/references/specialized-components.md`。`yss-formily` 保留为薄路由器，不再复制表单代码骨架和专项规则。
+
+旧 ID 只允许存在于本迁移记录、retired/obsolete 清单、负向测试和不可变历史证据中。
+
 ## 技能面收敛与前端入口合并（2026-09-05）
 
 以下 Skill 已一次性硬退役，不保留 alias、兼容目录、投影或 lock 条目：
@@ -39,8 +53,7 @@
 - 阶段合同：`yss-prototype-stage`
 - 原型档位与主入口：`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`
+- 当前 H1/H2：根 `DESIGN.md` 驱动的离线 HTML/CSS/JS；旧 Provider 路线见下方退役记录
 - 真实组件核验：不属于原型档位；进入已批准切片后由 `yss-ui` 基于目标 lockfile 执行，并写入前端实现验证
 - 独立低保真评审：`prototype-review`