create-yss-spec 3.0.0 → 3.1.0

package/template/.hermes/skills/yss-research/scripts/validate-research-package.mjs

@@ -1,128 +0,0 @@
-#!/usr/bin/env node
-import { readFileSync } from "node:fs";
-import path from "node:path";
-
-const PROFILE_VALUES = ["technical-evidence", "strategy-evidence"];
-const SOURCE_LEVELS = ["primary", "direct-experience", "near-primary", "secondary", "lead-only"];
-const CLAIM_KINDS = ["technical-fact", "user-problem", "business-constraint", "domain-boundary", "business-rule", "mvp", "non-goal", "success-criterion", "stage-decision-basis", "background"];
-const STRATEGY_DECISION_KINDS = new Set(["user-problem", "business-constraint", "domain-boundary", "business-rule", "mvp", "non-goal", "success-criterion", "stage-decision-basis"]);
-
-function fail(message) { throw new TypeError(message); }
-function requireString(value, label) { if (typeof value !== "string" || !value.trim()) fail(`${label} must be a non-empty string`); }
-function requireArray(value, label, nonEmpty = false) { if (!Array.isArray(value) || (nonEmpty && value.length === 0)) fail(`${label} must be ${nonEmpty ? "a non-empty" : "an"} array`); }
-function requireChoice(value, choices, label) { if (!choices.includes(value)) fail(`${label} must be one of: ${choices.join(", ")}`); }
-
-function indexed(items, label) {
-  const result = new Map();
-  items.forEach((item, index) => {
-    requireString(item?.id, `${label}[${index}].id`);
-    if (result.has(item.id)) fail(`${label} contains duplicate id: ${item.id}`);
-    result.set(item.id, item);
-  });
-  return result;
-}
-
-function readEvidence(file) {
-  try {
-    const value = JSON.parse(readFileSync(file, "utf8"));
-    if (!value || typeof value !== "object" || Array.isArray(value)) fail("evidence root must be an object");
-    return value;
-  } catch (error) {
-    if (error instanceof TypeError && error.message === "evidence root must be an object") throw error;
-    fail(`${path.basename(file)} must use JSON-compatible YAML 1.2 syntax: ${error.message}`);
-  }
-}
-
-function validate(briefFile, evidenceFile) {
-  if (!briefFile || !evidenceFile) fail("usage: validate-research-package.mjs <brief.md> <evidence.yaml>");
-  const briefPath = path.resolve(briefFile);
-  const evidencePath = path.resolve(evidenceFile);
-  if (path.dirname(briefPath) !== path.dirname(evidencePath)) fail("brief and evidence files must be adjacent");
-  if (!briefPath.endsWith("-research-brief.md") || !evidencePath.endsWith("-evidence.yaml")) fail("expected <slug>-research-brief.md and <slug>-evidence.yaml");
-  const briefSlug = path.basename(briefPath, "-research-brief.md");
-  if (!briefSlug || briefSlug !== path.basename(evidencePath, "-evidence.yaml")) fail("brief and evidence files must use the same non-empty slug");
-
-  const brief = readFileSync(briefPath, "utf8");
-  ["Research Scope", "Executive Read", "Findings", "Counter-Signals", "Source Map", "Decision Handoff", "Evidence Limitations"].forEach((heading) => {
-    if (!brief.includes(`## ${heading}`)) fail(`brief is missing heading: ## ${heading}`);
-  });
-
-  const data = readEvidence(evidencePath);
-  if (data.schema_version !== 1) fail("schema_version must be 1");
-  requireChoice(data.profile, PROFILE_VALUES, "profile");
-  if (data.mode !== "evidence-audited") fail("mode must be evidence-audited");
-  ["topic", "audience", "time_horizon"].forEach((field) => requireString(data.scope?.[field], `scope.${field}`));
-  ["research_questions", "inclusion_criteria", "exclusion_criteria"].forEach((field) => requireArray(data.scope?.[field], `scope.${field}`, true));
-  if (data.ownership?.research_owner !== "yss-research") fail("ownership.research_owner must be yss-research");
-  requireString(data.ownership?.downstream_owner, "ownership.downstream_owner");
-  if (data.ownership.decision_ref !== null && (typeof data.ownership.decision_ref !== "string" || !data.ownership.decision_ref.trim())) fail("ownership.decision_ref must be null or a non-empty string");
-
-  requireArray(data.search_log, "search_log", true);
-  const searches = indexed(data.search_log, "search_log");
-  data.search_log.forEach((entry, index) => {
-    ["channel", "query_or_corpus", "searched_at"].forEach((field) => requireString(entry[field], `search_log[${index}].${field}`));
-    requireChoice(entry.result, ["results-found", "none-found", "access-failed", "excluded"], `search_log[${index}].result`);
-  });
-
-  requireArray(data.evidence_items, "evidence_items", true);
-  const evidence = indexed(data.evidence_items, "evidence_items");
-  data.evidence_items.forEach((item, index) => {
-    requireChoice(item.source_level, SOURCE_LEVELS, `evidence_items[${index}].source_level`);
-    requireChoice(item.visibility, ["public", "internal"], `evidence_items[${index}].visibility`);
-    requireChoice(item.stance, ["support", "counter"], `evidence_items[${index}].stance`);
-    ["source_class", "source_ref", "locator", "observed_at", "observation"].forEach((field) => requireString(item[field], `evidence_items[${index}].${field}`));
-    requireArray(item.limitations, `evidence_items[${index}].limitations`);
-  });
-
-  requireArray(data.claims, "claims", true);
-  const claims = indexed(data.claims, "claims");
-  data.claims.forEach((claim, index) => {
-    requireChoice(claim.claim_kind, CLAIM_KINDS, `claims[${index}].claim_kind`);
-    requireString(claim.statement, `claims[${index}].statement`);
-    if (typeof claim.decision_bearing !== "boolean") fail(`claims[${index}].decision_bearing must be boolean`);
-    requireArray(claim.evidence_refs, `claims[${index}].evidence_refs`, true);
-    requireArray(claim.counter_signal_refs, `claims[${index}].counter_signal_refs`, true);
-    requireChoice(claim.audit_status, ["supported", "partially-supported", "unsupported", "not-audited"], `claims[${index}].audit_status`);
-    requireChoice(claim.confidence, ["low", "medium", "high"], `claims[${index}].confidence`);
-    requireChoice(claim.disposition, ["publish", "qualify", "needs-deeper-research"], `claims[${index}].disposition`);
-
-    const supporting = claim.evidence_refs.map((ref) => {
-      if (!evidence.has(ref)) fail(`${claim.id} has unresolved evidence ref: ${ref}`);
-      const item = evidence.get(ref);
-      if (item.stance !== "support") fail(`${claim.id} support ref is not marked support: ${ref}`);
-      if (item.source_level === "lead-only") fail(`${claim.id} uses lead-only evidence as support: ${ref}`);
-      return item;
-    });
-    claim.counter_signal_refs.forEach((ref) => {
-      if (!evidence.has(ref) && !searches.has(ref)) fail(`${claim.id} has unresolved counter-signal ref: ${ref}`);
-      if (evidence.has(ref) && evidence.get(ref).stance !== "counter") fail(`${claim.id} counter-signal evidence is not marked counter: ${ref}`);
-      if (searches.has(ref) && searches.get(ref).result !== "none-found") fail(`${claim.id} counter-signal search must have result none-found: ${ref}`);
-    });
-    if (data.profile === "technical-evidence" && claim.decision_bearing && !supporting.some((item) => item.source_level === "primary")) fail(`${claim.id} is a decision-bearing technical claim without primary evidence`);
-    if (data.profile === "strategy-evidence" && STRATEGY_DECISION_KINDS.has(claim.claim_kind) && claim.decision_bearing !== true) fail(`${claim.id} strategy claim kind must be decision-bearing: ${claim.claim_kind}`);
-    if (claim.audit_status === "partially-supported" && claim.disposition !== "qualify") fail(`${claim.id} is partially supported and must use qualify`);
-    if (claim.audit_status === "unsupported" && claim.disposition !== "needs-deeper-research") fail(`${claim.id} is unsupported and must use needs-deeper-research`);
-    if (claim.decision_bearing && claim.audit_status === "unsupported") fail(`${claim.id} is decision-bearing and cannot remain unsupported`);
-    if (!brief.includes(claim.id)) fail(`brief does not reference claim: ${claim.id}`);
-  });
-
-  requireArray(data.source_gaps, "source_gaps");
-  if (data.audit_summary?.status !== "complete") fail("audit_summary.status must be complete");
-  requireArray(data.audit_summary.audited_claim_ids, "audit_summary.audited_claim_ids", true);
-  requireArray(data.audit_summary.notes, "audit_summary.notes");
-  const audited = new Set(data.audit_summary.audited_claim_ids);
-  audited.forEach((id) => { if (!claims.has(id)) fail(`audit_summary has unknown claim: ${id}`); });
-  claims.forEach((claim, id) => {
-    if (claim.decision_bearing && !audited.has(id)) fail(`audit_summary is missing decision-bearing claim: ${id}`);
-    if (claim.decision_bearing && claim.audit_status === "not-audited") fail(`${id} remains not-audited`);
-  });
-  return { claims: claims.size, evidence: evidence.size, searches: searches.size, profile: data.profile };
-}
-
-try {
-  const result = validate(process.argv[2], process.argv[3]);
-  process.stdout.write(`YSS research package valid (${result.profile}, ${result.claims} claims, ${result.evidence} evidence items, ${result.searches} searches)\n`);
-} catch (error) {
-  process.stderr.write(`YSS research package invalid: ${error.message}\n`);
-  process.exitCode = 1;
-}

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

@@ -1,81 +0,0 @@
-#!/usr/bin/env node
-import { mkdtempSync, readFileSync, rmSync, writeFileSync } from "node:fs";
-import { tmpdir } from "node:os";
-import path from "node:path";
-import { spawnSync } from "node:child_process";
-import { fileURLToPath } from "node:url";
-
-const root = path.resolve(path.dirname(fileURLToPath(import.meta.url)), "..");
-const validator = path.join(root, "scripts/validate-research-package.mjs");
-const template = JSON.parse(readFileSync(path.join(root, "assets/evidence-template.yaml"), "utf8"));
-const directory = mkdtempSync(path.join(tmpdir(), "yss-research-"));
-const brief = path.join(directory, "sample-research-brief.md");
-const evidence = path.join(directory, "sample-evidence.yaml");
-const headings = ["Research Scope", "Executive Read", "Findings", "Counter-Signals", "Source Map", "Decision Handoff", "Evidence Limitations"];
-
-function run(payload, status, expected) {
-  writeFileSync(brief, `${headings.map((heading) => `## ${heading}`).join("\n\n")}\n\n${payload.claims.map((claim) => claim.id).join(" ")}\n`);
-  writeFileSync(evidence, `${JSON.stringify(payload, null, 2)}\n`);
-  const result = spawnSync(process.execPath, [validator, brief, evidence], { encoding: "utf8" });
-  if (result.status !== status || !`${result.stdout}${result.stderr}`.includes(expected)) throw new Error(`expected ${status}/${expected}, got ${result.status}: ${result.stdout}${result.stderr}`);
-}
-
-try {
-  template.scope.topic = "Example strategy question";
-  template.scope.audience = "Product team";
-  template.scope.time_horizon = "Last 12 months";
-  template.scope.research_questions = ["Which problem should the domain address?"];
-  template.scope.inclusion_criteria = ["Direct experience in scope"];
-  template.scope.exclusion_criteria = ["Untraceable reposts"];
-  template.ownership.downstream_owner = "yss-stage-decision";
-  template.search_log[0].channel = "Support records";
-  template.search_log[0].query_or_corpus = "failed approval workflow";
-  template.search_log[0].searched_at = "2026-09-03";
-  template.search_log[1].channel = "Support records";
-  template.search_log[1].query_or_corpus = "successful approval workflow";
-  template.search_log[1].searched_at = "2026-09-03";
-  template.evidence_items[0].source_class = "support";
-  template.evidence_items[0].source_ref = "support-case-001";
-  template.evidence_items[0].locator = "event-3";
-  template.evidence_items[0].observed_at = "2026-09-03";
-  template.evidence_items[0].evidence_date = "2026-08-30";
-  template.evidence_items[0].observation = "The approval stopped when the owner was missing.";
-  template.evidence_items[0].limitations = ["Single support case"];
-  template.claims[0].statement = "A missing owner can block the approval workflow.";
-  run(template, 0, "YSS research package valid");
-
-  const falseStrategyBackground = structuredClone(template);
-  falseStrategyBackground.claims[0].decision_bearing = false;
-  run(falseStrategyBackground, 1, "strategy claim kind must be decision-bearing");
-
-  const unsupported = structuredClone(template);
-  unsupported.claims[0].audit_status = "unsupported";
-  unsupported.claims[0].disposition = "publish";
-  run(unsupported, 1, "must use needs-deeper-research");
-
-  const unsupportedDecision = structuredClone(template);
-  unsupportedDecision.claims[0].audit_status = "unsupported";
-  unsupportedDecision.claims[0].disposition = "needs-deeper-research";
-  run(unsupportedDecision, 1, "decision-bearing and cannot remain unsupported");
-
-  const falseCounter = structuredClone(template);
-  falseCounter.claims[0].counter_signal_refs = ["search-001"];
-  run(falseCounter, 1, "counter-signal search must have result none-found");
-
-  const technicalWithoutPrimary = structuredClone(template);
-  technicalWithoutPrimary.profile = "technical-evidence";
-  technicalWithoutPrimary.claims[0].claim_kind = "technical-fact";
-  run(technicalWithoutPrimary, 1, "technical claim without primary evidence");
-
-  const leadOnly = structuredClone(template);
-  leadOnly.evidence_items[0].source_level = "lead-only";
-  run(leadOnly, 1, "uses lead-only evidence as support");
-
-  const unaudited = structuredClone(template);
-  unaudited.audit_summary.audited_claim_ids = [];
-  run(unaudited, 1, "must be a non-empty array");
-
-  process.stdout.write("YSS research scenarios passed (8)\n");
-} finally {
-  rmSync(directory, { recursive: true, force: true });
-}

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