create-yss-spec 2.2.10 → 3.0.1

package/template/.hermes/skills/ytree-usage/SKILL.md

@@ -1,132 +0,0 @@
----
-name: ytree-usage
-description: 指导 YSS UI 左树右表、组织树、分类树、目录树和节点管理页使用 @yss-ui/components 的 YTree，覆盖 fieldNames 字段映射、搜索过滤、受控选中、节点动作、删除确认、虚拟滚动和自适应高度；当生成或修改树形筛选、左树右表、树搜索或树节点操作时使用。
----
-
-# YTree 使用
-
-## 触发条件
-
-- 生成或修改左树右表、组织树、分类树、目录树、树搜索或树节点操作。
-- 需要配置 `fieldNames`、受控选中、`YTreeActionItem` 或树区域自适应高度。
-
-## 不适用场景
-
-- 树数据只用于表单 TreeSelect 字段：使用 `YFormily` 或对应表单规范。
-- 页面只有普通列表而没有层级筛选：使用 `../ytable-usage/SKILL.md`。
-
-## 实施流程
-
-1. 当前会话可用 yss-ui MCP 时，先用 `get_component_docs` 查询 `YTree` 的 Props、Slots、Events 和 `YTreeActionItem`；需要搜索、节点动作、受控选中或左树右表时，再用 `get_demo` 获取对应官方 Demo。
-2. MCP 工具不可用、调用失败或用 `search_docs/list_components` 校正后仍无结果时，才读取最新 `llms-full.txt`；若文档与当前项目依赖版本不一致，用当前源码和导出核验。
-3. 确定树数据的 title/key/children 字段、受控状态和选中后的业务联动。
-4. 按容器布局配置 `useTreeHeight`，再添加搜索和节点动作。
-5. 若包含删除，单独完成气泡确认链路；不把 `danger` 颜色当成二次确认。
-
-## 硬约束（禁止/必须）
-
-- 从 `@yss-ui/components` 导入 `YTree`、`YTreeActionItem` 等真实导出；高度使用 `@yss-ui/hooks` 的 `useTreeHeight`。
-- 数据字段不一致时配置 `fieldNames`，不为了改名重复递归复制树数据。
-- 搜索使用 `filterable + v-model:searchValue`；受控选中使用 `v-model:selectedKeys`。
-- 普通节点菜单使用 `showActions + getNodeActions`，并监听 `@action`。`YTreeActionItem` 只支持 `key/label/icon/disabled/danger`，禁止臆造 `isConfirm/click` 等字段。
-- `danger: true` 只改变危险项视觉，不会弹出确认框。删除必须放在节点附近的 `#node-suffix` 或当前选中节点操作区，用 Ant Design Vue `Popconfirm` 的 `@confirm` 调用接口；不使用居中 `Modal.confirm`。
-- 树区域需要滚动时绑定 `:height="treeHeight"`，不默认添加 `:virtual="true"`。只有展开后可见扁平节点数 `* itemHeight > height` 时才会实际裁剪 DOM。
-- 使用 YTree 内置搜索时，高度 Hook 通过 `extraOffset: YTREE_SEARCH_HEIGHT` 扣除 48px；不再叠加无依据的魔法数。
-- 左树右表优先组合 `YSplitPane + YCard + YTree + YTable`；切换节点时同步查询条件并把右表分页重置为第 1 页。
-- 节点删除 API 的错误由 `mutator.ts` 统一提示并 reject；不在 `else/catch` 重复 `message.error`。
-
-## 标准代码骨架
-
-```vue
-<script setup lang="ts">
-import { ref } from 'vue';
-import { YTree, type YTreeActionItem } from '@yss-ui/components';
-import { useTreeHeight, YTREE_SEARCH_HEIGHT } from '@yss-ui/hooks';
-
-/** 树节点数据。 */
-interface TreeNode {
-  id: string;
-  name: string;
-  children?: TreeNode[];
-}
-
-const emit = defineEmits<{
-  create: [node: TreeNode];
-  edit: [node: TreeNode];
-}>();
-const treeAreaRef = ref<HTMLDivElement>();
-const treeData = ref<TreeNode[]>([]);
-const searchValue = ref('');
-const selectedKeys = ref<Array<string | number>>([]);
-const { treeHeight } = useTreeHeight(treeAreaRef, {
-  extraOffset: YTREE_SEARCH_HEIGHT,
-});
-
-/** 生成当前节点的非危险操作。 */
-const getNodeActions = (): YTreeActionItem[] => [
-  { key: 'add', label: '新增子节点' },
-  { key: 'edit', label: '编辑' },
-];
-
-/** 处理 YTree 动作事件。 */
-const handleTreeAction = ({ key, node }: { key: string; node: TreeNode }) => {
-  if (key === 'add') emit('create', node);
-  if (key === 'edit') emit('edit', node);
-};
-</script>
-
-<template>
-  <div ref="treeAreaRef" class="tree-area">
-    <YTree
-      :height="treeHeight"
-      :tree-data="treeData"
-      :field-names="{ title: 'name', key: 'id', children: 'children' }"
-      filterable
-      show-actions
-      v-model:searchValue="searchValue"
-      v-model:selectedKeys="selectedKeys"
-      :get-node-actions="getNodeActions"
-      @action="handleTreeAction"
-    />
-  </div>
-</template>
-
-<style scoped lang="less">
-@import './style.less';
-</style>
-```
-
-```less
-/* style.less */
-.tree-area {
-  flex: 1;
-  min-height: 0;
-  overflow: hidden;
-}
-```
-
-## 删除确认边界
-
-```vue
-<template #node-suffix="{ node }">
-  <Popconfirm title="确认删除该节点吗？" ok-text="确定" cancel-text="取消" @confirm="handleDelete(node)">
-    <YButton type="link" @click.stop>删除</YButton>
-  </Popconfirm>
-</template>
-```
-
-`Popconfirm` 从 `ant-design-vue` 导入，`YButton` 从 `@yss-ui/components` 导入。如果每个节点都展示删除会过密，把同样的 `Popconfirm` 放到选中节点的页面工具栏。
-
-## 交付检查清单
-
-- [ ] `fieldNames`、`searchValue`、`selectedKeys`、`action` 与真实 API 一致。
-- [ ] 节点动作项未出现虚构字段，删除不会点菜单后立即执行。
-- [ ] 高度偏移与内置搜索实际开关一致，没有多扣魔法数。
-- [ ] 左树选中后，右表查询条件和分页重置闭环清晰。
-
-## 失败兜底策略
-
-- 节点字段不统一时先修正 `fieldNames`，不复制整棵树换键。
-- 点击删除立即调用 API 时，移出节点动作菜单，改为节点附近或页面操作区 `Popconfirm`。
-- 传入 `height` 但节点未裁剪时，先核对展开后可见节点数、`itemHeight` 和阈值，不盲目强制 `virtual=true`。
-- 节点 API 失败后让 mutator reject 中断右表刷新等后续流程，不重复错误提示。

package/template/.kiro/settings/mcp.json

@@ -1,8 +0,0 @@
-{
-  "mcpServers": {
-    "yss-ui": {
-      "command": "npx",
-      "args": ["-y", "@yss-ui/mcp"]
-    }
-  }
-}

package/template/.pi/skills/research/SKILL.md

@@ -1,12 +0,0 @@
----
-name: research
-description: Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
----
-
-Spin up a **background agent** to do the research, so you keep working while it reads.
-
-Its job:
-
-1. Investigate the question against **primary sources** — official docs, source code, specs, first-party APIs — not a secondary write-up of them. Follow every claim back to the source that owns it.
-2. Write the findings to a single Markdown file, citing each claim's source.
-3. Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where.

package/template/.pi/skills/research/agents/openai.yaml

@@ -1,3 +0,0 @@
-interface:
-  display_name: "Research"
-  short_description: "Research from high-trust sources"

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

@@ -1,51 +0,0 @@
----
-name: yss-router
-description: Use when a YSS vertical slice is entering implementation, spans multiple frontend/backend/API areas, needs implementation readiness checked, or requires a minimal YSS skill set, Slice Implementation Contract, TDD mode, evidence plan, or reroute decision.
----
-
-# YSS Router
-
-阶段 7 的实现合同编译器。它把已批准的生命周期资产和垂直切片编译为 `Slice Implementation Contract` 草案；不批准合同、不写业务代码、不设置 `ready-for-agent`。
-
-## 输入
-
-先读取 Spec、切片 Ticket、需求冻结、适用的原型确认、OpenAPI Freeze/no-impact、系统/数据架构、Design Review、Build Architecture Checklist、实现仓库和验证命令。输入缺失、未批准或 `stale` 时输出 `blocked`，交回 `yss-product-lifecycle`。
-
-## 编译循环
-
-1. 判断 frontend/backend/API/data/domain/cross-repo 影响，并逐项填写 backend `component_impacts`；命中聚合、状态机、不变量、一致性、Domain Event、Gateway 或持久化映射时加入 `yss-tactical-design`。
-2. 检查工程存在性和核心/长尾 skill 可用性。
-3. 选择主 skill，并按 [router-contract.yaml](references/router-contract.yaml) 计算强制依赖闭包。
-4. 为切片生成基线合同；为当前行为生成工作单元增量路由。
-5. 选择 `behavior-tdd` 或 `controlled-generation`。
-6. 输出 `draft`、`blocked` 或 `ready-for-lifecycle-review`，交生命周期编排器核验和持久化。
-
-合同结构见 [slice-implementation-contract.md](references/slice-implementation-contract.md)，专项返回协议见 [yss-skill-execution-result.md](references/yss-skill-execution-result.md)。前端、后端和测试子任务必须由生命周期主控从批准的 Slice Contract 编译任务包；任务包 schema 为 `docs/process/schemas/subagent-task-package.schema.json`，技能列表必须来自 `taskPackageDefaults`，不能由 Router 或执行 Agent 另行手写。
-
-## 硬规则
-
-- Router 不得输出 `approved`、`ready-for-agent` 或 `completed`。
-- UI 影响缺少正式原型确认时，不得路由页面实现。
-- Repository/数据模型影响缺少数据架构时，不得路由持久化实现。
-- 领域影响缺少批准且版本当前的 tactical-design contract 时，不得路由 Domain 实现；无领域影响必须记录 `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` 必须为显式布尔值。
-- 当前用户、审计事件、普通技术日志、请求校验、错误映射或加解密命中时，必须按 `router-contract.yaml` 的 `component_impact_routing` 补齐长尾 skill；不能只在 `boundaries.md` 中提及。仅复用已经验证的平台认证 / 授权能力不算 component impact，不自动增加权限专项 skill。
-- 业务行为使用 `behavior-tdd`；只有机械脚手架/生成物可用 `controlled-generation`，并记录例外和验证。
-- 原型确认后若 backend `scaffold_status=required`，先由本 Router 按 `scaffold_contract_schema` 编译 `yss-ddd-scaffold-generator` 的 `controlled-generation` 工作单元合同 draft；合同必须带 `contract_id`、`contract_version`、Router draft、生命周期批准、持久化引用、允许写路径、预期证据和验证命令。经生命周期编排器批准并持久化后才能运行生成器，再由受控工作单元实际执行固定的 `./mvnw validate`、`./mvnw test`、`./mvnw package` 并记录逐条结果，随后加载 `yss-backend-scaffold-parent` 并重新编译业务合同；脚手架不承载业务行为。
-- 脚手架合同在 Router 阶段只能是 `draft` / `ready-for-lifecycle-review` / `blocked`；只有生命周期编排器可以把已持久化脚手架合同标记为 `approved`。脚手架合同只覆盖业务代码前的工程骨架工作单元；生成、基线校验和 Router 重编译完成后，它不能替代脚手架后的 Slice Implementation Contract。
-- 脚手架输出消费批准的脚手架合同；脚手架后的所有生成后端代码都必须绑定当前批准且版本当前的 Slice Implementation Contract、主 YSS skill、依赖闭包、允许写路径、预期证据和 YSS Skill Execution Result。打印命令、`./mvnw validate` 单项通过或脚手架成功不能替代合同批准；生成范围从机械内容变成业务行为时触发完整重路由。
-- 专项结果中的越界路径、缺失证据、`drift`、`violation` 或 `new_impacts` 必须阻断或重路由。
-- 前后端子任务必须使用同一 `contract_id/contract_version`，并在任务包中记录 `role_id`、`runtime_id`、`execution_state`、`allowed_write_paths`、`downstream_consumers` 和 `convergence_ref`；版本不一致或汇合引用缺失时输出 `blocked`。
-- 长尾 skill 不可用时显式 `blocked`，不得用通用知识假装已应用 YSS 规范。
-
-## 三级路由
-
-- 切片基线路由：生成完整合同和技能闭包。
-- 工作单元增量路由：绑定一个行为、主/辅 skills、TDD 模式、路径和证据。
-- 完整重路由：API/schema、状态机、数据模型、仓库、写路径、skill、测试 seam 或架构约束发生实质变化时触发。实现中出现未冻结的新行为（包括明确的权限业务行为）统一写入 `new_impacts`，由生命周期按普通影响面重新分诊。
-
-## 输出
-
-输出合同草案、技能依赖闭包、不适用理由、阻塞项、TDD 模式、工作单元、预期证据、验证命令、人工审查点、完整重路由触发器，以及建议的 `suggested_owner_role_id`（UI 影响 → `role.frontend-engineer`，后端影响 → `role.backend-engineer`，测试/审查 → `role.test-engineer`）。自然语言说明不能替代结构化合同字段。Router 不得自行批准合同、设置 `ready-for-agent` 或关闭会签门禁；owner 建议只供主控派活。

package/template/.pi/skills/yss-router/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "YSS Router"
-  short_description: "Route YSS tasks to the right skills"
-  default_prompt: "Use yss-router to choose the minimal YSS skills for this task."

package/template/.pi/skills/yss-router/references/boundaries.md

@@ -1,50 +0,0 @@
-# YSS Skill Boundaries
-
-Use this reference when multiple YSS skills seem applicable.
-
-中文说明：当多个 YSS 技能看起来都能用时，先看这个边界说明，选择最小技能组合。
-
-## Frontend Boundaries
-
-- `yss-page-module-development`: Page/module workflow. Use for creating or reorganizing a page folder, deciding structure, and assembling page, hooks, schemas, and blocks.
-- `yss-components`: Component layout and visual/page composition rules. Use for YTable/YTree/YssFormily/YSplitPane usage details.
-- `yss-hook`: Request, pagination, parameter, tree-selection, and response-mapping logic in `views/**/hooks/useXxx.ts`.
-- `yss-api-integration`: Orval-generated API client imports, request/response mapping, `useRequest` calling patterns, submit/list/detail flows.
-- `yss-formily`: Hand-written YssFormily schema implementation and form behavior.
-- `yss-formily-schema-generator`: Generate YssFormily schema from requirements, screenshots, mockups, Figma, or natural-language field descriptions.
-- `yss-use-table-height`: Only table available-height calculation and required container/pagination/toolbar wiring.
-- `yss-use-tree-height`: Only tree available-height calculation, search offset, and virtual scrolling wiring.
-
-Default for a new page: first verify the approved product design, state matrix, Ant Design v6 theme/visual-standard high-fidelity HTML prototype, schema v2 semantic mapping/browser/accessibility evidence, and user confirmation; then use the implementation lockfile to map into YSS UI + Ant Design Vue 4.x, start with `yss-page-module-development`, and add the narrow skills that match the page controls.
-
-中文说明：新建页面默认从页面模块技能开始，只有遇到具体组件、Hook、API、Formily 细节时再加载专项技能。
-
-## Backend Boundaries
-
-- `yss-ddd-scaffold-generator`: Create a whole multi-module backend skeleton.
-- `yss-domain`: Domain modeling, domain gateway contracts, and domain-layer conventions.
-- `yss-application`: Application use cases, transaction boundaries, and cross-aggregate orchestration.
-- `yss-repository`: Persistence implementation, PO, Repository, Convertor, GatewayImpl.
-- `yss-web-controller`: REST adapter layer, request/response DTOs, VO, web convertor.
-- `yss-mybatis`: Framework behavior for MyBatis/MyBatis-Plus, BaseRepository, pagination, mapper scanning, batch, datasource issues.
-- `yss-dto`: Result/PageQuery/CommandDTO/QueryDTO and unified API contract objects.
-
-Default for end-to-end backend CRUD: include Domain, Application, Infrastructure, and Web skills plus `mapstruct`, `lombok`, and `alibaba-java-code-style`; add `yss-mybatis` when persistence framework details matter. The executable closure in `router-contract.yaml` is authoritative.
-
-中文说明：后端 CRUD 按领域、DTO、持久层、Controller 分层处理；只有涉及 MyBatis 机制、分页、扫描、多数据源时才加 `yss-mybatis`。
-
-## Component Boundaries
-
-- `yss-cache`: Query/update/clear cache annotations, Redis/Caffeine/JetCache wiring, cache invalidation.
-- `yss-audit-log`: Audit annotations, SpEL summaries, async publication, subscribers.
-- `yss-excel-mvc`: Spring MVC Excel import/export annotations and handlers.
-- `yss-distributed-id`: ID strategies, AutoIdInterceptor, Leaf/CosId/Snowflake, batch ID injection.
-- `yss-resilience4j`: Circuit breaker, fallback, and gateway resilience integration.
-- `yss-validation`: Validation engine and JSR-303 integration.
-- `yss-security-algorithm`: RSA/AES/SM/JWT/JWK/password-encoding compatibility and production key-management safety gates.
-- `yss-userinfo`: Current-user info propagation and starter integration.
-- `yss-exception`: Exception component and unified exception handling.
-
-Component skills should inspect generated `references/source-index.md` before changing code when the task depends on exact class or config names.
-
-中文说明：组件类技能不要凭记忆猜类名，先用源码索引找真实位置。

package/template/.pi/skills/yss-router/references/router-contract.yaml

@@ -1,345 +0,0 @@
-schema_version: 1
-allowed_statuses: [draft, blocked, ready-for-lifecycle-review]
-forbidden_statuses: [approved, ready-for-agent, completed]
-skill_aliases:
-  api-integration: yss-api-integration
-  microapp-commit: yss-microapp-commit
-  page-module-development: yss-page-module-development
-  use-table-height: yss-use-table-height
-  use-tree-height: yss-use-tree-height
-implementation_path_policy:
-  applies_to: harness-resident-runtime-code
-  project_roots:
-    backend: apps/backend/<project>/
-    frontend: apps/frontend/<project>/
-  container_roots:
-    - apps/backend/
-    - apps/frontend/
-  forbidden_roots:
-    - app/backend/
-    - app/frontend/
-  policies:
-    - harness-apps-multi-project
-    - external-repository-native
-    - git-submodule-harness-apps
-  git_submodule:
-    repository_scope: git-submodule
-    layout_policy: git-submodule-harness-apps
-    git_entry_mode: "160000"
-    empty_gitlink_scaffold: blocked
-    treat_empty_gitlink_as_regular_dir: blocked
-    treat_detached_head_as_regular_dir: blocked
-    force_overlay_mount: blocked
-    write_inside_detached_head: blocked
-    copy_source_into_harness: forbidden
-    inspect_working_tree_writable: explicit-boolean
-    empty_gitlink_writable: false
-    force_overlay_regular_dir_path: blocked
-  rules:
-    - "Harness 内每个运行时工程必须位于具体 project 目录，不能直接写入 apps/backend/ 或 apps/frontend/。"
-    - "app/backend/、app/frontend/ 及其子路径不是兼容别名，必须阻断。"
-    - "外部实现仓库使用登记的真实项目根路径，不用 Harness 容器路径冒充。"
-    - "git-submodule 挂载路径使用 git-submodule-harness-apps，必须是 gitlink 且分别登记；不得登记为 harness-apps。"
-    - "空 gitlink、detached HEAD、--force 覆盖挂载点不得当成普通目录；也不得在 detached HEAD 工作树内当普通目录写入。"
-    - "inspectWorkingTreeScope 必须返回 { writable }；空 gitlink / detached HEAD 的 writable 必为 false；--force 覆盖 gitlink 不得走普通目录覆盖路径。"
-subcontract_statuses: [required, not-applicable]
-
-readiness:
-  common: [spec, slice_ticket, architecture_review, build_architecture_checklist, implementation_repository, verification_commands]
-  ui_impact: [requirement_freeze, low_fidelity_review, prototype_review, high_fidelity_html, prototype_verification, antd_cli_evidence, browser_verification_evidence, prototype_confirmation]
-  api_impact: [openapi_freeze]
-  no_api_impact: [no_api_impact_record]
-  data_impact: [data_architecture]
-  backend_impact: [engineering_baseline, backend_repository, maven_wrapper]
-  cross_repo: [repository_registry, delivery_order, integration_verification, rollback_order]
-
-routing_input_required:
-  - slice_id
-  - impact_flags
-  - lifecycle
-  - implementation
-  - acceptance
-impact_flags_required: [ui_impact, api_impact, no_api_impact, data_impact, backend_impact, cross_repo, existing_frozen_baseline]
-exclusive_flags:
-  - [api_impact, no_api_impact]
-
-slice_contract_required:
-  root: [schema_version, contract_id, contract_version, slice_id, status, lifecycle_refs, readiness, common, frontend, backend, contract, cross_repo, work_units]
-  lifecycle_refs: [spec, ticket, requirement_freeze, low_fidelity_review, prototype_review, high_fidelity_html, prototype_verification, antd_cli_evidence, browser_verification_evidence, 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]
-  readiness: [blockers, stale_inputs, not_applicable]
-  common: [impacted_areas, implementation_path_policy, project_roots, 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]
-  frontend: [status, required_skills, approved_prototype_ref, state_matrix_ref, allowed_write_paths, component_test_seams, e2e_paths]
-  backend: [status, affected_layers, component_impacts, required_skills, application_boundary, transaction_boundary, persistence_strategy, allowed_write_paths, forbidden_patterns, expected_evidence_files, seam_deferred, verification_commands, tactical_ddd]
-  contract: [api_impact, freeze_ref, no_api_impact_ref, generated_clients, contract_tests, regeneration_commands]
-  cross_repo: [repositories, delivery_order, integration_verification, rollback_order]
-
-lifecycle_ref_by_readiness:
-  spec: spec
-  slice_ticket: ticket
-  architecture_review: architecture_review
-  build_architecture_checklist: build_architecture_checklist
-  implementation_repository: implementation_repository
-  requirement_freeze: requirement_freeze
-  low_fidelity_review: low_fidelity_review
-  prototype_review: prototype_review
-  high_fidelity_html: high_fidelity_html
-  prototype_verification: prototype_verification
-  antd_cli_evidence: antd_cli_evidence
-  browser_verification_evidence: browser_verification_evidence
-  prototype_confirmation: prototype_confirmation
-  openapi_freeze: openapi_freeze_or_no_impact
-  no_api_impact_record: openapi_freeze_or_no_impact
-  data_architecture: data_architecture
-  tactical_design: tactical_design
-  engineering_baseline: engineering_baseline
-  backend_repository: backend_repository
-  maven_wrapper: maven_wrapper
-
-work_unit_required: [id, behavior, primary_skill, supporting_skills, tdd_mode, allowed_write_paths, expected_evidence, verification_commands, controlled_generation]
-work_unit_nonempty_arrays: [allowed_write_paths, expected_evidence, verification_commands]
-slice_contract_nonempty: [contract_id, contract_version, slice_id, status]
-slice_contract_array_fields:
-  common: [impacted_areas, implementation_path_policy, project_roots, required_skills, allowed_write_paths, forbidden_patterns, expected_evidence_files, verification_commands, full_reroute_triggers, quality_baseline_ref, context_plan, doubt_driven_review]
-
-context_plan:
-  required: [required_context_refs, on_demand_context_refs, context_stop_rule, missing_context_action]
-  context_stop_rule: minimal-sufficient-evidence
-  missing_context_action: [blocked, reroute]
-
-scaffold_contract_schema:
-  schema_version: 2
-  identity: service-engineering-baseline
-  compiled_by: yss-router
-  approved_by: yss-product-lifecycle
-  status_by_owner:
-    router: [draft, ready-for-lifecycle-review, blocked]
-    lifecycle: [approved, stale, blocked]
-  required: [contract_id, contract_version, scaffold_request_id, status, router_draft_ref, lifecycle_approval_ref, persisted_ref, current_version, implementation_repository, backend_repository, scaffold_status, project_name, target_output_dir, base_package, maven_coordinates, profiles, allowed_write_paths, expected_evidence_files, verification_commands, approval, work_unit, generation_policy]
-  approval:
-    required: [approval_ref, approver, persisted_ref, current_version]
-  generation_policy:
-    required: [mode, existing_target, old_project_migration, template_upgrade]
-    mode: initialize-only
-    existing_target: unsupported
-    old_project_migration: unsupported
-    template_upgrade: unsupported
-  maven_coordinates:
-    required: [group_id, project_version, parent, yss_components_version]
-    parent_required: [group_id, artifact_id, version]
-    yss_components_version: 2.0.0-SNAPSHOT
-  profiles:
-    required: [architecture, persistence, database, platform, validation_namespace, dto_placement, repository]
-    supported_initial:
-      architecture: target-domain-model
-      persistence: mybatis-plus
-      database: mysql
-      platform: spring-boot-2.7-jdk8
-      validation_namespace: javax
-      dto_placement: web
-      repository: yss-internal
-    unsupported: [old-architecture-profile, client-in-domain, mybatis, spring-boot-3, jakarta, separate-client-module]
-  unsupported_inputs:
-    schema_v1: reject-no-auto-upgrade
-    slice_id: forbidden-as-scaffold-identity
-    existing_project: reject-no-scaffold-migration
-  lifecycle_boundary:
-    router_emits: [draft, ready-for-lifecycle-review, blocked]
-    lifecycle_approves: [approved]
-    generator_consumes: [approved]
-    after_generation: [yss-backend-scaffold-parent, yss-router-business-contract-recompile]
-  work_unit:
-    required: [id, behavior, primary_skill, supporting_skills, tdd_mode, allowed_write_paths, expected_evidence, verification_commands, controlled_generation]
-  generation_boundary:
-    allowed_for: [project_scaffold, pom, mechanical_config, wrapper, bootstrap_entrypoint, manifest_v2, architecture_rules, test_infrastructure]
-    forbidden_when: [business_behavior, business_fields, business_state, permission, transaction, complex_query, error_mapping, business_example_crud]
-    initialization: initialize-only
-    regeneration: unsupported
-    template_upgrade: unsupported
-    old_project_migration: unsupported-separate-architecture-modernization-initiative
-  verification:
-    commands: ["./mvnw validate", "./mvnw test", "./mvnw package"]
-    requires_execution: true
-    completion_levels: [generated, empty-scaffold-verified, first-slice-verified]
-    downstream_readiness_claim_requires: first-slice-verified
-    evidence: [preflight, command, exit_code, failure_category, duration_ms, stdout_ref, stderr_ref, executed_at]
-
-applicable_subcontract_nonempty:
-  frontend:
-    scalar: [approved_prototype_ref, state_matrix_ref]
-    array: [required_skills, allowed_write_paths, component_test_seams, e2e_paths]
-  backend:
-    scalar: [application_boundary, transaction_boundary, persistence_strategy]
-    array: [affected_layers, required_skills, allowed_write_paths, forbidden_patterns, expected_evidence_files, verification_commands]
-    conditional_tactical_ddd:
-      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]
-  contract_api:
-    scalar: [freeze_ref]
-    array: [contract_tests]
-  contract_no_api:
-    scalar: [no_api_impact_ref]
-  cross_repo:
-    array: [repositories, delivery_order, integration_verification, rollback_order]
-
-dependency_closure:
-  yss-ddd-scaffold-generator:
-    always: [yss-backend-scaffold-parent, alibaba-java-code-style]
-  yss-domain:
-    always: [alibaba-java-code-style]
-    when_modeling: [domain-modeling, yss-tactical-design]
-    when_pojo: [lombok]
-  yss-tactical-design:
-    always: [domain-modeling]
-    when_api_impact: [yss-openapi-draft-review]
-    when_data_impact: [yss-repository]
-  yss-application:
-    always: [alibaba-java-code-style]
-    when_conversion: [mapstruct, lombok]
-  yss-repository:
-    always: [mapstruct, lombok, alibaba-java-code-style]
-    when_mybatis: [yss-mybatis]
-  yss-web-controller:
-    always: [yss-dto, mapstruct, lombok, alibaba-java-code-style]
-  yss-userinfo:
-    always: [yss-dto]
-    when_cache_lookup: [yss-cache]
-  yss-audit-log:
-    always: [yss-userinfo, yss-dto]
-  yss-validation:
-    always: [yss-exception]
-  yss-security-algorithm:
-    always: [yss-exception]
-  yss-exception:
-    always: [yss-dto]
-  yss-ui-business-page-generation:
-    when_components: [yss-components]
-    when_hooks: [yss-hook]
-    when_form: [yss-formily]
-    when_api: [yss-api-integration]
-  yss-page-module-development:
-    when_components: [yss-components]
-    when_hooks: [yss-hook]
-    when_form: [yss-formily]
-    when_api: [yss-api-integration]
-  yss-api-integration:
-    when_regeneration: [yss-openapi-governance]
-
-component_impact_values:
-  - current-user-context
-  - user-cache-lookup
-  - audit-event
-  - request-validation
-  - error-mapping
-  - encryption-or-signing
-
-component_impact_routing:
-  current-user-context: [yss-userinfo]
-  user-cache-lookup: [yss-userinfo, yss-cache]
-  audit-event: [yss-audit-log, yss-userinfo, yss-dto]
-  request-validation: [yss-validation, yss-exception]
-  error-mapping: [yss-exception, yss-dto]
-  encryption-or-signing: [yss-security-algorithm, yss-exception]
-
-end_to_end_backend_required:
-  - yss-domain
-  - yss-application
-  - yss-repository
-  - yss-web-controller
-  - yss-dto
-  - mapstruct
-  - lombok
-  - alibaba-java-code-style
-
-tdd_modes:
-  behavior-tdd:
-    impacts: [domain-rule, state-machine, transaction, complex-query, permission, error-mapping, page-interaction, user-visible-state]
-  controlled-generation:
-    impacts: [project-scaffold, dto-boilerplate, po-boilerplate, mapstruct-generated, frozen-openapi-client, mechanical-config]
-    required: [exception_reason, generator, generator_inputs, expected_files, verification_commands, behavior_tests_after_generation]
-
-full_reroute_triggers:
-  - scaffold-baseline-drift
-  - api-schema-impact
-  - database-schema-impact
-  - state-machine-impact
-  - data-model-impact
-  - new-write-path
-  - new-repository
-  - aggregate-impact
-  - invariant-impact
-  - consistency-impact
-  - domain-event-impact
-  - gateway-boundary-impact
-  - persistence-mapping-impact
-  - new-required-skill
-  - not-applicable-invalidated
-  - architecture-drift
-  - contract-violation
-  - generation-became-behavior
-  - test-seam-changed
-  - verification-command-changed
-  - delivery-order-changed
-  - doubt-review-triggered
-
-reroute_destinations:
-  scaffold-baseline-drift: stage7-scaffold-revalidation
-  api-schema-impact: system-data-architecture-and-contract-review
-  database-schema-impact: data-architecture-and-migration-review
-  state-machine-impact: spec-system-data-and-contract-review
-  data-model-impact: data-architecture-and-contract-review
-  new-write-path: stage7-contract-recompile
-  new-repository: stage7-contract-recompile
-  new-required-skill: stage7-contract-recompile
-  not-applicable-invalidated: lifecycle-impact-reassessment
-  architecture-drift: architecture-recheck
-  contract-violation: stage7-contract-recompile
-  generation-became-behavior: stage7-contract-recompile
-  test-seam-changed: spec-ticket-test-seam-review
-  verification-command-changed: stage7-contract-recompile
-  delivery-order-changed: cross-repo-release-review
-  doubt-review-triggered: high-risk-decision-review
-
-doubt_driven_review:
-  applies_when:
-    - api-schema-impact
-    - database-schema-impact
-    - cross-repo-contract
-    - release-or-rollback
-    - authentication-authorization-tenant-or-sensitive-data-behavior
-    - lifecycle-or-generation-semantics
-  required: [claim, counterclaim, evidence_refs, residual_risks, reviewer_ref]
-  status_values: [not-applicable, required, completed, blocked]
-  blocking_when: [missing-counterclaim, insufficient-evidence, unresolved-residual-risk]
-  evidence_owner: decision-or-review-record
-  no_new_lifecycle_stage: true
-
-quality_baseline:
-  source: lifecycle_refs.engineering_baseline
-  required_for: [project-instance]
-  reused_by: [slice-contract, yss-skill-execution-result, code-review, release]
-  redefinition: forbidden
-
-execution_result_allowed_statuses: [implemented, seam-deferred, drift, violation, not-applicable]
-execution_blockers: [path-outside-contract, missing-evidence, verification-not-executed, verification-command-mismatch, seam-deferred-without-owner, constraint-failed, doubt-review-missing, unapproved-deviation, drift, violation, new-impacts]
-
-contract_versioning:
-  full_reroute_current_status: stale
-  next_version: increment
-  required_history: [previous_contract_ref, stale_reason, reroute_trigger]
-  affected_work_units_status: paused
-
-execution_result_required:
-  - consumed_contract
-  - changed_files
-  - evidence_files
-  - verification_results
-  - constraint_results
-  - seam_deferred
-  - deviations
-  - new_impacts
-  - not_applicable_reason
-seam_deferred_required: [risk, owner, follow_up_ticket, verification_plan, target_version_or_release_date]
-deviation_required: [rule, reason, approval_ref]
-not_applicable_required: [item, reason]
-unavailable_skill_required: [skill, provider, fallback, resolution]