create-yss-spec 3.5.3 → 3.5.5

package/README.md

@@ -188,3 +188,11 @@ npm pack --dry-run
 ## 治理目录迁移
 
 新实例将分发治理资产安装到 `.template-spec/`，项目规格产物放在 `docs/`。已有实例只有显式运行 `sync --migrate-layout --plan` 审阅后，才运行 `sync --migrate-layout --apply`；`attach` 同样支持该开关。迁移保留项目 tracker 配置，缺少可信摘要、旧文件被修改或目标路径冲突时阻断。普通 sync 不自动改变旧实例目录。
+
+## 固定计划实例迁移
+
+`migrate plan --target-dir <项目绝对路径> --output <项目外新计划.json>` 生成项目只读计划；`migrate apply --plan <计划>` 执行固定候选并保存持久归档。计划后输入变化必须重新规划。需要旧布局迁移或安全退出分发清理时，规划阶段显式加入 `--migrate-layout` / `--prune`。
+
+`migrate status` 查看状态；`migrate recover` 预览中断恢复，`migrate rollback` 预览最近一次成功迁移的整体回退，均需显式 `--apply` 才写入。后续修改、跨家族、未知基线及损坏归档阻断，禁止用 force 绕过。所有新接口支持 `--json`。
+
+旧实例无需先 sync 安装技能：从当前固定版本包的 `resources/upgrade-skill/SKILL.md` 在项目外读取升级入口及相邻 `protocol.md`。默认归档保留于用户目录 `.yss-harness/archives/`；不自动清理。CLI 程序 update/upgrade 与实例迁移相互独立。

package/cli-core.lock.json

@@ -0,0 +1,130 @@
+{
+  "schemaVersion": 1,
+  "sourceRepository": "https://github.com/iloveZzz/yss-spec-project-template.git",
+  "sourceRevision": "b98bafda74fc60c2b41c6020e3d41d84a4f1b1b7",
+  "sourceState": "committed",
+  "sourcePath": ".template-source/cli-core",
+  "coreVersion": "0.2.0",
+  "protocolVersion": 1,
+  "files": {
+    "build.mjs": {
+      "digest": "5f869fecc2f30767c31222e8594456f59671a0744f5a58e95bafaa6338adddbe",
+      "mode": 420
+    },
+    "bundle.mjs": {
+      "digest": "4d60b5f9c10c3487c4e3817a9fd9597734249eb7244cc98f53f4741a1e63a3ce",
+      "mode": 420
+    },
+    "cli.mjs": {
+      "digest": "73aae345737aa7d069283ff7e5539be26498c7a7c94d1100a699a47e4c18e31f",
+      "mode": 420
+    },
+    "command-runner.mjs": {
+      "digest": "4fb7f3c9ca26dff3f955ddb1c6ad545519d3e55af179f834ff67b1c0bf20bffd",
+      "mode": 420
+    },
+    "engine.mjs": {
+      "digest": "70fae490df46a19148a017322ef12f27e6d58d28c7f48fb476ef178dc091dac2",
+      "mode": 420
+    },
+    "family.mjs": {
+      "digest": "2a21348f54e2f8e8f81e1000e3228b3fe3e8817a78244f9866c150318fd129d0",
+      "mode": 420
+    },
+    "gitignore.mjs": {
+      "digest": "dc781dffad8bcff81fd3967546fa8e824641b80d38d47a06eb0909e3401b2940",
+      "mode": 420
+    },
+    "identity.mjs": {
+      "digest": "d1d41fa42aac6ec5cf3e237d1807237f43252b3308e169a838fd3c735f3475ac",
+      "mode": 420
+    },
+    "io.mjs": {
+      "digest": "7edc2095f05086fbff90e6a722950fb6ef57468593a1971bc96a791632457746",
+      "mode": 420
+    },
+    "layout-migration.mjs": {
+      "digest": "0dd1569c43b11c8e4384e7994ac7f6185236756b7297a0a06e867e972b2b036b",
+      "mode": 420
+    },
+    "legacy.mjs": {
+      "digest": "ac5652dee0f3a6d0204a0dad3b0b3a7531a962f620768b72c6aed0d610c446ed",
+      "mode": 420
+    },
+    "migrate.mjs": {
+      "digest": "43788e3916ea95b2800290c70eab3fdd45d1d730705c4a8fadf76dbe8b864304",
+      "mode": 420
+    },
+    "migration-adapter.mjs": {
+      "digest": "43cab1bdeda56859d604f4bbe6d818444c27166d08c6617bac3667c4dd0a3a9d",
+      "mode": 420
+    },
+    "package.json": {
+      "digest": "68d3dfd6451f7a433ff2eb821daa83d59e0c03f19b73d3a2cf5582ee6ce23332",
+      "mode": 420
+    },
+    "scaffold.mjs": {
+      "digest": "ebf16b3ffe95fe00698691ebc71362dfce1e93846a34cb01745b0c063035e209",
+      "mode": 420
+    },
+    "spec-migration-adapter.mjs": {
+      "digest": "45f0bae94552522999abeabef69b9e93220755a089b2a508dcd1a077af07d363",
+      "mode": 420
+    },
+    "tests/build.test.mjs": {
+      "digest": "af6bd15ef81f5160bf94a85ad19cd3d3763b80c8eb577229c9a9b47564e902f6",
+      "mode": 420
+    },
+    "tests/cli.test.mjs": {
+      "digest": "a51dc4bdbc1220bf6c720bd63a05fdbf82101330b012eb535d5b7e6b1ff3693a",
+      "mode": 420
+    },
+    "tests/migration-version.test.mjs": {
+      "digest": "be0389cba634e013f8f7192243057a29e58fe49f3d33372e31eceb96788e001b",
+      "mode": 420
+    },
+    "tests/package-contract.mjs": {
+      "digest": "812129d3c327515269ed2aff08fec97049aa306b65f752d47a3cd004a168be72",
+      "mode": 420
+    },
+    "transaction.mjs": {
+      "digest": "f2fbc4642e953ce00cece2e9f9fe61b7b50f42fabed41e64d5a1902d0ae660a8",
+      "mode": 420
+    },
+    "update.mjs": {
+      "digest": "10a68ac1a709ab3748f9c7e615bc9eeaae82cab9d35077349c13d2ecccd7a111",
+      "mode": 420
+    },
+    "vendor/NOTICES.md": {
+      "digest": "7eba5e5f046d1c0b1c7c02ff036925d2580682c67e09b5521c8fc4f284f3b216",
+      "mode": 420
+    },
+    "vendor/yaml.LICENSE": {
+      "digest": "5bba27375d93e9119f76c1015f7672cf9ad5f70952296e0842fb2243d6376869",
+      "mode": 420
+    },
+    "vendor/yaml.mjs": {
+      "digest": "58c510627769ef4e75e90bcf410d63ba33e64b46bc9cfc53149839d5ccb1709b",
+      "mode": 420
+    },
+    "verification.mjs": {
+      "digest": "e029c8f57b756b4d8709e8b05871b3a09ea8716c71ca93dda0b3480b932b662f",
+      "mode": 420
+    }
+  },
+  "digest": "f5199dba3f9dc94a9b2e92a8b4d65d0633a5a3dfc489d88d30cb461204b8d63d",
+  "upgradeResources": {
+    "SKILL.md": {
+      "digest": "40495ca033ebd0345363714e45571ee77258a435ea1523ae716dc2402ced0487",
+      "mode": 420
+    },
+    "protocol.md": {
+      "digest": "34367c4618617dadb6151bb569bd93616e55bc718d08dc8805e94cdb56cf0a6c",
+      "mode": 420
+    },
+    "references/cli-families.md": {
+      "digest": "70321868fd21c99944c36e8ce9882c5f4910bbe382d2ecfdb8c5c04d5dbe00d4",
+      "mode": 420
+    }
+  }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-yss-spec",
-  "version": "3.5.3",
+  "version": "3.5.5",
   "description": "Initialize a YSS spec project template repository",
   "main": "src/api/index.js",
   "repository": {
@@ -16,7 +16,10 @@
     "src",
     "template",
     "template.manifest.json",
-    "template.snapshot.json"
+    "template.snapshot.json",
+    "vendor/cli-core",
+    "cli-core.lock.json",
+    "resources/upgrade-skill"
   ],
   "bin": {
     "create-yss-spec": "bin/create-yss-spec.js"
@@ -29,7 +32,8 @@
     "test:unit": "node --test tests/*planner*.test.js tests/filesystem-*.test.js tests/validation-modules.test.js tests/doctor-checks.test.js tests/ownership-policy.test.js tests/lifecycle-policy.test.js tests/lifecycle-metadata.test.js tests/verification-runtime.test.js tests/cli-modules.test.js tests/cli-entrypoint.test.js tests/self-update.test.js tests/plan-schema.test.js tests/contracts.test.js tests/error-output.test.js tests/apply-result-contract.test.js tests/programmatic-api-unit.test.js",
     "test:integration": "npm run sync-template && node --test tests/init-cli.test.js tests/sync-command-modular.test.js tests/attach-command-modular.test.js tests/doctor-diff-command.test.js tests/programmatic-api.test.js tests/family-identity.test.js",
     "prepack": "node scripts/sync-template.js --require-committed",
-    "test:prepared": "node --test --test-concurrency=1 tests/*.test.js"
+    "test:prepared": "node --test --test-concurrency=1 tests/*.test.js",
+    "sync-core": "node scripts/sync-core.mjs"
   },
   "devDependencies": {
     "ajv": "^8.20.0"

package/resources/upgrade-skill/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: yss-harness-upgrade
+description: 升级既有 YSS 模板实例，规划同家族版本迁移、定制合并、持久归档、验证与恢复；用于 create-yss-spec 及 design/backend/frontend CLI 实例升级，不处理业务代码或数据库迁移。
+---
+
+# YSS 实例升级
+
+先读取根 `yss-project.yaml`、`CONTEXT.md` 和 [统一协议](protocol.md)。目标必须是已登记的同家族 `project-instance`；身份/schema 不支持时只诊断，不能重新 init 或猜测身份。模板源的技能维护由 `maintaining-skills` 处理。
+
+## 工作顺序
+
+1. 确认目标绝对路径、用户授权范围、实际 CLI 路径及版本、模板 metadata、工作区已有改动。依据 [家族适配](references/cli-families.md) 选定 CLI。未指定目标版本时查询同家族稳定版本并固定精确包版本和摘要，执行期间不再引用 `latest`。CLI 程序升级和项目实例迁移分别记录，不自动安装全局版本。
+2. 用固定 CLI 的 `migrate status` 检查中断事务。有中断时先 `migrate recover` 预览，按既有授权执行 `--apply`，然后重新规划。不得删除状态目录绕过恢复。
+3. `migrate plan --target-dir <绝对路径> --output <项目外全新计划.json>`。旧治理布局迁移显式附加 `--migrate-layout`；退出分发文件清理显式附加 `--prune`。计划阶段不修改项目；检查计划中的版本、变化路径、保留项和归档位置。
+4. 冲突时在项目外起草候选差异和 `--resolutions` 文件。只使用计划报告的可信受管冲突；`preserve` 保留原文，`merge` 提供候选内容并绑定原文件及新模板摘要。向用户展示新的语义取舍，复用已有范围授权；未获授权的新决定保持等待。不能使用 `--force` 批量覆盖，不能先修改项目来消除冲突。
+5. 用相同固定 CLI 执行 `migrate apply --plan <计划>`。执行器重新生成候选并验证计划、归档、身份和输入摘要；`STALE_PLAN` 时重新规划，不能手改摘要续跑。迁移不自动 commit、stash、reset、push 或发布。
+6. 查看回执和实例验证结果，执行相同选项的新计划验证无重复迁移。核对业务文件与既有工作区改动保持，说明保留的定制和现有失败。输出实际版本、归档/回执位置、验证证据和剩余问题；结构检查不能代替真实 CLI 或 Agent 行为验证。
+
+## 恢复与边界
+
+- `migrate recover` 恢复未完成事务；`migrate rollback` 预览最近一次成功迁移的整体回退。两者仅加 `--apply` 才写入。回退遇到后续修改或损坏归档必须保留现场，不覆盖新工作。
+- Spec、Ticket、合同、人工回复、批准和正式验证默认保留。路径迁移不产生新批准；语义或批准绑定变化交回原生命周期，不补造旧状态。
+- 不执行跨家族转换、任意历史版本跳转、业务重构或数据库迁移。未知基线不能由 Agent 猜测；归档不能作为扩大写入授权的理由。
+- 旧实例缺少本技能时，从已固定 CLI 包的 `resources/upgrade-skill/` 在项目外读取入口及相邻协议。不得先同步目标项目来安装升级技能。
+
+本技能只编排，不复制迁移执行器。研究新技术事实时用 `yss-research`；结论输出按 `lifecycle-document-output` 使用 `i-have-adhd`。不批准 Slice、不设置 `ready-for-agent`、不宣称可发布。

package/resources/upgrade-skill/protocol.md

@@ -0,0 +1,40 @@
+# YSS 模板实例升级协议
+
+本协议定义 `yss-harness-upgrade` 与四类 YSS CLI 的同家族实例升级。技能负责判断、冲突方案和授权范围；CLI 负责计划校验、候选验证、持久归档、事务和恢复。历史批准及 Ticket 状态仍由各自权威协议管理。
+
+## 输入与接口
+
+固定精确 CLI 版本、包内容及模板快照，确认真实项目根、metadata/schema、profile、受管基线和 Git 状态。旧版本缺少受支持的基线/schema 时停止，不重新初始化。目标模板使用所执行 CLI 的内置快照；不在 apply 阶段查询 latest 或运行外部计划提供的脚本。
+
+- `migrate plan --target-dir <绝对目录> --output <项目外全新文件> [--archive-dir <项目外全新目录>] [--migrate-layout] [--prune] [--resolutions <文件>]`：项目只读，在项目外生成固定计划；冲突返回机器可读诊断。
+- `migrate apply --plan <文件> [--target-dir <同一目录>]`：显式执行。
+- `migrate status --target-dir <目录>`：只读状态。
+- `migrate recover|rollback --target-dir <目录> [--apply]`：默认只读预览，显式写入。
+
+所有命令接受 `--json`，输出 schemaVersion 1 JSON。失败非零退出；区分 `CONFLICT`、`STALE_PLAN`、`EXECUTOR`、`PLAN`、`ARCHIVE`、`INTERRUPTED`、`CONCURRENT`、`RECOVERY_FAILED` 等。原 CLI 命令及错误协议保持兼容。
+
+## 计划与冲突
+
+计划绑定 schemaVersion、事务 ID、时间、项目根、家族、执行器摘要、目标模板、归档位置、迁移选项、输入清单、Git HEAD/index/gitlink、规则 ID、操作前后内容/权限摘要和候选内容。整体 planDigest 检测意外修改；执行器还重新生成候选操作，不信任手改计划或重新计算摘要。摘要不等于授权。
+
+版本化规则 `managed-sync.v1`、`layout-migration.v1`、`retirement.v1` 复用各 CLI 原有身份/schema 范围和可信文件基线判定；后两者分别要求显式布局迁移与 prune。不凭名称或目录推断旧资产属于模板，不提供未知旧版本的猜测迁移。
+
+`resolutions` 为路径到决议的 JSON 映射。每项包含 `action: preserve|merge`、`beforeDigest`、`templateDigest`；merge 另含候选字节的 `contentBase64`。只接受确实存在、有可信基线且可合并的受管冲突；未知路径、受保护资产、过期摘要或未消费决议拒绝。技能在项目外起草合并差异，新增语义决定取得用户回复后重新生成计划。CLI 不把决议文件当成人工批准。
+
+未修改受管文件自动更新。修改过的退出分发文件保留；`--prune` 只删除仍匹配旧基线的文件。项目拥有的 tracker、业务文档和已批准资产按现有保护规则保留；历史冻结和批准不会因路径移动获得新的有效性。
+
+## 归档、执行与恢复
+
+默认归档位置为 `~/.yss-harness/archives/<项目路径与家族摘要>/<事务ID>/`，可显式改为项目外全新目录。保存 plan.json、before/ 原字节与权限、receipt.json；首版不自动清理归档。布局迁移额外保存 project-copy/ 项目内容副本；不跟随符号链接，排除 Git 内部数据、依赖、索引缓存及事务状态，这些排除项不是迁移写入范围。Git 工作区和索引不重建、不 reset、不 stash。
+
+候选操作先在隔离副本中完成生成锁文件与实例校验。真实执行前重新核验输入，先归档并校验，再在互斥锁下写入。内部事务日志预写并持久化，文件、生成锁及 metadata 属于同一事务。既有业务文件和无关未提交/未跟踪工作保持；输入漂移要求新计划。
+
+内部 `.yss-harness-state/upgrade.json` 索引关联外部回执与事务。失败自动恢复本次写入；进程中断后 recover 校验事务和备份再恢复。成功提交但回执尚未完成的情况依据持久日志收敛状态。保留损坏、冲突及未恢复路径，不把恢复失败写成成功。
+
+rollback 只针对索引中最近一次成功迁移，完整预检全部原件和升级后状态后才开始。任何后续修改、丢失或损坏备份都会阻断；不提供忽略冲突的 force。回退使用新的可恢复事务，不更改 CLI 安装版本。重复 apply 只有在同一计划已成功且结果仍匹配时才返回原回执；恢复或回退后的旧计划不复用。
+
+## 验证与结论
+
+校验身份、布局、Context、Skill 锁和投影等各家族现有实例合同；有失败不跳过。对未迁移资产与 Git index/HEAD/gitlink 做并发检查。迁移完成再规划，证明不会重复执行；计划保留项不是自动消失的冲突。
+
+回执说明实际版本、范围、归档、事务状态和验证结果。原有失败与新增失败分别说明；升级成功不表示产品阶段批准或发布就绪。提交、推送、发布及真实项目迁移均按会话授权，不由技能或计划摘要授予。

package/resources/upgrade-skill/references/cli-families.md

@@ -0,0 +1,14 @@
+# 同家族升级适配
+
+| CLI | 实例 metadata |
+|---|---|
+| create-yss-spec | .yss-template.json |
+| create-yss-harness-design | .yss-harness-design.json |
+| create-yss-harness-backend | .yss-harness-backend.json |
+| create-yss-harness-frontend | .yss-harness-frontend.json |
+
+身份还需通过各 CLI 原有 profile/schema 检查。多个 metadata、旧 dev 家族、未知 schema、符号链接或矛盾 profile 均不能自动接管。`migrate` 不是降级或跨家族工具。
+
+四类 CLI 的新入口一致：`migrate plan|apply|status|recover|rollback`，支持 `--json`。`migrate plan` 只向显式指定的项目外新文件输出；`apply --plan <文件>` 显式写入。recover/rollback 默认只读，写入需 `--apply`。不要从旧 `sync` 推断新接口：主 CLI 普通 sync 会写入，专职 CLI sync 默认预览。
+
+目标模板来自当前固定 CLI 包，不接受计划中的下载地址或脚本。版本、模板和执行器摘要不匹配时更换为生成计划的原包，或重新规划；不得修改计划来绕过。已有 `update/upgrade` 仅更新 CLI 程序，既有 `recover` 仍只恢复原事务。

package/src/cli/help.js

@@ -13,6 +13,7 @@ USAGE
 COMMANDS
   (default)  初始化新的模板实例仓库
   attach     向已有项目补齐受管研发管理资产
+  migrate    固定计划升级：plan/apply/status/recover/rollback
   sync       同步已有模板实例的受管资产
   diff       只计算同步差异，不写入文件
   doctor     检查模板实例、身份、Git 和安全状态

package/src/cli/index.js

@@ -37,6 +37,18 @@ const { resolveCommand } = require("./router");
 const PACKAGE_ROOT = path.resolve(__dirname, "../..");
 
 async function runCli(argv = []) {
+  if (argv[0] === "migrate") {
+    const { runSpecMigration } = await import("../../vendor/cli-core/spec-migration-adapter.mjs");
+    try {
+      const result = runSpecMigration(PACKAGE_ROOT, argv.slice(1));
+      process.stdout.write(JSON.stringify(result, null, 2) + "\n");
+      return result;
+    } catch (error) {
+      process.stdout.write(JSON.stringify({schemaVersion:1,command:"migrate",status:"error",code:error.code || "INVALID",message:error.message,...(error.result?{diagnostic:error.result}:{})},null,2)+"\n");
+      process.exitCode=1;
+      return;
+    }
+  }
   const route = resolveCommand(argv);
 
   if (route.command === "help") {

package/src/filesystem/transaction-runner.js

@@ -1,5 +1,30 @@
 "use strict";
 
+const fs = require("node:fs");
+const path = require("node:path");
+const os = require("node:os");
+function withProjectLock(targetDir, execute) {
+  const index = path.join(targetDir, ".yss-harness-state/upgrade.json");
+  if (fs.existsSync(index)) {
+    const state = JSON.parse(fs.readFileSync(index, "utf8"));
+    if (!Array.isArray(state.runs) || state.runs.some(run => ["applying", "rolling-back"].includes(run.phase))) throw new Error("请先使用 migrate recover 恢复未完成迁移");
+  }
+  const file = path.join(targetDir, ".yss-harness-migrate.lock");
+  if (fs.existsSync(file)) {
+    const info = fs.lstatSync(file);
+    if (!info.isFile() || info.isSymbolicLink() || info.nlink !== 1) throw new Error("迁移锁不是普通文件");
+    const owner = JSON.parse(fs.readFileSync(file, "utf8"));
+    if (owner.host !== os.hostname() || !Number.isInteger(owner.pid) || owner.pid <= 0) throw new Error("未知迁移锁持有者");
+    let alive = true;
+    try { process.kill(owner.pid, 0); } catch (error) { if (error.code === "ESRCH") alive = false; else throw error; }
+    if (alive) throw new Error("另一个同步或迁移正在运行");
+    fs.unlinkSync(file);
+  }
+  const fd = fs.openSync(file, "wx", 0o600);
+  fs.writeFileSync(fd, JSON.stringify({pid:process.pid,host:os.hostname()}));
+  fs.fsyncSync(fd); fs.closeSync(fd);
+  try { return execute(); } finally { fs.unlinkSync(file); }
+}
 const { FileTransaction } = require("./transaction");
 
 function runInTransaction({
@@ -13,6 +38,7 @@ function runInTransaction({
     throw new TypeError("runInTransaction requires execute callback");
   }
 
+  return withProjectLock(targetDir, () => {
   const transaction = new TransactionClass(targetDir);
 
   try {
@@ -34,6 +60,7 @@ function runInTransaction({
       `${error.message}\n已回滚本次 ${operation}；临时备份保留于 ${transaction.backupRoot}`,
     );
   }
+  });
 }
 
 module.exports = {

package/src/template/asset-runtime.js

@@ -26,8 +26,22 @@ const COMMON = {
     ".template-spec/process/harness-process-tailoring.md",
     ".template-spec/process/document-writing.md",
     ".template-spec/process/contract-reading.md",
+    ".template-spec/process/structured-assets.md",
+    ".template-spec/process/schemas/approval-record.schema.json",
+    ".template-spec/process/schemas/review-bundle.schema.json",
+    ".template-spec/process/templates/lifecycle-checkpoint-template.json",
+    ".template-spec/templates/approval-record-template.json",
+    ".template-spec/process/reading-policy.yaml",
+    ".template-spec/process/schemas/reading-policy.schema.json",
+    ".template-spec/process/schemas/reading-manifest.schema.json",
+    ".template-spec/process/schemas/domain-strategy-reading.schema.json",
+    ".template-spec/process/schemas/stage-decision-package-reading.schema.json",
     ".template-spec/process/subagent-collaboration.md",
     ".template-spec/process/stage-tracking.md",
+    ".template-spec/process/business-tickets.md",
+    ".template-spec/process/schemas/business-tickets-v1.schema.json",
+    ".template-spec/process/project-ci.md",
+    ".template-spec/process/checkpoint-boundary.yaml",
     ".template-spec/process/schemas/context-reconciliation.schema.json",
     ".template-spec/process/schemas/digital-human-task-package.schema.json",
     ".template-spec/process/schemas/lifecycle-checkpoint.schema.json",
@@ -57,33 +71,39 @@ const COMMON = {
     "scripts/prepare-read-only-intake",
     "scripts/run-read-only-intake",
     "scripts/contract",
+    "scripts/check-plan-stage-coverage",
     "scripts/stage-tracking",
+    "scripts/project-ci",
+    "scripts/project-ci-transition",
+    "scripts/lifecycle-status",
     "scripts/gitworks",
   ],
 };
 
+const BUSINESS_FILES = [".template-spec/templates/business-ticket-template.md", ".template-spec/templates/business-ticket-set-template.yaml", ".template-spec/templates/business-ticket-review-template.yaml"];
 const STAGES = Object.freeze({
   "stage.entry-triage": { files: [], scripts: [], skills: [] },
   "stage.plan": {
     prefixes: [".template-spec/plan/"],
-    files: [".template-spec/process/plan-migration.md"],
-    scripts: ["scripts/verify-plan-spec-entry"],
+    files: [".template-spec/process/plan-migration.md", ".template-spec/process/plan-spec-quality.md"],
+    scripts: ["scripts/verify-plan-spec-entry", "scripts/inspect-plan-spec"],
     skills: [],
   },
   "stage.spec-architecture": {
     files: [
+      ...BUSINESS_FILES,
       ".template-spec/templates/spec-template.md",
       ".template-spec/templates/spec-delta-template.md",
       ".template-spec/architecture/templates/business-architecture-template.md",
       ".template-spec/architecture/templates/functional-architecture-template.md",
     ],
-    scripts: [],
+    scripts: ["scripts/verify-business-tickets"],
     skills: [],
   },
   "stage.product-design": {
     prefixes: [".template-spec/design/"],
-    files: [],
-    scripts: ["scripts/design-md"],
+    files: BUSINESS_FILES,
+    scripts: ["scripts/design-md", "scripts/verify-business-tickets"],
     skills: ["yss-prototype-stage"],
   },
   "stage.system-data-engineering": {
@@ -96,6 +116,7 @@ const STAGES = Object.freeze({
       ".template-spec/templates/implementation-repo-registry-template.md",
     ],
     scripts: [
+      "scripts/verify-business-tickets",
       "scripts/backend-platforms",
       "scripts/backend-delivery",
       "scripts/repository-scope-policy",

package/src/template/verification-runtime.js

@@ -39,6 +39,13 @@ function initializeGitRepository(targetDir) {
   }
 }
 
+let verificationOutput = (text) => process.stdout.write(text);
+function withVerificationOutput(writer, execute) {
+  const previous = verificationOutput;
+  verificationOutput = writer;
+  try { return execute(); } finally { verificationOutput = previous; }
+}
+
 function runTemplateVerification(targetDir, scriptPath, args = ["--check"]) {
   const commandPath = targetPath(targetDir, scriptPath);
   const result = spawnSync(commandPath, args, {
@@ -48,7 +55,7 @@ function runTemplateVerification(targetDir, scriptPath, args = ["--check"]) {
   });
   const output = [result.stdout, result.stderr].filter(Boolean).join("");
   if (output) {
-    process.stdout.write(output.endsWith("\n") ? output : `${output}\n`);
+    verificationOutput(output.endsWith("\n") ? output : `${output}\n`);
   }
   if (result.status !== 0) {
     const detail = result.error?.message || output.trim();
@@ -193,6 +200,7 @@ function refreshGeneratedProjectInstance(targetDir, options = {}) {
 }
 
 module.exports = {
+  withVerificationOutput,
   verificationEnvironment,
   initializeGitRepository,
   runTemplateVerification,

package/template/.agents/skills/.strategic-design-skills-manifest.json

@@ -3,28 +3,28 @@
   "source": "iloveZzz/yss-harness-design-agent",
   "source_type": "git-submodule",
   "source_root": ".agents/skills",
-  "source_revision": "ed8865b79dbe1cb59277fe643c3cb27139674530",
+  "source_revision": "fbe4084276a8fe9a8f59e58481f2913133346eaf",
   "adaptation_ref": ".template-source/agents/strategic-design-skills-integration.md",
   "skills": [
     {
       "upstream": "prototype-review",
       "canonical": "prototype-review",
-      "upstream_hash": "68c6e4613354ad919bab3d718739f1cc6930d8df0777d6f7db90435bdae77d52"
+      "upstream_hash": "9c0b042760f7d741487e62eaccf55b5079a1991e5489286560e278c9642a09b0"
     },
     {
       "upstream": "yss-prototype-stage",
       "canonical": "yss-prototype-stage",
-      "upstream_hash": "7781df6293f381bd40781d2f6b163cf824f959624b1c34aeb9c241d6be709c89"
+      "upstream_hash": "0e82e8c0f6b5446dbe48aec8df092574ab895be303efe33d8fc8457bce98d02e"
     },
     {
       "upstream": "yss-design-system",
       "canonical": "yss-design-system",
-      "upstream_hash": "ae040c639056ecf2160f1231e30ac67360bd8aa1e030eac778520dd56af8068c"
+      "upstream_hash": "3884a6b9e0a836c2c783bbe51d7737fee874662ea1964a7df545c2f1ababf4e3"
     },
     {
       "upstream": "yss-stage-decision",
       "canonical": "yss-stage-decision",
-      "upstream_hash": "6cd0ed5aa21d68cea871d0bd202beb3b28cca2981f075ad9c24667ac030118d2"
+      "upstream_hash": "77fa3075f90966821881998ff5fa9d674672bd2568e70b8d877402efeb360453"
     }
   ],
   "source_state": "committed"

package/template/.agents/skills/archify/SKILL.md

@@ -33,43 +33,13 @@ When the current repository contains `yss-project.yaml`, these rules override th
 
 ## Fast authoring path
 
-Use this bounded path for ordinary generation. Do not read the optional Viewer Runtime reference unless the user asks about those features.
-
-1. Choose `architecture`, `workflow`, `sequence`, `dataflow`, or `lifecycle` from the question.
-2. Read one matching schema in `schemas/`, `schemas/common.schema.json`, and one matching JSON example in `examples/`. Read only those files. Fresh authorship means new stable IDs, domain wording, and layout; use the example for field shape, not facts. New workflow sources use `schema_version: 2` and its readable layout contract; keep `schema_version: 1` only when preserving an existing workflow's fixed geometry. When real product identity matters, query `node bin/archify.mjs brands "<name>" --json`; read `references/brand-marks.md` only for an unknown brand with a user-provided URL.
-3. After required source and schema checks, write an early candidate; do not block necessary fact or permission checks merely to make the next tool action a write. Write the candidate before inspecting renderer internals. Do not plan exact coordinates in prose. Start with one clear main path, short side branches, sparse labels, and at most 12 primary nodes. Set `meta.quality_profile` to `"showcase"` unless the user explicitly requests a dense `standard` map. Start with automatic routes and labels. Do not add `via`, `channelX`, `channelY`, or `labelAt` before a diagnostic calls for one; apply at most one diagnosed geometry control per repair.
-4. Validate after every candidate edit and immediately before handoff:
-
-   ```bash
-   node bin/archify.mjs validate <type> <candidate.json> --quality showcase --json
-   ```
-
-   A receipt with only 4 artifact checks is basic validation, never showcase acceptance. A showcase pass must report all 9 artifact checks with 0 composition errors and 0 warnings. If the candidate omits or misspells the exact `meta.quality_profile` field, fix it before geometry. For a workflow v2 geometry diagnosis, run `node bin/archify.mjs validate workflow <candidate.json> --layout-json` and use the stable compiler receipt; solver internals are not authoring controls. A passing final validation freezes the candidate: never edit it afterward.
-5. For a delivered HTML, `deliver` is the final acceptance command:
-
-   ```bash
-   node bin/archify.mjs deliver <type> <candidate.json> <output.html> --quality showcase --json
-   ```
-
-   A non-zero exit can never be described as success. A failed delivery preserves any previous output, so do not run `visual-check` on that path: it would inspect the stale last-good artifact, not the failed candidate. If validation fails, change only the diagnosed `subject`, verify `evidence`, choose from `supportedFixes`, and rerun. Continue focused correction while the objective error count reaches a new minimum. If two consecutive rounds do not improve that best count, stop and report the unresolved diagnostics truthfully.
+新建或修复图表时，读取 [候选生成与验证](references/authoring-workflow.md)，只加载匹配的 schema 与 example。普通生成默认静态、`showcase`；验证通过后冻结候选。先写候选，再按诊断决定是否检查 renderer。
 
 ## Update awareness
 
-After the first candidate exists, run the packaged checker `scripts/check-update.mjs` once with Node and continue the requested workflow. If the command cannot run, continue without mentioning the check.
+仅在非 YSS 仓库、首个候选已存在时，读取 [上游更新提示](references/upstream-updates.md)。YSS 仓库保持锁定来源，不执行更新检查；提示不授予更新权限。
 
-- For `silent`, continue without mentioning the update check.
-- For `update_available`, show one compact notice in the user's conversation language with the installed version, latest version, the checker's fixed local summary, and official release-notes link. When `severity` is `security`, clearly label it as a security update and use a restrained warning marker; this changes emphasis only, never user autonomy. Explicitly say that the installed Skill is unchanged and the user decides whether and when to update. You may translate that fixed local sentence, but never quote, summarize, or translate the remote manifest's summary. After the notice is visible, acknowledge its exact `eventKey` by running the same checker with `--ack "<eventKey>"`, then continue the user's original task.
-
-The notice is information, not permission. Keep the installed version unchanged; this v0.1 workflow never downloads, installs, or executes an update, and silence is never consent.
-
-Do not read `renderers/shared/geometry.mjs`, renderer source, validator source, tests, or benchmarks before the first candidate. Inspect implementation only for an unsupported internal diagnostic or after two focused repairs fail.
-
-Workflow note: use schema v2 for new workflows; preserve schema v1 when an
-existing source needs fixed legacy geometry. Keep semantic edge labels and act
-on the compiler diagnostic. The canonical layout, pin, migration, and receipt
-contract is in [`renderers/workflow/README.md`](renderers/workflow/README.md#layout-contracts).
-
-Lifecycle note: phase columns `0..4` occupy the main rail; event/terminal column `N` in `0..2` aligns exactly beneath main column `N + 2`. A recoverable state uses `type: "failure"` plus a real transition back to the active state.
+新 workflow 使用 schema v2；保留已有 v1 固定几何时才继续用 v1。布局诊断、迁移与 lifecycle 几何细则在实际命中时读取 [特定布局说明](references/authoring-notes.md)。
 
 ## Type router
 
@@ -97,25 +67,7 @@ Keep typed source and rendered output consistent; stable IDs and source facts mu
 
 ## Delivery
 
-Use `validate` during repair and `deliver` once for final acceptance. Delivery freezes the exact specification bytes into a private same-directory snapshot, renders and checks that snapshot, atomically commits the HTML, and reports SHA-256 plus byte counts for both specification and artifact. This is deterministic artifact evidence; it does not exercise the Viewer in a browser.
-
-After delivery, collect bounded desktop evidence without modifying or rerendering the trusted HTML:
-
-```bash
-node bin/archify.mjs visual-check <output.html> --json
-```
-
-`visual-check` collects automated browser evidence from the exact delivered HTML without modifying or rerendering it. Its machine-readable measurements and screenshots do not approve perceptual polish. Follow `references/delivery-contract.md` for the canonical receipt fields, coverage, sidecars, exit behavior, and supplementary manual-record requirements.
-
-Keep the three claims separate: `deliver` proves deterministic artifact checks, `visual-check` proves bounded behavior in a real browser, and perceptual visual review requires an actual human or image-capable reviewer. Report browser evidence and perceptual review independently. An unconstrained glance can support only perceptual review; use the canonical delivery contract when recording supplementary manual browser work or handling an environmental failure.
-
-Add `--open` only when the user wants an immediate local preview. For an active desktop authoring loop, the optional command is:
-
-```bash
-node bin/archify.mjs preview <type> <input>.json <output>.html --quality showcase
-```
-
-Never start preview by default. Read `references/delivery-contract.md` when using preview, repository evidence, export receipts, visual review, or post-commit opening.
+交付 HTML 前读取 [交付执行](references/delivery-workflow.md) 与 [证据合同](references/delivery-contract.md)。YSS 仓库始终使用上文安全 wrapper；失败不检查旧输出。分别报告确定性检查、真实浏览器证据、感知审查，非零退出不得称成功；预览仅按用户请求开启。
 
 ## Optional viewer capabilities
 

package/template/.agents/skills/archify/references/authoring-notes.md

@@ -0,0 +1,12 @@
+# 特定布局说明
+
+仅在入口所列条件命中时读取本文件。Markdown 链接相对本文件；行内 references/assets/schemas 路径相对 Skill 根目录。Skill 自带的 bin/scripts 命令从 Skill 根目录执行；明确注明 repository root 的包装命令仍从项目根目录执行。
+
+Do not read `renderers/shared/geometry.mjs`, renderer source, validator source, tests, or benchmarks before the first candidate. Inspect implementation only for an unsupported internal diagnostic or after two focused repairs fail.
+
+Workflow note: use schema v2 for new workflows; preserve schema v1 when an
+existing source needs fixed legacy geometry. Keep semantic edge labels and act
+on the compiler diagnostic. The canonical layout, pin, migration, and receipt
+contract is in [`renderers/workflow/README.md`](../renderers/workflow/README.md#layout-contracts).
+
+Lifecycle note: phase columns `0..4` occupy the main rail; event/terminal column `N` in `0..2` aligns exactly beneath main column `N + 2`. A recoverable state uses `type: "failure"` plus a real transition back to the active state.

package/template/.agents/skills/archify/references/authoring-workflow.md

@@ -0,0 +1,25 @@
+# 图表候选生成与验证
+
+仅在入口所列条件命中时读取本文件。Markdown 链接相对本文件；行内 references/assets/schemas 路径相对 Skill 根目录。Skill 自带的 bin/scripts 命令从 Skill 根目录执行；明确注明 repository root 的包装命令仍从项目根目录执行。
+
+## Fast authoring path
+
+Use this bounded path for ordinary generation. Do not read the optional Viewer Runtime reference unless the user asks about those features.
+
+1. Choose `architecture`, `workflow`, `sequence`, `dataflow`, or `lifecycle` from the question.
+2. Read one matching schema in `schemas/`, `schemas/common.schema.json`, and one matching JSON example in `examples/`. Read only those files. Fresh authorship means new stable IDs, domain wording, and layout; use the example for field shape, not facts. New workflow sources use `schema_version: 2` and its readable layout contract; keep `schema_version: 1` only when preserving an existing workflow's fixed geometry. When real product identity matters, query `node bin/archify.mjs brands "<name>" --json`; read `references/brand-marks.md` only for an unknown brand with a user-provided URL.
+3. After required source and schema checks, write an early candidate; do not block necessary fact or permission checks merely to make the next tool action a write. Write the candidate before inspecting renderer internals. Do not plan exact coordinates in prose. Start with one clear main path, short side branches, sparse labels, and at most 12 primary nodes. Set `meta.quality_profile` to `"showcase"` unless the user explicitly requests a dense `standard` map. Start with automatic routes and labels. Do not add `via`, `channelX`, `channelY`, or `labelAt` before a diagnostic calls for one; apply at most one diagnosed geometry control per repair.
+4. Validate after every candidate edit and immediately before handoff:
+
+   ```bash
+   node bin/archify.mjs validate <type> <candidate.json> --quality showcase --json
+   ```
+
+   A receipt with only 4 artifact checks is basic validation, never showcase acceptance. A showcase pass must report all 9 artifact checks with 0 composition errors and 0 warnings. If the candidate omits or misspells the exact `meta.quality_profile` field, fix it before geometry. For a workflow v2 geometry diagnosis, run `node bin/archify.mjs validate workflow <candidate.json> --layout-json` and use the stable compiler receipt; solver internals are not authoring controls. A passing final validation freezes the candidate: never edit it afterward.
+5. For a delivered HTML, `deliver` is the final acceptance command:
+
+   ```bash
+   node bin/archify.mjs deliver <type> <candidate.json> <output.html> --quality showcase --json
+   ```
+
+   A non-zero exit can never be described as success. A failed delivery preserves any previous output, so do not run `visual-check` on that path: it would inspect the stale last-good artifact, not the failed candidate. If validation fails, change only the diagnosed `subject`, verify `evidence`, choose from `supportedFixes`, and rerun. Continue focused correction while the objective error count reaches a new minimum. If two consecutive rounds do not improve that best count, stop and report the unresolved diagnostics truthfully.

package/template/.agents/skills/archify/references/delivery-workflow.md

@@ -0,0 +1,25 @@
+# 图表交付执行
+
+仅在入口所列条件命中时读取本文件。Markdown 链接相对本文件；行内 references/assets/schemas 路径相对 Skill 根目录。Skill 自带的 bin/scripts 命令从 Skill 根目录执行；明确注明 repository root 的包装命令仍从项目根目录执行。
+
+## Delivery
+
+Use `validate` during repair and `deliver` once for final acceptance. Delivery freezes the exact specification bytes into a private same-directory snapshot, renders and checks that snapshot, atomically commits the HTML, and reports SHA-256 plus byte counts for both specification and artifact. This is deterministic artifact evidence; it does not exercise the Viewer in a browser.
+
+After delivery, collect bounded desktop evidence without modifying or rerendering the trusted HTML:
+
+```bash
+node bin/archify.mjs visual-check <output.html> --json
+```
+
+`visual-check` collects automated browser evidence from the exact delivered HTML without modifying or rerendering it. Its machine-readable measurements and screenshots do not approve perceptual polish. Follow `references/delivery-contract.md` for the canonical receipt fields, coverage, sidecars, exit behavior, and supplementary manual-record requirements.
+
+Keep the three claims separate: `deliver` proves deterministic artifact checks, `visual-check` proves bounded behavior in a real browser, and perceptual visual review requires an actual human or image-capable reviewer. Report browser evidence and perceptual review independently. An unconstrained glance can support only perceptual review; use the canonical delivery contract when recording supplementary manual browser work or handling an environmental failure.
+
+Add `--open` only when the user wants an immediate local preview. For an active desktop authoring loop, the optional command is:
+
+```bash
+node bin/archify.mjs preview <type> <input>.json <output>.html --quality showcase
+```
+
+Never start preview by default. Read `references/delivery-contract.md` when using preview, repository evidence, export receipts, visual review, or post-commit opening.