create-yss-spec 2.2.10 → 3.0.1

package/template/.hermes/skills/yss-prototype-stage/tests/run-scenarios.mjs

@@ -1,154 +0,0 @@
-#!/usr/bin/env node
-import assert from "node:assert/strict";
-import { mkdtemp, mkdir, readFile, writeFile } from "node:fs/promises";
-import os from "node:os";
-import path from "node:path";
-import {
-  preparePrototype,
-  validatePrototypeEvidence,
-  validatePrototypeProject
-} from "../scripts/prototype-contract.mjs";
-
-const tempRoot = await mkdtemp(path.join(os.tmpdir(), "yss-prototype-contract-"));
-const projectRoot = path.join(tempRoot, "project");
-const feature = "order-review";
-const prototypeRoot = path.join(projectRoot, "docs/.scratch", feature, "design/prototypes");
-await mkdir(path.join(prototypeRoot, "src"), { recursive: true });
-await mkdir(path.join(projectRoot, "docs/design/tokens"), { recursive: true });
-await writeFile(path.join(prototypeRoot, "package.json"), JSON.stringify({
-  name: "order-review-prototype",
-  private: true,
-  type: "module",
-  scripts: { build: "vite build" },
-  dependencies: { react: "19.2.0", "react-dom": "19.2.0", vite: "6.4.2" }
-}, null, 2));
-await writeFile(path.join(projectRoot, "docs/design/tokens/theme.json"), JSON.stringify({
-  algorithm: "default",
-  token: {
-    colorPrimary: "#3371ff",
-    borderRadius: 6,
-    controlHeight: 32,
-    layoutHeaderHeight: 64
-  }
-}, null, 2));
-
-const before = await validatePrototypeProject({ root: prototypeRoot, targetAntdVersion: "6.6.2" });
-assert(before.errors.some((message) => message.includes("antd")), "RED: starter without antd must fail");
-assert(before.errors.some((message) => message.includes("pnpm-lock.yaml")), "RED: missing pnpm lockfile must fail");
-
-await preparePrototype({ projectRoot, root: prototypeRoot, feature, targetAntdVersion: "6.6.2", pnpmVersion: "10.15.0" });
-const pkg = JSON.parse(await readFile(path.join(prototypeRoot, "package.json"), "utf8"));
-assert.equal(pkg.dependencies.antd, "6.6.2");
-assert.equal(pkg.packageManager, "pnpm@10.15.0");
-assert.match(await readFile(path.join(prototypeRoot, "src/yss-theme.js"), "utf8"), /compactAlgorithm/);
-
-await writeFile(path.join(prototypeRoot, "pnpm-lock.yaml"), "lockfileVersion: '9.0'\n");
-await writeFile(path.join(prototypeRoot, "src/App.jsx"), [
-  'import { ConfigProvider, Button } from "antd";',
-  'import { yssTheme } from "./yss-theme.js";',
-  'export function App() { return <ConfigProvider theme={yssTheme}><Button type="primary">提交</Button></ConfigProvider>; }'
-].join("\n"));
-const after = await validatePrototypeProject({ root: prototypeRoot, targetAntdVersion: "6.6.2" });
-assert.deepEqual(after.errors, []);
-
-const wrongTarget = await validatePrototypeProject({ root: prototypeRoot, targetAntdVersion: "6.6.1" });
-assert(wrongTarget.errors.some((message) => message.includes("精确锁定 antd 6.6.1")), "target 与实际 antd 版本不一致必须失败");
-
-const npmPackage = structuredClone(pkg);
-npmPackage.packageManager = "npm@11.0.0";
-await writeFile(path.join(prototypeRoot, "package.json"), JSON.stringify(npmPackage, null, 2));
-const npmProject = await validatePrototypeProject({ root: prototypeRoot, targetAntdVersion: "6.6.2" });
-assert(npmProject.errors.some((message) => message.includes("packageManager")), "原型包管理器漂移到 npm 必须失败");
-await writeFile(path.join(prototypeRoot, "package.json"), JSON.stringify(pkg, null, 2));
-
-await assert.rejects(
-  preparePrototype({
-    projectRoot,
-    root: path.join(projectRoot, "prototypes", feature),
-    feature,
-    targetAntdVersion: "6.6.2",
-    pnpmVersion: "10.15.0"
-  }),
-  /docs\/.scratch/,
-  "非标准原型目录必须被拒绝"
-);
-
-const validEvidence = {
-  schema_version: 2,
-  feature,
-  prototype_ref: `docs/.scratch/${feature}/design/prototypes/index.html`,
-  prototype_stack: {
-    framework: "react",
-    package_manager: "pnpm",
-    package_manifest_ref: `docs/.scratch/${feature}/design/prototypes/package.json`,
-    lockfile_ref: `docs/.scratch/${feature}/design/prototypes/pnpm-lock.yaml`,
-    source_entry_ref: `docs/.scratch/${feature}/design/prototypes/src/App.jsx`,
-    build_entry_ref: `docs/.scratch/${feature}/design/prototypes/dist/index.html`,
-    build_command: "pnpm build",
-    build_result: "passed",
-    actual_antd_version: "6.6.2"
-  },
-  design_baseline: {
-    design_standard: "ant-design-v6",
-    project_design_ref: "docs/design/design.md",
-    project_token_refs: ["docs/design/tokens/theme.json"],
-    theme_adapter_ref: `docs/.scratch/${feature}/design/prototypes/src/yss-theme.js`,
-    project_override_reviewed: true
-  },
-  visual_semantic_mapping: {
-    runtime_component_library: "ant-design-vue-4.x",
-    runtime_version_source: "implementation-lockfile",
-    components: [{
-      semantic_role: "primary-action",
-      antd_v6_component: "Button",
-      project_token_refs: ["colorPrimary"],
-      yss_or_antdv_target: "YButton",
-      state_mapping: ["default", "hover", "active", "disabled", "loading"],
-      react_only_api_not_copied: true,
-      verification_ref: "verification/button-states.png"
-    }]
-  },
-  antd: { target_antd_version: "6.6.2", queries: { design_md: "verification/antd-design.json", components: [] } },
-  browser_verification: { rendered_nonblank: true, viewports: [], main_flow_result: "passed", failure_permission_or_conflict_result: "passed", console_error_ref: "verification/console.txt" },
-  design_qa: { report_ref: `docs/.scratch/${feature}/verification/design-qa.md`, result: "passed" },
-  accessibility_verification: {
-    contrast_results_ref: "verification/contrast.json",
-    keyboard_navigation_result: "passed",
-    focus_visible_and_order_result: "passed",
-    semantic_label_dialog_result: "passed",
-    zoom_200_result: "passed",
-    reduced_motion_result: "passed",
-    target_size_result: "passed",
-    automated_scan: { tool: "axe", version: "4", result: "passed", ref: "verification/axe.json" }
-  },
-  review: { prototype_review_ref: "design/review.md", result: "approved" },
-  user_confirmation: { confirmation_ref: "design/confirmation.md", result: "approved" },
-  blockers: []
-};
-assert.deepEqual(validatePrototypeEvidence(validEvidence).errors, []);
-
-const missingMapping = structuredClone(validEvidence);
-delete missingMapping.visual_semantic_mapping;
-assert(validatePrototypeEvidence(missingMapping).errors.some((message) => message.includes("visual_semantic_mapping")));
-
-const copiedReactApi = structuredClone(validEvidence);
-copiedReactApi.visual_semantic_mapping.components[0].react_only_api_not_copied = false;
-assert(validatePrototypeEvidence(copiedReactApi).errors.some((message) => message.includes("React-only")));
-
-const inaccessible = structuredClone(validEvidence);
-inaccessible.accessibility_verification.contrast_results_ref = "";
-assert(validatePrototypeEvidence(inaccessible).errors.some((message) => message.includes("contrast_results_ref")));
-
-const wrongQaRoot = structuredClone(validEvidence);
-wrongQaRoot.design_qa.report_ref = "docs/design/design-qa.md";
-assert(validatePrototypeEvidence(wrongQaRoot).errors.some((message) => message.includes("design_qa.report_ref")));
-
-const versionMismatch = structuredClone(validEvidence);
-versionMismatch.antd.target_antd_version = "6.6.1";
-assert(validatePrototypeEvidence(versionMismatch).errors.some((message) => message.includes("target_antd_version")));
-
-const unresolvedBlocker = structuredClone(validEvidence);
-unresolvedBlocker.blockers = ["缺少权限失败态"];
-assert(validatePrototypeEvidence(unresolvedBlocker).errors.some((message) => message.includes("blockers")));
-
-process.stdout.write("YSS prototype contract scenarios passed\n");

package/template/.hermes/skills/yss-repository/SKILL.md

@@ -1,78 +0,0 @@
----
-name: yss-repository
-description: Use when generating or refactoring YSS persistence models, BaseRepository/MyBatis repositories, MapStruct convertors, Domain Gateway implementations, or metadata/DDL-backed queries.
----
-
-# yss-repository
-
-这是一个偏代码生成和结构补全的 skill，适合在已有工程里补 Repository 层，不适合替代完整脚手架。
-
-## 何时使用
-
-- 用户要生成 `PO / Repository / Convertor / GatewayImpl`。
-- 用户已有 Domain 模型，缺基础设施持久层落地。
-- 用户要基于表结构、DDL、metadata 补齐持久层代码。
-
-## 不适用
-
-- 只做 Controller 时，优先 `yss-web-controller`。
-- 只做领域建模时，优先 `yss-domain`。
-- 从零建多模块工程时，优先 `yss-ddd-scaffold-generator`。
-
-## 工作方式
-
-1. 先确认输入来源：领域模型、metadata、数据库表、DDL。
-2. 确认持久化 Profile 为 `mybatis-plus` 与 `PO <-> Domain Model`；`Entity + BaseRepository + DTO/VO GatewayImpl` 等旧架构对新脚手架为 `unsupported`。
-3. 如果 metadata 不完整，先补齐 metadata、数据库表结构或 DDL 输入。
-4. 涉及 POJO 字段、getter/setter、constructor、builder 或日志时，必须加载并遵守 `lombok`。
-5. 涉及持久化模型与 Domain/Application Result 转换时，必须加载并遵守 `mapstruct`；Infrastructure 不生成 Web VO/CMD 转换。
-6. 生成代码时严格保持 Domain 与 Infrastructure 分层边界。
-7. 默认先生成基础 CRUD 骨架，把复杂查询留给手工实现。
-
-## 产物范围
-
-- `domain/{segment}/gateway/*Gateway.java`
-- `repository/entity/*PO.java`
-- `repository/*Repository.java`
-- `repository/convertor/*Convertor.java`
-- `repository/gateway/impl/*GatewayImpl.java`
-- `query/adapter/*QueryAdapter.java`（实现 Application Query Port）
-
-## 约束
-
-- Domain 不依赖 Infrastructure。
-- Gateway 定义在 Domain，实现放在 Infrastructure。
-- Domain Gateway 只交换 Domain Model、领域值和标识；分页、列表和读模型走 Application Query Port，禁止返回 Web VO 或把 `PageQuery` 带入 Domain。
-- PO / Domain Model 等 POJO 样板代码优先使用 Lombok；不要成片手写 getter/setter、constructor、builder 或 logger。
-- Convertor 必须优先使用 `@Mapper(componentModel = "spring")` 和构造器注入；禁止静态 `INSTANCE`、`BeanUtils.copyProperties`、反射式通用拷贝和重复手写字段赋值，除非实现合同记录受控例外、测试和 review 证据。
-- MapStruct 与 Lombok 同时使用时，必须确认注解处理器顺序和 `lombok-mapstruct-binding` 配置；构建命令使用项目根目录 `./mvnw ...`。
-- 逻辑删除、审计字段、主键策略要显式处理，不要隐式略过。
-- 事务放在批准的 Application 用例边界；检测到旧 GatewayImpl 事务布局时返回 `unsupported`，不在 scaffold 链路内迁移。
-
-## 质量门禁
-
-- 生成代码必须可编译。
-- 命名、包路径、注解要与工程现有规范一致。
-- Convertor 必须有 MapStruct 接口 / 抽象类、生成实现可编译，必要时补 mapper 单测或覆盖核心字段转换的行为测试。
-- POJO 使用 Lombok 时不得引入 `@Data` 造成实体 equals / toString 风险；有关系字段、敏感字段或懒加载字段时按 `lombok` skill 排除。
-- 遇到无法自动判断的字段或规则时，写 TODO 或向用户说明，不要假装已确认。
-
-## 协同顺序
-
-- metadata / DDL 输入准备：确认输入完整
-- 领域建模：`yss-domain`
-- 用例编排：`yss-application`
-- POJO 样板代码：`lombok`
-- 对象转换：`mapstruct`
-- Web 补齐：`yss-web-controller`
-
-## 分层开发规范
-
-实现 PO / Repository / GatewayImpl 前，必须加载 `references/infrastructure-layer-guide.md`：其中定义持久化对象、Repository、Convertor 与 Gateway 实现的结构与示例。
-
-## 阶段 7 合同
-
-- 前置条件：数据架构、领域元数据、实现仓库和批准后的 `Slice Implementation Contract` 均可用；否则不执行本 skill，由 Router 返回 `blocked`。
-- PO/Repository/Convertor 骨架可使用 `controlled-generation`；复杂过滤、分页语义、并发、事务和迁移行为必须拆为 `behavior-tdd`。
-- 写入仅限合同 `allowed_write_paths`，证据必须包含实际 PO、Repository、Convertor、GatewayImpl、测试和 `./mvnw ...` 结果。
-- 按统一 `YSS Skill Execution Result` 返回 `seam_deferred/deviations/new_impacts`；发现数据模型、DDL、SQL、索引或 API schema 变化时暂停并重路由。

package/template/.hermes/skills/yss-repository/agents/openai.yaml

@@ -1,5 +0,0 @@
-version: 1
-interface:
-  display_name: "YSS Repository"
-  short_description: "Repository、Convertor 与 gateway 实现规范"
-  default_prompt: "Use $yss-repository to generate or refactor YSS repository, convertor, and gateway implementation code."

package/template/.hermes/skills/yss-repository/references/infrastructure-layer-guide.md

@@ -1,107 +0,0 @@
-# YSS Infrastructure Target Profile 指南
-
-本指南只定义 `target-domain-model + mybatis-plus`。历史 `Entity + DTO/VO Gateway` 为 `unsupported`，不存在旧架构 Profile。
-
-## 1. 职责
-
-- 实现 Domain Gateway，负责 Aggregate 持久化。
-- 实现 Application Query Port，负责分页、列表和读模型。
-- 定义 PO、MyBatis-Plus Repository/Mapper、XML 和数据源适配。
-- 通过 Spring MapStruct Bean 完成 `PO <-> Domain Model`、`PO -> Application Result`。
-
-Infrastructure 不拥有业务事务边界，不向 Application/Web 暴露 PO，也不直接生成 HTTP VO。
-
-## 2. 包结构
-
-```text
-{base_package}.infrastructure
-├── persistence
-│   ├── po
-│   ├── repository
-│   ├── convertor
-│   └── gateway
-└── query
-    ├── adapter
-    └── convertor
-```
-
-新脚手架固定使用 `{base_package}.infrastructure`。已有 `{base_package}.repository` 工程不由 scaffold 改写；需要现代化时单独立项。
-
-## 3. Domain Gateway 实现
-
-```java
-@Repository
-@RequiredArgsConstructor
-public class QualityTemplateGatewayImpl implements QualityTemplateGateway {
-    private final QualityTemplateRepository repository;
-    private final QualityTemplatePersistenceConvertor convertor;
-
-    @Override
-    public Optional<QualityTemplate> findById(QualityTemplateId id) {
-        return Optional.ofNullable(repository.selectById(id.value()))
-                .map(convertor::toDomain);
-    }
-
-    @Override
-    public void save(QualityTemplate aggregate) {
-        repository.insertOrUpdate(convertor.toPO(aggregate));
-    }
-}
-```
-
-GatewayImpl 不接收 Web Cmd/Query，不返回 VO/PageResult，不声明新的业务事务。
-
-## 4. Query Port 实现
-
-分页/列表属于 Application Query Port：
-
-```java
-@Repository
-@RequiredArgsConstructor
-public class QualityTemplateQueryAdapter implements QualityTemplateQueryPort {
-    private final QualityTemplateRepository repository;
-    private final QualityTemplateQueryConvertor convertor;
-
-    @Override
-    public PageResult<QualityTemplateResult> page(QualityTemplatePageQuery query) {
-        // orderBy/groupBy 必须先映射到批准列白名单，再构造 MyBatis 条件。
-        return convertor.toResultPage(repository.selectPage(...));
-    }
-}
-```
-
-`PageQuery` 可以在 Web/Application/Infrastructure 协作链使用，但不得进入 Domain。`orderBy` / `groupBy` 禁止直接拼接 SQL。
-
-## 5. PO 与 Repository
-
-- Target Profile 使用 `*PO`；旧式 `*Entity` 布局为 `unsupported`。
-- PO 默认使用最小 Lombok 注解，不无条件使用 `@Data`。
-- 当前实现继承项目既有 `BasePlusRepository<PO>`；普通 MyBatis 为 `unsupported`。
-- Mapper XML 位于项目既有扫描路径；扫描包和 XML 路径必须由集成测试证明。
-
-## 6. MapStruct
-
-```java
-@Mapper(componentModel = "spring")
-public interface QualityTemplatePersistenceConvertor {
-    QualityTemplate toDomain(QualityTemplatePO source);
-    QualityTemplatePO toPO(QualityTemplate source);
-}
-```
-
-- 禁止 `INSTANCE = Mappers.getMapper(...)`。
-- Convertor 使用构造器注入。
-- 父 POM 必须配置 `mapstruct-processor`、Lombok 和 `lombok-mapstruct-binding`。
-- 验证必须编译生成实现，不能只检查接口文本。
-
-## 7. 验证
-
-- Domain Gateway：保存后可通过 Gateway seam 重新加载等价 Aggregate。
-- Query Port：分页、total、排序白名单和空结果。
-- Mapper/Repository：实际 MyBatis-Plus/H2 或批准数据库 fixture。
-- Architecture：Infrastructure 可以依赖 Application/Domain；反向依赖必须失败。
-- 使用项目根 `./mvnw test/package` 留证。
-
-## 8. 旧架构边界
-
-检测到 Repository 直接接收 client Query、返回 VO、Convertor 做 `PO -> VO` 或使用旧式 Entity 布局时，返回 `unsupported`，不得由新 scaffold 自动改写。旧项目继续按原工程维护；现代化改造必须单独立项。

package/template/.hermes/skills/yss-resilience4j/SKILL.md

@@ -1,46 +0,0 @@
----
-name: yss-resilience4j
-description: Use when 用于 YSS Resilience4j starter、网关熔断、限流降级、GlobalCircuitExceptionAdvice、GatewayConfiguration 和断路器配置排障。
----
-
-# yss-resilience4j
-
-Use this skill for YSS Resilience4j 组件. Keep implementation grounded in the local project and resolvable YSS backend component source.
-
-中文说明：本技能用于 YSS Resilience4j 组件。执行时优先读取源码索引，避免凭记忆猜类名、配置项或接入方式。
-
-## Source Index First
-
-- Backend source location is environment-specific; resolve it with `yss-source-index/references/source-location.md`.
-- Generated index: `references/source-index.md`
-- Component path hints: `yss-microservice-components/yss-component-resilience4j-starter`
-
-Read `references/source-index.md` as a path-hint index whenever the task depends on exact modules, annotations, auto configuration, properties, controllers, clients, repositories, DTOs, handlers, or troubleshooting.
-
-## Workflow
-
-1. Read `references/source-index.md`, then read component `readme.md`.
-2. Identify whether the task is gateway circuit breaker configuration, fallback response, global circuit exception handling, or resilience troubleshooting.
-3. Inspect `GatewayConfiguration` for route/filter wiring and `GlobalCircuitExceptionAdvice` for exception response behavior.
-4. Tune thresholds/timeouts in configuration rather than hardcoding resilience behavior in business handlers.
-5. Keep fallback responses consistent with gateway/API response contracts.
-
-## Capability Split
-
-- Gateway resilience wiring: `GatewayConfiguration`.
-- Circuit exception mapping: `GlobalCircuitExceptionAdvice`.
-- Operational guidance: README "轻量微服务断路器".
-
-## Checklist
-
-- Required dependency or starter module is present.
-- Circuit breaker names and route IDs match gateway configuration.
-- Fallback status/body are acceptable for frontend/API consumers.
-- Timeout, slow-call, and failure thresholds match service SLOs.
-- Logs/metrics make open/half-open/recovered states diagnosable.
-
-## Do Not
-
-- Do not invent class names or configuration keys without checking the source index.
-- Do not replace component extension points with business-local framework code.
-- Do not broaden the task into unrelated YSS components unless the user asks.

package/template/.hermes/skills/yss-resilience4j/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "yss-resilience4j"
-  short_description: "YSS component skill for yss-resilience4j"
-  default_prompt: "Use yss-resilience4j for this YSS backend component task."

package/template/.hermes/skills/yss-resilience4j/references/source-index.md

@@ -1,33 +0,0 @@
-# yss-resilience4j Source Index
-
-Generated: 2026-08-17T12:03:37.436Z
-Source commit: `38b556a5081e6c66c0c538cbc1ef839b19996ed3`
-Source worktree: `dirty`
-Indexed source root: resolved at refresh time; set `YSS_SOURCE_ROOT` to reproduce or refresh.
-
-This file is generated by `yss-source-index/scripts/refresh-yss-skill-index.mjs`. Do not hand-edit generated sections.
-
-Paths below are source path hints captured at refresh time. If they do not exist in the current workspace, locate sources using `YSS_SOURCE_ROOT`, CodeGraph, package/class names, Maven artifact names, or repository search before assuming the source is unavailable.
-
-## Component Path Hints
-
-- `yss-microservice-components/yss-component-resilience4j-starter` (existed when indexed)
-
-## Documentation Files
-
-- `yss-microservice-components/yss-component-resilience4j-starter/readme.md`
-
-## Maven Modules
-
-- `yss-microservice-components/yss-component-resilience4j-starter`
-
-## Key Java Entry Points
-
-- `yss-microservice-components/yss-component-resilience4j-starter/src/main/java/com/yss/cloud/breaker/config/GatewayConfiguration.java`
-- `yss-microservice-components/yss-component-resilience4j-starter/src/main/java/com/yss/cloud/breaker/exception/GlobalCircuitExceptionAdvice.java`
-
-## Recommended Next Reads
-
-- Start with the documentation files above when learning component usage.
-- Search the key Java entry points for annotations, auto configuration, properties, aspects, interceptors, handlers, and result objects before changing application code.
-- Prefer existing component extension points over rewriting framework logic in business modules.

package/template/.hermes/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/.hermes/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/.hermes/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.
-
-中文说明：组件类技能不要凭记忆猜类名，先用源码索引找真实位置。