create-yss-spec 2.2.10 → 3.0.1

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

@@ -1,35 +0,0 @@
-# yss-security-algorithm 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-security-algorithm` (existed when indexed)
-
-## Documentation Files
-
-- No component documentation files found.
-
-## Maven Modules
-
-- `yss-microservice-components/yss-component-security-algorithm`
-
-## Key Java Entry Points
-
-- `yss-microservice-components/yss-component-security-algorithm/src/main/java/com/yss/cloud/CryptoType.java`
-- `yss-microservice-components/yss-component-security-algorithm/src/main/java/com/yss/cloud/config/DefaultJwtConfiguration.java`
-- `yss-microservice-components/yss-component-security-algorithm/src/main/java/com/yss/cloud/jose/KeyGeneratorUtils.java`
-- `yss-microservice-components/yss-component-security-algorithm/src/main/java/com/yss/cloud/util/SecurityCryptoUtil.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-source-index/SKILL.md

@@ -1,63 +0,0 @@
----
-name: yss-source-index
-description: Use when YSS backend component source or frontend UI documentation changes and skill source indexes need refreshing.
----
-
-# yss-source-index
-
-Use this maintenance skill to keep YSS skills grounded in current source and documentation.
-
-中文说明：这个技能用于维护 YSS skills 的“源码索引”。后端组件库或前端文档入口变化后，运行脚本刷新引用文件。
-
-## Source Location Policy
-
-- Backend component source is environment-specific. Use `references/source-location.md` before trusting any generated path.
-- Preferred explicit setting: `YSS_SOURCE_ROOT=/absolute/path/to/yss-cloud-microservice`.
-- Frontend YSS UI components: `http://192.168.164.27:3200/components`
-- Frontend YSS UI hooks: `http://192.168.164.27:3200/hooks`
-- Frontend YSS UI skill docs: `http://192.168.164.27:3200/skills`
-
-## Refresh Workflow
-
-Run:
-
-```bash
-export YSS_SKILLS_ROOT="/path/to/.agents/skills"
-export YSS_SOURCE_ROOT="/path/to/yss-cloud-microservice"
-node "$YSS_SKILLS_ROOT/yss-source-index/scripts/refresh-yss-skill-index.mjs"
-```
-
-Backend-only refreshes may set `YSS_REFRESH_FRONTEND=false` to avoid unrelated frontend timestamp churn.
-
-The script updates `references/source-index.md` for backend component skills and `references/frontend-docs.md` for frontend YSS UI skills. Read `references/source-map-config.md` for the full skill-to-source mapping.
-
-中文说明：脚本不会复制大段源码，只会生成可追踪的文档路径、模块路径和关键 Java 入口类，方便 Agent 后续精准读取。
-
-If `YSS_SOURCE_ROOT` is omitted, the script tries to find a repository containing `yss-microservice-components` from the current workspace and common local project folders. If it cannot find one, set `YSS_SOURCE_ROOT` explicitly.
-
-## Output Contract
-
-Generated source indexes should contain:
-
-- source root and generated timestamp
-- exact source Git commit and worktree state
-- component directories and documentation files
-- Maven modules
-- key Java classes matched by names such as annotations, auto configurations, properties, aspects, interceptors, handlers, repositories, DTOs, and result objects
-- recommended next reads for Agent when performing implementation or troubleshooting
-
-Do not paste full component source into `SKILL.md`. Keep `SKILL.md` short and let specialists read generated indexes or targeted assets only when needed.
-
-## Freshness Gate
-
-Before exact class/config/security guidance, compare the index `Source commit` with `git -C "$YSS_SOURCE_ROOT" rev-parse HEAD`. A mismatch or `dirty` indexed state means `stale`: refresh the index or return `blocked`; do not silently rely on the old snapshot. Historical path hints may still be used only to locate current source.
-
-中文说明：`SKILL.md` 保持短小，细节放到 `references/`，这是为了降低每次触发技能时的上下文成本。
-
-## After Refresh
-
-Validate the migrated Node helper with:
-
-```bash
-node --test "$YSS_SKILLS_ROOT/yss-source-index/scripts/refresh-yss-skill-index.test.mjs"
-```

package/template/.hermes/skills/yss-source-index/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "YSS Source Index"
-  short_description: "Refresh YSS skill source indexes"
-  default_prompt: "Refresh YSS skill indexes from yss-cloud-microservice and YSS UI docs."

package/template/.hermes/skills/yss-source-index/scripts/refresh-yss-skill-index.mjs

@@ -1,24 +0,0 @@
-#!/usr/bin/env node
-import { execFileSync } from "node:child_process";
-import { access, mkdir, readdir, writeFile } from "node:fs/promises";
-import os from "node:os";
-import path from "node:path";
-import { fileURLToPath } from "node:url";
-
-const BACKEND = {"yss-cache":["yss-microservice-components/yss-component-cache-parent"],"yss-mybatis":["yss-microservice-components/yss-component-persistence"],"yss-dto":["yss-microservice-components/yss-component-dto"],"yss-audit-log":["yss-microservice-components/yss-component-audit-log"],"yss-excel-mvc":["yss-microservice-components/yss-component-excel-mvc","yss-microservice-components/yss-component-excel-starter"],"yss-distributed-id":["yss-microservice-components/yss-component-distributed-id","yss-microservice-components/yss-component-leaf"],"yss-resilience4j":["yss-microservice-components/yss-component-resilience4j-starter"],"yss-validation":["yss-microservice-components/yss-component-validation-engine-parent","yss-microservice-components/yss-component-validation-jsr303"],"yss-security-algorithm":["yss-microservice-components/yss-component-security-algorithm"],"yss-userinfo":["yss-microservice-components/yss-component-userinfo-starter"],"yss-exception":["yss-microservice-components/yss-component-exception"]};
-const FRONTEND={"yss-ui":["components","hooks","skills"],"yss-components":["components"],"yss-hook":["hooks"],"yss-page-module-development":["components","hooks","skills"],"yss-use-table-height":["hooks"],"yss-use-tree-height":["hooks"]};
-const URLS={components:"http://192.168.164.27:3200/components",hooks:"http://192.168.164.27:3200/hooks",skills:"http://192.168.164.27:3200/skills"};
-const KEYS=["Audit","Cache","Clear","Command","Configuration","Controller","DTO","Data","Enable","Excel","Handler","Interceptor","Jdbc","Mapper","Mybatis","Page","Properties","Query","Repository","Request","Response","Result","Update","Aspect","Leaf","Id","Dir","Dic","Dictionary","File","Upload","Log","Message","Mail","Liquibase","Circuit","Breaker","Sql","Tpl","Tag","Task","Flow","Report","Validation","Validator","Security","Crypto","User","Variable","Quality","Search","Similarity","Scheduler","Runner","Duck","Dynamic","Factory","Client","Feign","Gateway","Convertor","Adapter","Advice","Bridge","Route","Uploader","Sftp","Minio","Parser","Express","Rule","Template","Generator","Importer","Engine","Event","Submitter","Executor","Context","Status","Type","State"];
-const DOCS=new Set(["README.md","readme.md","HELP.md","TECHNICAL_DESIGN.md"]);
-const exists=async p=>{try{await access(p);return true}catch{return false}};
-async function walk(root){if(!await exists(root))return[];const out=[];for(const item of await readdir(root,{withFileTypes:true})){const p=path.join(root,item.name);if(item.isDirectory())out.push(...await walk(p));else if(item.isFile())out.push(p)}return out}
-const relative=(root,p)=>{const value=path.relative(root,p);return value&&!value.startsWith("..")?value:p};
-function state(root){try{const run=args=>execFileSync("git",["-C",root,...args],{encoding:"utf8",stdio:["ignore","pipe","ignore"]}).trim();return[run(["rev-parse","HEAD"]),run(["status","--porcelain"])?"dirty":"clean"]}catch{return["unavailable","unknown"]}}
-async function sourceRoot(){if(process.env.YSS_SOURCE_ROOT){const root=path.resolve(process.env.YSS_SOURCE_ROOT);if(await exists(path.join(root,"yss-microservice-components")))return root;throw new Error(`YSS_SOURCE_ROOT must point to the repository root containing \`yss-microservice-components\`: ${root}`)}const home=os.homedir(),candidates=[process.cwd(),...ancestors(process.cwd()),path.join(home,"Documents/yss-project/yss-cloud-microservice"),path.join(home,"Documents/yss-project"),path.join(home,"Projects/yss-cloud-microservice"),path.join(home,"Projects")];for(const base of [path.join(home,"Projects"),path.join(home,"Documents"),path.join(home,"Documents/yss-project")])if(await exists(base))for(const entry of await readdir(base,{withFileTypes:true}))if(entry.isDirectory())candidates.push(path.join(base,entry.name));for(const root of candidates)if(await exists(path.join(root,"yss-microservice-components")))return path.resolve(root);throw new Error("Could not find a YSS source repository containing `yss-microservice-components`. Export YSS_SOURCE_ROOT=/absolute/path/to/yss-cloud-microservice and rerun.")}
-function ancestors(start){const out=[];let current=path.resolve(start);while(path.dirname(current)!==current){current=path.dirname(current);out.push(current)}return out}
-async function files(bases){const out={docs:[],poms:[],java:[]};for(const base of bases)for(const p of await walk(base)){if(DOCS.has(path.basename(p)))out.docs.push(p);else if(path.basename(p)==="pom.xml")out.poms.push(p);else if(p.endsWith(".java")&&p.includes(`${path.sep}src${path.sep}main${path.sep}java${path.sep}`))out.java.push(p)}for(const a of Object.values(out))a.sort();return out}
-export async function refresh({skillsRoot,source,now=new Date().toISOString(),frontend=true}){const [commit,worktree]=state(source);for(const [skill,parts]of Object.entries(BACKEND)){const bases=parts.map(item=>path.join(source,item));const found=await files(bases);const java=found.java.filter(p=>KEYS.some(key=>path.basename(p,".java").includes(key))).slice(0,120);const list=(items,map,empty)=>items.length?items.map(map):[empty];const baseHints=await Promise.all(bases.map(async p=>`- \`${relative(source,p)}\` (${await exists(p)?"existed":"missing"} when indexed)`));const lines=[`# ${skill} Source Index`,``,`Generated: ${now}`,`Source commit: \`${commit}\``,`Source worktree: \`${worktree}\``,`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`,``,...baseHints,``,`## Documentation Files`,``,...list(found.docs,p=>`- \`${relative(source,p)}\``,"- No component documentation files found."),``,`## Maven Modules`,``,...list(found.poms,p=>`- \`${relative(source,path.dirname(p))}\``,"- No Maven modules found."),``,`## Key Java Entry Points`,``,...list(java,p=>`- \`${relative(source,p)}\``,"- No key Java entry points matched the configured name patterns."),``,`## 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.`,``];const target=path.join(skillsRoot,skill,"references","source-index.md");await mkdir(path.dirname(target),{recursive:true});await writeFile(target,lines.join("\n"),"utf8")}
- if(frontend)for(const[skill,keys]of Object.entries(FRONTEND)){if(!await exists(path.join(skillsRoot,skill)))continue;const target=path.join(skillsRoot,skill,"references","frontend-docs.md");await mkdir(path.dirname(target),{recursive:true});await writeFile(target,[`# ${skill} Frontend Documentation`,``,`Generated: ${now}`,``,`Use these YSS UI documentation entry points as authoritative references when local repo examples are insufficient.`,``,...keys.map(key=>`- ${key}: ${URLS[key]}`),``,`When documentation and local code differ, inspect the current project code before editing and prefer established local usage.`,``].join("\n"),"utf8")}
- return{backend:Object.keys(BACKEND).length,frontend:frontend?Object.keys(FRONTEND).length:0}}
-async function main(){try{const script=path.dirname(fileURLToPath(import.meta.url));const result=await refresh({skillsRoot:path.resolve(process.env.YSS_SKILLS_ROOT||path.join(script,"../..")),source:await sourceRoot(),frontend:!["0","false","no"].includes((process.env.YSS_REFRESH_FRONTEND||"true").toLowerCase())});console.log(`Updated ${result.backend} backend indexes and ${result.frontend} frontend doc references.`)}catch(error){console.error(error.message);process.exitCode=1}}
-if(process.argv[1]===fileURLToPath(import.meta.url))await main();

package/template/.hermes/skills/yss-stage-decision/SKILL.md

@@ -1,50 +0,0 @@
----
-name: yss-stage-decision
-description: 编排 Discovery 到 Spec 入口的阶段决策与 DDD 战略设计；当需求、领域边界、统一语言或下游影响尚未稳定时使用。
----
-
-# YSS Stage Decision
-
-`yss-stage-decision` 是由 `yss-product-lifecycle` 调度的上游决策技能空间，负责把需求、产品、商务输入和 DDD 战略设计结果整理成可审查、可版本化、可被下游消费的阶段决策包。它不替代生命周期主控，也不生成产品代码、原型、OpenAPI 或垂直切片 Ticket。
-
-## 适用边界
-
-- 适用于 `project-instance` 的 Discovery → Spec 入口。
-- `template-source` 只维护本技能、Schema、验证器和合成 Fixture，不生成具体产品领域资产。
-- DDD 工作单元只做子域、限界上下文、Context Map、统一语言、关键场景、事件、核心领域概念候选和业务不变量。
-- Entity、Aggregate、Repository、Java 类、数据库表和 OpenAPI Freeze 留给下游工作单元。
-
-## 执行顺序
-
-1. 读取 `yss-project.yaml`、`CONTEXT.md`、既有 Discovery/Spec、ADR 和父 Ticket/checkpoint。
-2. 分离事实、决策、假设、约束和未决项；技术事实走 `research`，市场/竞品事实走 `competitive-intelligence`。
-3. 从业务场景、事件、规则、责任人和失败路径识别子域及限界上下文，不从数据库表或调用链直接反推边界。
-4. 为每个上下文建立本地统一语言；为跨上下文关系记录语义上游/下游、业务决策权、技术传输方向和翻译责任。
-5. 记录核心领域概念候选，不提前锁定 Entity 或 Aggregate。
-6. 生成 `domain_strategy` 和 `stage_decision_package`，绑定版本、digest、证据和下游影响映射。
-7. 运行 Schema、引用、语义一致性和传播验证；发现关键冲突时返回 `blocked`，不得生成 `approved` 包。
-
-## 语义方向规则
-
-`semantic_upstream` 是拥有业务规则、决策语义或权威模型的一方；`semantic_downstream` 是消费、适配或依赖该语义的一方。二者不等于 HTTP、事件或数据库的技术方向。每条 Context Map 关系必须独立记录 `transport_direction` 和 `translation_responsibility`；同一对上下文可以存在多条相反方向的语义边。
-
-## 产物与批准
-
-- DDD 资产是事实源，阶段决策包只通过 `domain_strategy_ref` 引用它们。
-- `stage_decision_package` 必须经过 `draft → ready-for-human → approved`；起草者不得自签。
-- 建议门禁为 `gate.domain-strategy-approved` 和 `gate.stage-decision-package-approved`，实际状态由 `yss-product-lifecycle` 维护；阶段包批准引用必须通过 `scripts/verify-approval-record`，不得用不可读路径或聊天确认替代。
-- 下游只能消费批准且版本当前的包；发现语义冲突返回 `drift` / `new_impacts`，不得静默修改上游。
-
-## 结果合同
-
-返回标准 `Workflow Execution Result`，至少包含 `work_unit`、`workflow_reference`、`result`、`evidence_refs`、`changed_artifacts`、`new_impacts`、`stale_candidates`、`next_route` 和 `blocking_signals`。`blocked` 必须包含冲突、责任人、恢复条件和下一工作单元。
-
-## 禁止事项
-
-- 不把阶段包当作第二套领域事实源。
-- 不按数据库、微服务、菜单或 HTTP 调用方向自动划分上下文。
-- 不把同名术语强行合并为全局概念。
-- 不在战略设计阶段生成 Entity、Aggregate、Repository、生产代码或 API 契约。
-- 不把模板 Fixture 当作具体项目的业务事实。
-
-详细合同、字段和验证规则见 `references/domain-strategy-contract.md`、`references/stage-decision-package-contract.md` 与 `references/validation-rules.md`。机器可读合同分别为 `references/domain-strategy.schema.json` 和 `references/stage-decision-package.schema.json`；对应验证器为 `scripts/validate-domain-strategy.mjs` 与 `scripts/validate-stage-decision-package.mjs`。

package/template/.hermes/skills/yss-stage-decision/references/domain-strategy-contract.md

@@ -1,26 +0,0 @@
-# DDD 战略设计合同
-
-## 顶层结构
-
-机器可读合同使用 `references/domain-strategy.schema.json`。顶层必须包含：
-
-- `schema_version`、`domain_strategy_id`、`domain_version`、`status`；
-- `contexts`、`subdomains`、`relationships`、`scenarios`；
-- `concept_candidates`、`invariants`、`terminology_refs`；
-- `downstream_mapping`、`evidence_refs`、`approval`。
-
-## 上下文
-
-每个上下文声明 `context_id`、职责边界、非职责、子域分类、模型所有者、关键场景和本地词汇引用。`context_id` 是稳定身份，不得使用代码模块、数据库 schema 或菜单路径替代。
-
-## 关系
-
-关系必须声明 `relationship_pattern`、`semantic_upstream`、`semantic_downstream`、`business_authority`、`model_change_impact`、`transport_direction` 和 `translation_responsibility`。语义方向与技术方向可以不同；关系模式只能使用合同中列出的 DDD 模式。
-
-## 核心概念
-
-使用 `domain_concept_candidate` 表达战略阶段的核心概念候选，记录身份特征、生命周期、不变量引用、可能的战术角色和置信度。不得在该合同中把概念直接批准为 Entity 或 Aggregate Root。
-
-## 阶段决策包
-
-阶段包应通过 `domain_strategy_ref` 引用 DDD 合同的当前版本和 digest，并使用 `domain_to_downstream_mapping` 描述领域变化对 Spec、设计、API、数据、Ticket 和测试 seam 的传播。

package/template/.hermes/skills/yss-stage-decision/references/domain-strategy.schema.json

@@ -1,128 +0,0 @@
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://yss.local/schemas/domain-strategy-v1.json",
-  "title": "YSS DDD Strategic Design",
-  "type": "object",
-  "required": ["schema_version", "domain_strategy_id", "domain_version", "status", "contexts", "subdomains", "relationships", "scenarios", "concept_candidates", "invariants", "terminology_refs", "downstream_mapping", "evidence_refs", "approval"],
-  "properties": {
-    "schema_version": {"const": 1},
-    "domain_strategy_id": {"type": "string", "pattern": "^domain-strategy\\.[a-z0-9][a-z0-9-]*$"},
-    "domain_version": {"type": "string", "pattern": "^v[0-9]+$"},
-    "status": {"enum": ["draft", "ready-for-human", "approved", "stale", "blocked"]},
-    "contexts": {"type": "array", "minItems": 1, "items": {"$ref": "#/$defs/context"}},
-    "subdomains": {"type": "array", "minItems": 1, "items": {"$ref": "#/$defs/subdomain"}},
-    "relationships": {"type": "array", "items": {"$ref": "#/$defs/relationship"}},
-    "scenarios": {"type": "array", "minItems": 1, "items": {"$ref": "#/$defs/scenario"}},
-    "concept_candidates": {"type": "array", "items": {"$ref": "#/$defs/concept"}},
-    "invariants": {"type": "array", "items": {"$ref": "#/$defs/invariant"}},
-    "terminology_refs": {"type": "array", "items": {"type": "string", "minLength": 1}},
-    "downstream_mapping": {"type": "array", "items": {"$ref": "#/$defs/mapping"}},
-    "evidence_refs": {"type": "array", "minItems": 1, "items": {"type": "string", "minLength": 1}},
-    "approval": {"$ref": "#/$defs/approval"}
-  },
-  "$defs": {
-    "context": {
-      "type": "object",
-      "required": ["context_id", "name", "responsibilities", "non_responsibilities", "subdomain_type", "owner", "status"],
-      "properties": {
-        "context_id": {"type": "string", "pattern": "^[A-Z][A-Za-z0-9]+$"},
-        "name": {"type": "string", "minLength": 1},
-        "responsibilities": {"type": "array", "minItems": 1, "items": {"type": "string", "minLength": 1}},
-        "non_responsibilities": {"type": "array", "items": {"type": "string", "minLength": 1}},
-        "subdomain_type": {"enum": ["Core Domain", "Supporting Subdomain", "Generic Subdomain"]},
-        "owner": {"type": "string", "minLength": 1},
-        "status": {"enum": ["candidate", "confirmed", "stale"]}
-      }
-    },
-    "subdomain": {
-      "type": "object",
-      "required": ["subdomain_id", "name", "type", "rationale", "evidence_refs"],
-      "properties": {
-        "subdomain_id": {"type": "string", "pattern": "^subdomain\\.[a-z0-9][a-z0-9-]*$"},
-        "name": {"type": "string", "minLength": 1},
-        "type": {"enum": ["Core Domain", "Supporting Subdomain", "Generic Subdomain"]},
-        "rationale": {"type": "string", "minLength": 1},
-        "evidence_refs": {"type": "array", "minItems": 1, "items": {"type": "string", "minLength": 1}}
-      }
-    },
-    "relationship": {
-      "type": "object",
-      "required": ["relationship_id", "from_context", "to_context", "relationship_pattern", "semantic_upstream", "semantic_downstream", "business_authority", "model_change_impact", "transport_direction", "translation_responsibility", "direction_explanation"],
-      "properties": {
-        "relationship_id": {"type": "string", "pattern": "^relationship\\.[a-z0-9][a-z0-9-]*$"},
-        "from_context": {"type": "string", "pattern": "^[A-Z][A-Za-z0-9]+$"},
-        "to_context": {"type": "string", "pattern": "^[A-Z][A-Za-z0-9]+$"},
-        "relationship_pattern": {"enum": ["Partnership", "Customer/Supplier", "Conformist", "Anti-Corruption Layer", "Open Host Service", "Published Language", "Shared Kernel", "Separate Ways"]},
-        "semantic_upstream": {"type": "string", "pattern": "^[A-Z][A-Za-z0-9]+$"},
-        "semantic_downstream": {"type": "string", "pattern": "^[A-Z][A-Za-z0-9]+$"},
-        "business_authority": {"type": "string", "minLength": 1},
-        "model_change_impact": {"type": "string", "minLength": 1},
-        "transport_direction": {"type": "string", "minLength": 1},
-        "translation_responsibility": {"type": "string", "minLength": 1},
-        "direction_explanation": {"type": "string", "minLength": 1}
-      }
-    },
-    "scenario": {
-      "type": "object",
-      "required": ["scenario_id", "actor", "preconditions", "commands", "rules", "events", "failure_results", "responsible_context", "consumers", "status"],
-      "properties": {
-        "scenario_id": {"type": "string", "pattern": "^scenario\\.[a-z0-9][a-z0-9-]*$"},
-        "actor": {"type": "string", "minLength": 1},
-        "preconditions": {"type": "array", "items": {"type": "string"}},
-        "commands": {"type": "array", "minItems": 1, "items": {"type": "string"}},
-        "rules": {"type": "array", "minItems": 1, "items": {"type": "string"}},
-        "events": {"type": "array", "items": {"type": "string"}},
-        "failure_results": {"type": "array", "minItems": 1, "items": {"type": "string"}},
-        "responsible_context": {"type": "string", "pattern": "^[A-Z][A-Za-z0-9]+$"},
-        "consumers": {"type": "array", "items": {"type": "string", "pattern": "^[A-Z][A-Za-z0-9]+$"}},
-        "status": {"enum": ["candidate", "confirmed", "stale"]}
-      }
-    },
-    "concept": {
-      "type": "object",
-      "required": ["concept_id", "name", "context_id", "identity_features", "lifecycle", "confidence", "status"],
-      "properties": {
-        "concept_id": {"type": "string", "pattern": "^domain-concept\\.[a-z0-9][a-z0-9-]*$"},
-        "name": {"type": "string", "minLength": 1},
-        "context_id": {"type": "string", "pattern": "^[A-Z][A-Za-z0-9]+$"},
-        "identity_features": {"type": "array", "minItems": 1, "items": {"type": "string"}},
-        "lifecycle": {"type": "array", "minItems": 1, "items": {"type": "string"}},
-        "invariant_refs": {"type": "array", "items": {"type": "string"}},
-        "possible_tactical_role": {"type": "string"},
-        "confidence": {"enum": ["low", "medium", "high"]},
-        "status": {"enum": ["candidate", "confirmed", "stale"]}
-      }
-    },
-    "invariant": {
-      "type": "object",
-      "required": ["invariant_id", "statement", "responsible_context", "scenario_refs", "verification_method"],
-      "properties": {
-        "invariant_id": {"type": "string", "pattern": "^invariant\\.[a-z0-9][a-z0-9-]*$"},
-        "statement": {"type": "string", "minLength": 1},
-        "responsible_context": {"type": "string", "pattern": "^[A-Z][A-Za-z0-9]+$"},
-        "scenario_refs": {"type": "array", "minItems": 1, "items": {"type": "string"}},
-        "verification_method": {"type": "string", "minLength": 1}
-      }
-    },
-    "mapping": {
-      "type": "object",
-      "required": ["domain_change", "impacts", "propagation", "reapproval_condition"],
-      "properties": {
-        "domain_change": {"type": "string", "minLength": 1},
-        "impacts": {"type": "array", "minItems": 1, "items": {"type": "string"}},
-        "propagation": {"enum": ["direct", "transitive", "stale"]},
-        "reapproval_condition": {"type": "string", "minLength": 1}
-      }
-    },
-    "approval": {
-      "type": "object",
-      "required": ["approval_ref", "approver", "persisted_ref", "current_version"],
-      "properties": {
-        "approval_ref": {"type": "string", "minLength": 1},
-        "approver": {"type": "string", "minLength": 1},
-        "persisted_ref": {"type": "string", "minLength": 1},
-        "current_version": {"type": "string", "pattern": "^v[0-9]+$"}
-      }
-    }
-  }
-}

package/template/.hermes/skills/yss-stage-decision/references/stage-decision-package-contract.md

@@ -1,19 +0,0 @@
-# 阶段决策包合同
-
-`stage_decision_package` 是 Discovery、需求/产品/商务决策与 DDD 战略设计之间的冻结入口。它记录“做什么、为什么做、范围是什么、哪些仍未决”，不复制领域模型事实。
-
-## 必须包含
-
-- 问题陈述、目标用户、MVP、非目标、成功标准和可执行的测试 seam；
-- 已确认决策、假设、约束和未决项；
-- `domain_strategy_ref`：领域战略合同的稳定 ID、版本、digest 和批准状态；
-- UI/API/Data/Backend/Frontend/跨仓/高风险影响面布尔值；
-- 每个下游消费者的传播方式、重新批准条件、证据引用和批准记录。`approval.approval_ref` 必须指向可读取且通过 `scripts/verify-approval-record` 的 `gate.stage-decision-package-approved` 会签记录；`approval.approver` 必须与记录中的 `role_id` 一致。
-
-## 未决项规则
-
-`blocker` 必须阻断批准；`deferred` 必须同时记录责任人、下一动作和目标版本/发布日期。没有责任人或恢复路径的未决项不得隐藏在备注中。
-
-## 下游消费规则
-
-只有 `approved` 且引用的领域战略为 `approved`、版本当前的阶段包，才可以进入 Spec synthesis。任何领域战略 digest、版本或影响面变化都使阶段包 `stale`，并要求重新评估。

package/template/.hermes/skills/yss-stage-decision/references/stage-decision-package.schema.json

@@ -1,86 +0,0 @@
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://yss.local/schemas/stage-decision-package-v1.json",
-  "title": "YSS Stage Decision Package",
-  "type": "object",
-  "required": ["schema_version", "stage_decision_id", "package_version", "status", "problem_statement", "target_users", "mvp", "non_goals", "success_criteria", "test_seams", "confirmed_decisions", "assumptions", "constraints", "unresolved_items", "terminology_refs", "domain_strategy_ref", "impact_assessment", "downstream_mapping", "evidence_refs", "approval"],
-  "properties": {
-    "schema_version": {"const": 1},
-    "stage_decision_id": {"type": "string", "pattern": "^stage-decision\\.[a-z0-9][a-z0-9-]*$"},
-    "package_version": {"type": "string", "pattern": "^v[0-9]+$"},
-    "status": {"enum": ["draft", "ready-for-human", "approved", "stale", "blocked"]},
-    "problem_statement": {"type": "string", "minLength": 1},
-    "target_users": {"type": "array", "minItems": 1, "items": {"type": "string", "minLength": 1}},
-    "mvp": {"type": "array", "minItems": 1, "items": {"type": "string", "minLength": 1}},
-    "non_goals": {"type": "array", "items": {"type": "string", "minLength": 1}},
-    "success_criteria": {"type": "array", "minItems": 1, "items": {"type": "string", "minLength": 1}},
-    "test_seams": {"type": "array", "minItems": 1, "items": {"type": "string", "minLength": 1}},
-    "confirmed_decisions": {"type": "array", "minItems": 1, "items": {"type": "string", "minLength": 1}},
-    "assumptions": {"type": "array", "items": {"type": "string", "minLength": 1}},
-    "constraints": {"type": "array", "items": {"type": "string", "minLength": 1}},
-    "unresolved_items": {"type": "array", "items": {"$ref": "#/$defs/unresolved"}},
-    "terminology_refs": {"type": "array", "items": {"type": "string", "minLength": 1}},
-    "domain_strategy_ref": {"$ref": "#/$defs/domainRef"},
-    "impact_assessment": {"$ref": "#/$defs/impact"},
-    "downstream_mapping": {"type": "array", "minItems": 1, "items": {"$ref": "#/$defs/mapping"}},
-    "evidence_refs": {"type": "array", "minItems": 1, "items": {"type": "string", "minLength": 1}},
-    "approval": {"$ref": "#/$defs/approval"}
-  },
-  "$defs": {
-    "unresolved": {
-      "type": "object",
-      "required": ["item", "type", "owner", "next_action", "target_version"],
-      "properties": {
-        "item": {"type": "string", "minLength": 1},
-        "type": {"enum": ["blocker", "deferred"]},
-        "owner": {"type": "string", "minLength": 1},
-        "next_action": {"type": "string", "minLength": 1},
-        "target_version": {"type": "string", "minLength": 1}
-      }
-    },
-    "domainRef": {
-      "type": "object",
-      "required": ["domain_strategy_id", "domain_version", "digest", "status", "persisted_ref"],
-      "properties": {
-        "domain_strategy_id": {"type": "string", "pattern": "^domain-strategy\\.[a-z0-9][a-z0-9-]*$"},
-        "domain_version": {"type": "string", "pattern": "^v[0-9]+$"},
-        "digest": {"type": "string", "minLength": 1},
-        "status": {"enum": ["approved", "stale", "blocked"]},
-        "persisted_ref": {"type": "string", "minLength": 1}
-      }
-    },
-    "impact": {
-      "type": "object",
-      "required": ["ui", "api", "data", "backend", "frontend", "cross_repo", "high_risk"],
-      "properties": {
-        "ui": {"type": "boolean"},
-        "api": {"type": "boolean"},
-        "data": {"type": "boolean"},
-        "backend": {"type": "boolean"},
-        "frontend": {"type": "boolean"},
-        "cross_repo": {"type": "boolean"},
-        "high_risk": {"type": "boolean"}
-      }
-    },
-    "mapping": {
-      "type": "object",
-      "required": ["domain_change", "consumer", "propagation", "reapproval_condition"],
-      "properties": {
-        "domain_change": {"type": "string", "minLength": 1},
-        "consumer": {"type": "string", "minLength": 1},
-        "propagation": {"enum": ["direct", "transitive", "not-applicable", "stale"]},
-        "reapproval_condition": {"type": "string", "minLength": 1}
-      }
-    },
-    "approval": {
-      "type": "object",
-      "required": ["approval_ref", "approver", "persisted_ref", "current_version"],
-      "properties": {
-        "approval_ref": {"type": "string", "minLength": 1},
-        "approver": {"type": "string", "minLength": 1},
-        "persisted_ref": {"type": "string", "minLength": 1},
-        "current_version": {"type": "string", "pattern": "^v[0-9]+$"}
-      }
-    }
-  }
-}

package/template/.hermes/skills/yss-stage-decision/references/validation-rules.md

@@ -1,18 +0,0 @@
-# 验证规则
-
-验证分为结构、引用和语义三层：
-
-1. **结构**：Schema 版本、稳定 ID、状态枚举、必填字段、条件字段和证据格式。
-2. **引用**：上下文端点、场景、不变量、术语和下游资产引用必须可解析。
-3. **语义**：禁止关系自环、未知上下文、未批准 Shared Kernel、未解释的语义/技术方向差异、职责重叠、无责任人的不变量和跨上下文直接共享实体。
-
-以下情况必须 `blocked`：关键规则所有权未知、关键术语冲突、上下文边界未定、关键失败场景缺失、事件语义无法解释、领域专家确认缺失。
-
-以下变化应触发精确传播：
-
-- 术语含义变化 → Spec、验收、原型或 API；
-- 上下文边界变化 → 系统架构、OpenAPI、数据和切片；
-- Context Map 关系变化 → 集成契约和模型翻译；
-- 不变量变化 → 测试 seam、实现合同和验证策略。
-
-验证器允许“语义方向 ≠ 技术方向”，但要求 `direction_explanation` 和翻译责任非空。