create-yss-spec 3.5.0 → 3.5.3

package/template/.cursor/skills/yss-openapi-governance/SKILL.md

@@ -5,7 +5,7 @@ description: "维护、校验、冻结或导出 YSS OpenAPI 3.1 设计合同；
 
 # YSS OpenAPI Governance
 
-已有生命周期资产优先用 `scripts/contract view <资产> --kind <类型>` 阅读；执行任务用 `--profile task --unit <ID>`，绑定与校验明细用 `--profile full`。视图不授予执行权限，仍按本 Skill 的原始来源和批准门禁处理。类型、准备和迁移见 `docs/process/contract-reading.md`。
+已有生命周期资产优先用 `scripts/contract view <资产> --kind <类型>` 阅读；执行任务用 `--profile task --unit <ID>`，绑定与校验明细用 `--profile full`。视图不授予执行权限，仍按本 Skill 的原始来源和批准门禁处理。类型、准备和迁移见 `.template-spec/process/contract-reading.md`。
 
 本 skill 负责 YSS OpenAPI 的 **YAML-first** 工作流：
 
@@ -17,11 +17,11 @@ Spec / 设计输入 → OpenAPI YAML Draft → 审查与 Freeze → JSON 派生
 
 YSS DTO 的可复用 HTTP/JSON 映射由 `.agents/skills/yss-dto/references/openapi-wire-profile.yaml` 单一维护。它描述公开 wire shape，不是 Java 字段或 getter 清单；本 skill 必须消费 profile，不能在治理文档、feature YAML 和 JSON 中各自发明 `SingleResult`、`PageResult` 或 `PageQuery` 字段表。
 
-文档输出时按 `lifecycle-document-output` 条件调用 `i-have-adhd`，读取 `docs/process/document-writing.md`；作用域仅限当前产物，派发时传递条件及引用。
+文档输出时按 `lifecycle-document-output` 条件调用 `i-have-adhd`，读取 `.template-spec/process/document-writing.md`；作用域仅限当前产物，派发时传递条件及引用。
 
 ## 文档写作
 
-编写接口说明和契约评审交接正文前，读取 `docs/process/document-writing.md` 的共用写法及工程契约指引；协议标识、schema、冻结状态和验证记录按原合同保存。
+编写接口说明和契约评审交接正文前，读取 `.template-spec/process/document-writing.md` 的共用写法及工程契约指引；协议标识、schema、冻结状态和验证记录按原合同保存。
 
 ## 边界与职责
 
@@ -34,7 +34,7 @@ YSS DTO 的可复用 HTTP/JSON 映射由 `.agents/skills/yss-dto/references/open
 - 在 `docs/.scratch/<feature>/api/<feature>-validation.yaml` 持久化结构校验记录，并用 `scripts/verify-openapi-draft-validation-record` 复核当前 YAML SHA-256、锁定的 Redocly 版本、实际命令、退出码、执行时间和证据引用。
 - 在 OpenAPI Freeze 后，用锁定的 Redocly CLI 将 YAML bundle 为 JSON，并记录可重现证据。
 - 维护治理记录、Freeze 记录和 JSON 派生记录。
-- 在技术分析中生成 `api-contract-decision-v1`：有 API 影响时以原始字节摘要闭包绑定权威 YAML、Validation、独立 Draft Review 和 Freeze；无 API 影响时绑定影响评估、明确原因和至少一项可读证据，且不得生成空占位资产。
+- 在技术分析中生成 API Contract Decision（版本与历史兼容见下文第 3 步）：有 API 影响时以原始字节摘要闭包绑定权威 YAML、Validation、独立 Draft Review 和 Freeze；无 API 影响时绑定影响评估、明确原因和至少一项可读证据，且不得生成空占位资产。
 - Spec Delta 影响存在时，在 `docs/.scratch/<feature>/spec-delta/` 记录与冻结 YAML 的关系；没有影响时明确记录 `not-applicable`。
 
 不使用本 skill 来替代：
@@ -72,7 +72,7 @@ pnpm exec redocly bundle \
 2. **运行结构与治理校验**
    - 先执行项目 lockfile 锁定版本的 `pnpm exec redocly lint`；CI 可以包装调用，但 validation record 必须记录这条实际命令与退出码。
    - 检查 YAML 可解析、`$ref` 可解析、路径参数完整、operationId 唯一、examples 合法、schema 命名稳定。
-   - 从 `docs/api/templates/openapi-draft-validation-record-template.yaml` 创建 `<feature>-validation.yaml`，记录 YAML SHA-256 与 lint 工具链；运行 `scripts/verify-openapi-draft-validation-record --root <project-root> <record>`。自定义解析脚本可以补充诊断，但不能代替锁定的 Redocly lint evidence。
+   - 从 `.template-spec/api/templates/openapi-draft-validation-record-template.yaml` 创建 `<feature>-validation.yaml`，记录 YAML SHA-256 与 lint 工具链；运行 `scripts/verify-openapi-draft-validation-record --root <project-root> <record>`。自定义解析脚本可以补充诊断，但不能代替锁定的 Redocly lint evidence。
    - 对每个 P0 写模型、配置模型及影响关键交互的读模型建立字段级追踪：`Spec/交互来源 → operationId → request/response schema → property path → 类型与嵌套形状 → create/update requiredness → nullable/default/enum/format → error/test seam`。数组元素使用 `items[].property` 一类稳定 property path。
    - create/update 或其他不同生命周期操作复用同一写 schema 时，逐操作证明 requiredness 与省略语义一致；若不一致，拆分 schema 或明确条件契约。凭据类字段还要说明创建、更新、掩码回显、省略保留与显式清空语义，不能仅凭字段名统一设为必填。
    - 先运行 `scripts/verify-yss-dto-openapi-profile`，并记录 profile 版本；检查 `/api/v1/` 版本策略（或记录例外）、`x-yss-response-wrapper`、`YssResultMeta` + `allOf` 具体 schema、统一错误结构、分页、幂等 / 乐观锁和契约测试 seam。
@@ -83,12 +83,12 @@ pnpm exec redocly bundle \
    - 将通过 verifier 且 SHA-256 与当前 YAML 一致的 validation record 交给 `yss-openapi-draft-review`。缺锁定 lint 时可以先做语义预审，但独立 Review 总结果必须为 `Blocked`；不能用“Freeze 前补 lint”支持 `Approved`。
    - YAML、validation record 或 lint ruleset 变化后，旧结构证据与旧 Review 立即失效，必须重新校验和审查。阻断项未关闭前，YAML 仍是 review-only Draft，不得生成生产客户端。
    - Freeze 记录必须引用 YAML 路径、Git ref（如适用）和 YAML SHA-256。冻结后 API 行为变更必须先回到 YAML Draft 与审查。
-   - 将同一 YAML 的版本与摘要、validation record、独立 Review 和 Freeze 写入 API Contract Decision v1。`gate.engineering-contract-approved` 一次批准同时绑定 Technical Design、Data Architecture Decision、API Contract Decision；API `required` 时还必须直接绑定冻结 YAML。不得另造字符串 URI 或仅凭 `status: approved` 关闭门禁。
+   - 将同一 YAML 的版本与摘要、validation record、独立 Review 和 Freeze 写入 API Contract Decision（新建 v2；历史 v1 只读兼容，准备与迁移见 `.template-spec/process/contract-reading.md`）。`gate.engineering-contract-approved` 一次批准同时绑定 Technical Design、Data Architecture Decision、API Contract Decision；API `required` 时还必须直接绑定冻结 YAML。不得另造字符串 URI 或仅凭 `status: approved` 关闭门禁。
 
 4. **从冻结 YAML 派生 JSON**
    - 使用上面的锁定 `redocly bundle` 命令生成 `docs/.scratch/<feature>/api/<feature>.json`，JSON 不纳入人工编辑面。
    - 对输出 JSON 重新执行解析 / lint（按项目工具链），确认 bundle 未产生组件重名冲突或无法解析的引用。
-   - 写入 `docs/.scratch/<feature>/api/<feature>-json-export.md`，可从 `docs/api/templates/openapi-json-export-record-template.md` 创建。
+   - 写入 `docs/.scratch/<feature>/api/<feature>-json-export.md`，可从 `.template-spec/api/templates/openapi-json-export-record-template.md` 创建。
    - 记录 YAML SHA-256、JSON SHA-256、OAS 版本、Redocly CLI 版本与 lockfile 引用、完整命令、metafile、`$ref` 例外以及结果。
 
 5. **交给下游前端**

package/template/.cursor/skills/yss-product-lifecycle/SKILL.md

@@ -5,23 +5,23 @@ description: 编排 YSS 研发全生命周期；当阶段、产物、门禁或 S
 
 # YSS Product Lifecycle
 
-合同阅读：`scripts/contract view`；见 `docs/process/contract-reading.md`。
+合同阅读：`scripts/contract view`；见 `.template-spec/process/contract-reading.md`。
 
-主控识别请求、仓库身份和可信阶段，计算 frontier、派发与验收工作单元；专项 Skill 负责设计、实现和独立审查。
+主控识别请求、身份和阶段，计算 frontier、派发并验收工作单元。
 
-文档按 `document_writing` 条件调用 `i-have-adhd`，并传递 `docs/process/document-writing.md` 规范。
+文档按 `document_writing` 条件调用 `i-have-adhd`，并传递 `.template-spec/process/document-writing.md` 规范。
 
 ## 事实源与按需加载
 
-先读 `yss-project.yaml`、`CONTEXT.md`、相关 ADR、父 Ticket/checkpoint 和当前资产，按需加载合同子树：
+先读 `yss-project.yaml`、`AGENTS.md`、`CONTEXT.md` 和当前任务视图；按需加载命中的合同子树：
 
 | 事实 | 权威来源 |
 |---|---|
-| 阶段、聚合门禁、内部检查、产物、工作单元、证据和稳定 ID | `docs/process/lifecycle-registry.yaml` |
+| 阶段、聚合门禁、内部检查、产物、工作单元、证据和稳定 ID | `.template-spec/process/lifecycle-registry.yaml` |
 | 执行模式、流转、readiness、暂停、结果和授权语义 | `references/orchestration-contract.yaml` |
-| Skill 身份、capability、依赖和路由 | `docs/agents/yss-skill-registry.yaml` |
-| 数字人角色、运行时和会签策略 | `docs/agents/digital-human-roles.yaml` |
-| 影响面、裁剪和模板维护强度 | `docs/process/harness-process-tailoring.md`、`docs/process/maintenance-intensity.yaml` |
+| Skill 身份、capability、依赖和路由 | `.template-spec/agents/yss-skill-registry.yaml` |
+| 数字人角色、运行时和会签策略 | `.template-spec/agents/digital-human-roles.yaml` |
+| 影响面、裁剪和模板维护强度 | `.template-spec/process/harness-process-tailoring.md`、`.template-source/process/maintenance-intensity.yaml` |
 
 用 `scripts/query-lifecycle-context` 查询合同：
 
@@ -40,7 +40,7 @@ scripts/query-lifecycle-context --mode route --stage stage.plan --work-unit work
 3. 按合同 `request_triage` 选择 `route`、`orchestrate`、`resume`、`audit`；明确行动请求无需模式关键字，意图不明时只读 `route`。`modes`、门禁及授权边界仍适用。
 4. `project-instance` 按生命周期注册表推进；`template-source` 只走模板维护流程。
 
-Plan 入口读取 `docs/plan/README.md` 和 `docs/process/plan-migration.md`，按注册表的退出条件核查战略输入。关键未决项阻断进入 Spec；非关键细节须有责任人、解决时点和下游接收方。只使用 Plan 标识；旧阶段不提供兼容解析，历史批准不自动成为 Plan 批准。
+Plan 入口读取 `.template-spec/plan/README.md` 和 `.template-spec/process/plan-migration.md`，核查战略输入与退出条件。关键未决项阻断 Spec；其他未决项记录责任人、解决时点和接收方。只用 Plan 标识；旧阶段不兼容解析，历史批准不自动沿用。
 
 理解、澄清与纠错见 [请求分诊协议](references/request-triage.md)；用 `scripts/query-lifecycle-context --include request_triage` 查询合同。先查上下文和证据，只问影响下一动作的缺口，不按问题长度追问。
 
@@ -70,8 +70,8 @@ Plan 入口读取 `docs/plan/README.md` 和 `docs/process/plan-migration.md`，
 
 1. 从真实资产重建当前状态，查询当前 mode、stage、work-unit 及必要合同子树。
 2. 评估影响面、上游新鲜度、门禁和阻塞，选择第一个未阻塞工作单元；不把 `not-applicable` 当作豁免。
-3. 原生工作单元由主控持有正式资产；专项工作通过结构化任务包派发，只调用编排合同允许的 model-invoked skill。
-4. `grill-with-docs`、`to-spec`、`to-tickets`、`implement` 等兼容入口只可由用户显式调用。主控先预检输入、路径和门禁；入口按 `matt_invocation_boundary` 写入其产物并回交验收，不批准或改变 Ticket 就绪状态。原生资产仍归主控。
+3. 原生工作单元由主控持有正式资产；专项按结构化任务包派发，只调用合同允许的 model-invoked skill。
+4. `to-spec`、`to-tickets`、`implement` 等兼容入口只可由用户显式调用。主控先预检输入、路径和门禁；入口按 `matt_invocation_boundary` 写入其产物并回交验收，不批准或改变 Ticket 就绪状态。原生资产仍归主控。
 5. 先对照用户目标逐项验收，检查遗漏诉求、错误假设与尚未解决的问题，再验收 `Workflow Execution Result`：工作单元、合同、允许写路径、`context_reconciliation`、证据、实际验证、延期 seam、漂移和下一路由必须可核验。实现派发额外绑定当前 Slice Implementation Contract v3；其他阶段不得伪造该合同。
 6. 在授权边界内继续下一工作单元；遇到人工决定、新授权、证据冲突、专项失败或合并/发布结论时暂停。暂停不得阻断无依赖的独立工作。
 
@@ -79,22 +79,22 @@ Plan 入口读取 `docs/plan/README.md` 和 `docs/process/plan-migration.md`，
 
 ## 面向业务角色
 
-默认使用业务语言推进：
+使用业务语言推进：
 
 `机会与目标 → 业务故事 → 责任与交接 → 规则、例子与疑问 → 可验收需求 → 页面验证 → 业务任务 → 交接研发`
 
-按当前决策澄清目标、流程、责任、规则、最小范围和验收例子。可生成引用权威资产的“业务方案总览”，展示状态、未决项、责任人和下一步；不复制正文或新增门禁。
+按当前决策澄清目标、流程、责任、规则、范围和验收例子。业务方案总览引用权威资产，展示状态、未决项、责任人和下一步；不复制正文或新增门禁。
 
-Plan → Spec（含正式草稿、恢复与显式 `to-spec`）写入前，按 `docs/plan/entry-review.md` 持久化审阅包并运行 `node scripts/verify-plan-spec-entry <state.yaml>`。检查默认 pending，缺项、过期或无真实回复即阻断；独立调研可继续。
+Plan → Spec（含正式草稿、恢复与显式 `to-spec`）写入前，按 `.template-spec/plan/entry-review.md` 持久化审阅包并运行 `node scripts/verify-plan-spec-entry <state.yaml>`。检查默认 pending，缺项、过期或无真实回复即阻断；独立调研可继续。
 
 ## 结果与暂停
 
-咨询直接回答；工作单元保留完整结果，对外仅展示当前决定所需信息。
+咨询直接回答；工作单元完整留证，对外展示当前决定。
 
 工作单元结果至少包含：模式、仓库身份、当前阶段和工作单元、影响面、资产与门禁状态、证据、新鲜度、Ticket/垂直切片/合同状态、`ready-for-agent` 结论、阻塞项、本轮动作、下一工作单元、暂停或继续理由、Ticket 同步和 Git checkpoint 判断。
 
 暂停会签时追加门禁 ID、`role_id`、`runtime_id`、会签文件路径、推荐答案和恢复动作；恢复前运行适用验证器。只有同一候选快照通过全部适用审查轴与 fresh verification，才能提出合并、发布或完成结论；发布仍须生物人决定。
 
-专项合同加载索引见 `references/orchestration.md`。
+Plan / Spec / Design 追踪按 `.template-spec/process/stage-tracking.md`。
 
-Plan / Spec / Design 追踪按 `docs/process/stage-tracking.md`。
+需求澄清读 [对账](references/plan-requirements.md)；外部输入读 [问卷](references/external-input-questionnaire.md)。

package/template/.cursor/skills/yss-product-lifecycle/references/external-input-questionnaire.md

@@ -0,0 +1,19 @@
+# 外部输入问卷
+
+当前工作单元在信息掌握于他人时使用本合同。复用已知接收人和目的，仅询问影响问卷的缺口；草稿不授权对外发送。
+
+明确接收人的角色、专业背景、与提问者关系，以及需要取回的具体事实或决定。围绕信息缺口起草问卷，重要问题优先，一个问题只问一件事，每题留答案位置。超过少量问题时按主题分组，说明答案用于哪个决定。允许部分回答和“不知道”，不把沉默视为批准。
+
+## 问卷模板
+
+在获准的当前阶段资产目录保存 `external-input-<slug>.md`：
+
+- 标题、目的、发起人、接收人、答案用途。
+- 一段必要背景，避免假定对方读过当前对话。
+- 截止时间、预计耗时与不确定答案的标注方式。
+- 分主题的问题、必要时一句原因、每题答案位置。
+- 最后一个补充问题：还有哪些影响决定的信息未被覆盖？
+
+## 暂停与恢复
+
+未收到答案时保持 `pause.reason_code: external-input-required`，保存 `questionnaire_ref`、`recipient_role`、`requested_outputs` 和 `resume_route`。答案回流后保存 `response_ref`、`reclassified_impact`、`updated_authoritative_asset`，重算 stale、门禁与 frontier，再由编排器恢复原工作单元或合法的 Spec 入口。收到回复不等于自动批准；原门禁与真实用户决定规则仍适用。

package/template/.cursor/skills/yss-product-lifecycle/references/matt-yss-adapter.md

@@ -7,7 +7,7 @@ Matt skills 决定如何工作；YSS 生命周期决定是否允许推进；YSS
 ## 入口与仓库身份裁决
 
 - 所有入口先读取 `yss-project.yaml`。缺失、解析失败、schema 不支持或 `repository_mode` 非法时，停止路由并进入 migration-check。
-- **直接调用生命周期管理的 Matt user-invoked skill**（`setup-matt-pocock-skills`、`grill-with-docs`、`to-spec`、`to-tickets`、`implement`）时，用户仍是正式资产的创建者；生命周期先校验前置条件，再接受结果并重新计算阶段、门禁和状态。其他 user-invoked skill 同样不得由生命周期自动调用；只有在其专属适配合同存在时才进入 YSS 流程。
+- **直接调用生命周期管理的 Matt user-invoked skill**（`setup-matt-pocock-skills`、`to-spec`、`to-tickets`、`implement`）时，用户仍是正式资产的创建者；生命周期先校验前置条件，再接受结果并重新计算阶段、门禁和状态。其他 user-invoked skill 同样不得由生命周期自动调用；只有在其专属适配合同存在时才进入 YSS 流程。
 - **直接调用 `yss-product-lifecycle`** 时，不机械嵌套调用任何 Matt user-invoked skill；编排器直接使用原生工作单元和允许的 model-invoked 原语。Matt user-invoked skill 保持显式兼容入口，生命周期负责准备、校验并验收其结果。
 - `template-source` 只允许进入模板维护流程。命中 `to-spec`、`to-tickets`、`implement`、Release 或 Retrospective 时返回 `blocked`，原因是 `template-source-product-artifact-forbidden`；`setup-matt-pocock-skills` 不得为具体产品生成 Spec、prototype、OpenAPI 或垂直切片 Ticket。
 - `project-instance` 才允许进入产品 Plan → Spec → 设计 → 契约 → Ticket → 实现 → Release / Retrospective 链路。
@@ -15,11 +15,11 @@ Matt skills 决定如何工作；YSS 生命周期决定是否允许推进；YSS
 | 情形 | Matt flow | 生命周期验收 |
 |---|---|---|
 | 首次启用或配置缺失 | `setup-matt-pocock-skills`（用户显式） | `needs-human`，说明缺失项；用户完成 setup 后重新计算 readiness |
-| 需求澄清 | `grill-with-docs`（用户显式）或 `grilling`、`domain-modeling`（生命周期原语） | 按退出判定检查未决项和回流 |
-| 信息在其他人手中 | `to-questionnaire` | 使用 `external-input-required` 暂停；答案回流后记录 response、重新分类影响面，再进入 `grill-with-docs` 或 `to-spec` |
+| 需求澄清 | 原生 `work-unit.plan-requirements`，按需使用 `grilling`、`domain-modeling`（生命周期原语） | 按退出判定检查未决项和回流 |
+| 信息在其他人手中 | 生命周期外部输入问卷 | 使用 `external-input-required` 暂停；答案回流后记录 response、重新分类影响面，再进入 `work-unit.plan-requirements` 或 `to-spec` |
 | 大型模糊工作 | `wayfinder`（可选） | 仅在跨会话 / 跨 Agent 或 frontier 不清晰时启用；map 真正完成后 `handoff → to-spec` |
 | 技术或战略事实 | `yss-research`（`research` 为 deprecated alias） | `technical-evidence` 核验一手技术资料；`strategy-evidence` 为领域战略和阶段决策提供可审计证据；研究包不得自行修改或批准下游资产 |
-| runnable 问题 | `prototype` | 生成单文件可分享 HTML，保留 `prototype/<name>` 分支作为主来源；必须 source/return handoff 和结论回填，只能作为阶段 4 输入，不得替代低保真评审、H1/H2 档位路由、schema v3 验证和用户确认 |
+| runnable 问题 | `prototype` | 生成单文件可分享 HTML，保留 `prototype/<name>` 分支作为主来源；必须 source/return handoff 和结论回填，只能作为阶段 4 输入，不得替代低保真评审、H1/H2 档位路由、schema v4 验证和用户确认 |
 | Spec 综合 | 原生 `work-unit.spec-synthesis`；`to-spec`（用户显式兼容） | 初稿进入 `ready-for-human`，不得直接实现 |
 | 切片 | 原生 `work-unit.ticket-decomposition`；`to-tickets`（用户显式兼容） | 仅在冻结/无影响记录后拆垂直切片，初始 Ticket 状态为 `ready-for-human` |
 | 实现 | 原生 `work-unit.slice-implementation`；`implement`（用户显式兼容） | 当前合同批准并持久化后执行；内部使用 `tdd`，结果回交后再次核验 |
@@ -27,7 +27,7 @@ Matt skills 决定如何工作；YSS 生命周期决定是否允许推进；YSS
 | 审查 | `code-review` | 唯一默认代码审查入口；审查者独立且不得写实现；Standards 消费 Spec、仓库治理规则、Slice `required_skills` 和 YSS / Alibaba 专项检查输入；finding 按合同分流修复或 stale 回 实现合同编译器 |
 | 跨上下文 | `handoff` | 保存来源、阶段、未决项、命令和下一责任人 |
 | 阶段边界 | 生命周期 phase-boundary 合同 | 按 `Continue → /clear → /handoff → subagent → /compact` 选择上下文动作；只记录证据，不扩展生命周期状态 |
-| 解释未落地 | `wait-what` | 只重新解释当前结论，不改变阶段、门禁、Ticket 或 `ready-for-agent` |
+| 解释未落地 | 普通对话与文档写作规范 | 只重新解释当前结论，不改变阶段、门禁、Ticket 或 `ready-for-agent` |
 | 人工步骤 | 人工 checkpoint | 记录 Agent 无法替代的点击、审批、凭据和迁移步骤；秘密值必须隐藏并脱敏 |
 | 编写 Agent 文档 | `writing-for-agents`；维护 skill 时使用 `maintaining-skills` | 共享 skill 只改 `.agents/skills`；流程文档保持简体中文 |
 
@@ -48,7 +48,7 @@ workflow_reference:
   invocation_mode: reference
 result: completed # completed / blocked / needs-human / failed
 evidence_refs:
-  - docs/process/yss-product-lifecycle-orchestrator-validation.md
+  - .template-spec/process/yss-product-lifecycle-orchestrator-validation.md
 changed_artifacts: []
 new_impacts: []
 stale_candidates: []
@@ -66,7 +66,7 @@ blocking_signals: []
 
 | Matt flow | 进入条件 | 生命周期结果 |
 |---|---|---|
-| `to-spec`（用户显式） | Plan work unit 或 `grill-with-docs` 已满足退出条件，且不存在未回流 runnable blocker；用户问题、MVP/非目标、成功标准、测试 seam 和术语审查均有证据 | 生命周期只准备/验收；Spec 初稿为 `ready-for-human`，不等于批准 |
+| `to-spec`（用户显式） | Plan work unit 或 `work-unit.plan-requirements` 已满足退出条件，且不存在未回流 runnable blocker；用户问题、MVP/非目标、成功标准、测试 seam 和术语审查均有证据 | 生命周期只准备/验收；Spec 初稿为 `ready-for-human`，不等于批准 |
 | `to-tickets`（用户显式） | OpenAPI Freeze 或 `no-api-impact` 记录、必要门禁、垂直切片范围和阻塞边均已明确 | 生命周期只准备/验收；只能生成垂直切片 Ticket，初始统一为 `ready-for-human`；必须留下 `ticket_decomposition_result_ref` 和 `vertical_slice_ticket_ref` |
 | `implement`（用户显式） | `ready-for-agent` 公式、Ticket 正式化结果、垂直切片引用/类型/状态、Contract 已批准/持久化/版本一致、Build Architecture Checklist、实现仓库/分支/CI/验证命令/回滚点，以及后端 Contract（适用时）均满足 | 生命周期只准备/验收；单会话实现同样适用，不得绕过门禁；父 Ticket、`ready-for-human` 切片或跳过 Ticket 正式化的 `next_route` 必须 `blocked` |
 
@@ -74,7 +74,7 @@ blocking_signals: []
 
 ## Review 候选与 Git 授权
 
-YSS 调用 `code-review` 前必须形成 review input，至少包含 `review_mode`、`review_base_ref`、`implementation_candidate_ref`、`candidate_snapshot_ref`、`candidate_digest`、`spec_ref`、`ticket_ref`、`slice_contract_ref`、`build_architecture_checklist_ref` 和 `yss_execution_result_refs`，并满足 `orchestration-contract.yaml.review_input.manifest_required_by_mode`。Standards 还必须编译 `review_standards_route`：合同 `required_skills`、影响面专项检查输入、报告模板与 `finding_disposition`；机器检查按 `run_if_present` 执行。质量标准只从 `engineering-baseline` 引用，禁止在 review input 或切片中另起一份。命中高风险影响时，review input 还要引用 Doubt-Driven 主张 / 反证记录；缺少反证或残余风险未处理时返回 `blocked`。`committed` 审查 merge-base 到不可变 `HEAD`；`worktree` 一次捕获 merge-base 到 working tree 的 committed、staged、unstaged 和 untracked 内容，使用 `yss-worktree-candidate-v1` 规定的 raw path、uint64 big-endian 长度、tracked/untracked record 和不支持条目阻断规则计算 SHA-256，让两个 Reviewer 消费同一不可变快照，并在返回和完成 checkpoint 复核摘要未变化。缺少输入、候选为空、专项覆盖缺失、未关闭 mandatory `violation`、适用行空白或摘要变化时返回 `blocked`，不能缩小审查范围、另起通用审查 skill、由审查者改实现，或合并不同候选的结论。`violation` 类 finding 交实现者在原合同路径修复后全轴复审；`drift` / `new_impacts` 使合同 `stale` 并回 实现合同编译器。
+YSS 调用 `code-review` 前必须形成 review input，至少包含 `review_mode`、`review_base_ref`、`implementation_candidate_ref`、`candidate_snapshot_ref`、`candidate_digest`、`spec_ref`、`ticket_ref`、`slice_contract_ref`、`build_architecture_checklist_ref` 和 `yss_execution_result_refs`，并满足 `orchestration-contract.yaml.review_input.manifest_required_by_mode`。Standards 还必须编译 `review_standards_route`：合同 `required_skills`、影响面专项检查输入、报告模板与 `finding_disposition`；机器检查按 `run_if_present` 执行。质量标准只从 `engineering-baseline` 引用，禁止在 review input 或切片中另起一份。命中高风险影响时，review input 还要引用 Doubt-Driven 主张 / 反证记录；缺少反证或残余风险未处理时返回 `blocked`。`committed` 审查 merge-base 到不可变 `HEAD`；`worktree` 一次捕获 merge-base 到 working tree 的 committed、staged、unstaged 和 untracked 内容，使用 `yss-worktree-candidate-v1` 规定的 raw path、uint64 big-endian 长度、tracked/untracked record 和不支持条目阻断规则计算 SHA-256，让所有参与审查者（人数按 `orchestration-contract.yaml.gate_consolidation`） 消费同一不可变快照，并在返回和完成 checkpoint 复核摘要未变化。缺少输入、候选为空、专项覆盖缺失、未关闭 mandatory `violation`、适用行空白或摘要变化时返回 `blocked`，不能缩小审查范围、另起通用审查 skill、由审查者改实现，或合并不同候选的结论。`violation` 类 finding 交实现者在原合同路径修复后全轴复审；`drift` / `new_impacts` 使合同 `stale` 并回 实现合同编译器。
 
 Matt `implement` 的通用提交指令不构成 YSS Git 授权。只有用户明确给出 `commit_authorized` 为 `true`、非空 `commit_scope` 和 `commit_authorization_ref` 时才能 commit；只有明确给出 `push_authorized` 为 `true`、非空 `push_scope` 和 `push_authorization_ref` 时才能 push。缺少任一字段时保持工作区不变，只输出 checkpoint 判断；不得把 `orchestrate`、实现授权、当前分支、测试通过或负责人要求解释为隐含授权。`git-submodule` 还必须按仓授权、禁止 detached HEAD 提交，并先推子仓再更新父仓 gitlink。
 
@@ -92,11 +92,11 @@ Matt `implement` 的通用提交指令不构成 YSS Git 授权。只有用户明
 
 当 YSS 生命周期处于 active 状态时，Matt `to-spec` 中独立运行时的 `ready-for-agent` 发布提示由本适配层覆盖为 `ready-for-human`：Spec 必须先经过产品总体设计 / 功能架构、必要的设计与契约门禁，之后才由生命周期编排器决定垂直切片 Ticket 的 `ready-for-agent`。这只约束 YSS 编排下的状态写入，不修改 Matt skill 单独运行时的核心行为。
 
-`setup-matt-pocock-skills` 仅由用户显式启动。readiness=`missing` 时返回 `needs-human`、`requested_skill=setup-matt-pocock-skills` 和 `resume_route=setup-readiness`；仅发现旧路径资产仍进入 migration-check 并暂停写入。`ready` 直接继续，`conflict` 进入迁移裁决，`degraded` 保留待发布草案，`not-applicable` 仅验证模板契约。通用 setup 文案与 YSS tracker 合同冲突时，以 `docs/agents/issue-tracker.md` 和本编排契约为准。
+`setup-matt-pocock-skills` 仅由用户显式启动。readiness=`missing` 时返回 `needs-human`、`requested_skill=setup-matt-pocock-skills` 和 `resume_route=setup-readiness`；仅发现旧路径资产仍进入 migration-check 并暂停写入。`ready` 直接继续，`conflict` 进入迁移裁决，`degraded` 保留待发布草案，`not-applicable` 仅验证模板契约。通用 setup 文案与 YSS tracker 合同冲突时，以 `.template-spec/agents/issue-tracker.md` 和本编排契约为准。
 
 ### Local Markdown 兼容映射
 
-当 `docs/agents/issue-tracker.md` 的 `platform` 为 `local-markdown` 时，Matt flow 的本地输出归一化为以下 YSS 载体：
+当 `.template-spec/agents/issue-tracker.md` 的 `platform` 为 `local-markdown` 时，Matt flow 的本地输出归一化为以下 YSS 载体：
 
 | Matt 产物 | Local 载体 |
 |---|---|

package/template/.cursor/skills/yss-product-lifecycle/references/orchestration-contract.yaml

@@ -4,21 +4,21 @@ document_writing:
   condition: lifecycle-document-output
   scope: current-document-work-only
   dispatch: pass-condition-and-reference-to-document-owner
-  reference: docs/process/document-writing.md
-  examples: docs/templates/examples/lifecycle-writing-examples.md
+  reference: .template-spec/process/document-writing.md
+  examples: .template-spec/templates/examples/lifecycle-writing-examples.md
   load_when: [lifecycle-document-draft, lifecycle-document-revision, progress-or-decision-presentation]
   dispatch_input: include-reference-for-document-work
   artifact_ownership: unchanged
   gate_and_status_semantics: unchanged
 
 backend_architecture_identity_policy:
-  source: docs/agents/yss-skill-registry.yaml
+  source: .template-spec/agents/yss-skill-registry.yaml
   generated_profiles: architecture_profiles
   existing_profiles: existing_project_profiles
   existing_evidence: [repository-registration, engineering-baseline, existing-project-observation]
   evidence_policy: original-ref-digest-and-current-source-verification
   delivery_preflight: scripts/preflight-delivery
-  schema: docs/process/schemas/backend-architecture-identity.schema.json
+  schema: .template-spec/process/schemas/backend-architecture-identity.schema.json
   required_surfaces: [engineering-baseline, repository-registration, scaffold-manifest, slice-contract, work-unit, execution-result]
   agreement: exact-identity-and-digest
   missing_or_drift: blocked-and-recompile
@@ -89,6 +89,7 @@ request_triage:
     explicit_audit: audit
     authorized_continuation: resume
     clear_action_request: orchestrate
+    clear_read_only_investigation_request: orchestrate
     unresolved_intent: route
     investigation: read-only-actions-unless-additional-scope-authorized
     mode_keywords_required: false
@@ -138,9 +139,19 @@ execution_efficiency:
     template_regression_suite: template-maintenance-or-explicit-regression-task
     per_work_unit_context_reconciliation: required
     skip_triggered_gates: forbidden
+  recovery:
+    state_source: current-checkpoint-stage-tracking-and-readable-task-results
+    status_view: read-only-diagnostics-never-execution-authorization
+    running_or_unknown_task: inspect-existing-task-identity-before-dispatch
+    completed_task: verify-current-evidence-then-recompute-frontier
+    action_completed_before_checkpoint: reconcile-actual-artifacts-before-repeating-side-effects
+    changed_inputs: invalidate-affected-dependencies-and-revalidate
+    missing_legacy_tracking: existing-compatibility-or-explicit-migration
+    unknown_external_result: stop-duplicate-side-effect-and-report-missing-evidence
+    approval: revalidate-current-decision-or-supported-continuation
   interaction:
     questions: batch-independent-current-stage-questions
-    user_decision_policy_ref: docs/agents/digital-human-roles.yaml#user_decision_policy
+    user_decision_policy_ref: .template-spec/agents/digital-human-roles.yaml#user_decision_policy
     decision_evidence_ref: references/user-decisions.md
     dependent_future_approvals: forbidden
     checkpoint_policy_ref: checkpoint_policy
@@ -157,7 +168,7 @@ entry_routing:
   invalid_manifest:
     action: migration-check
   formal_user_entry:
-    skills: [setup-matt-pocock-skills, grill-with-docs, to-spec, to-tickets, implement]
+    skills: [setup-matt-pocock-skills, to-spec, to-tickets, implement]
     action: lifecycle-validate-and-accept
     lifecycle_artifact_write: conditional-explicit-user-entry
     return_to_orchestrator: required
@@ -208,7 +219,7 @@ workflow_execution_result:
   evidence_ref_validation: readable-or-resolvable
   completed_requires_no_blocking_signals: true
   context_reconciliation:
-    schema_ref: docs/process/schemas/context-reconciliation.schema.json
+    schema_ref: .template-spec/process/schemas/context-reconciliation.schema.json
     validator: scripts/verify-context-reconciliation
     project-instance: {required_status: reconciled, readable_ref_required: true, transition_without_reconciliation: blocked}
     template-source: {required_status: not-applicable, reason_required: true}
@@ -233,8 +244,8 @@ workflow_execution_result:
 task_package:
   schema_version: 1
   applies_to: all-formal-digital-human-dispatches
-  schema_ref: docs/process/schemas/digital-human-task-package.schema.json
-  compatibility_schema_ref: docs/process/schemas/subagent-task-package.schema.json
+  schema_ref: .template-spec/process/schemas/digital-human-task-package.schema.json
+  compatibility_schema_ref: .template-spec/process/schemas/subagent-task-package.schema.json
   validator: scripts/verify-digital-human-task-package
   compatibility_validator: scripts/verify-subagent-task-package
   persistence_layout: docs/.scratch/<feature>/task-packages/<task-id>.yaml
@@ -242,7 +253,7 @@ task_package:
   execution_states: [Explorer, Drafter, Worker, Reviewer, Verifier]
   workflow_statuses: [not-started, active, paused, resolved, failed]
   skill_source:
-    registry_ref: docs/agents/digital-human-roles.yaml
+    registry_ref: .template-spec/agents/digital-human-roles.yaml
     defaults: taskPackageDefaults(role_id)
     copy_required: [core_skills, forbidden_skills]
   contract:
@@ -286,8 +297,8 @@ task_package:
 # may prepare, validate and accept their results, but cannot invoke them or create
 # their formal artifacts on their behalf.
 matt_invocation_boundary:
-  user_invoked_skills: [grill-with-docs, handoff, implement, improve-codebase-architecture, setup-matt-pocock-skills, to-questionnaire, to-spec, to-tickets, triage, wait-what, wayfinder]
-  lifecycle_managed_user_entries: [setup-matt-pocock-skills, grill-with-docs, to-spec, to-tickets, implement]
+  user_invoked_skills: [handoff, implement, setup-matt-pocock-skills, to-spec, to-tickets, triage, wayfinder]
+  lifecycle_managed_user_entries: [setup-matt-pocock-skills, to-spec, to-tickets, implement]
   model_invoked_skills: [code-review, codebase-design, diagnosing-bugs, domain-modeling, grilling, prototype, resolving-merge-conflicts, tdd, writing-for-agents, yss-research]
   lifecycle_allowed_model_invoked_skills: [code-review, codebase-design, diagnosing-bugs, domain-modeling, grilling, prototype, tdd, yss-research]
   lifecycle_may_invoke_user_invoked: false
@@ -305,13 +316,25 @@ skill_source_contract:
 lifecycle_native_entries:
   default_entry: yss-product-lifecycle
   formal_artifact_owner: yss-product-lifecycle
-  user_confirmation_policy_ref: docs/agents/digital-human-roles.yaml#user_decision_policy
+  user_confirmation_policy_ref: .template-spec/agents/digital-human-roles.yaml#user_decision_policy
   compatibility_entries:
     to-spec: lifecycle-validate-and-accept
     to-tickets: lifecycle-validate-and-accept
     implement: lifecycle-validate-and-accept
 
 work_unit_routes:
+  work-unit.maintenance-research:
+    native: {source: yss-product-lifecycle, skill: yss-research, invocation_mode: model-invoked}
+    primary_skill: yss-research
+    supporting_skills: []
+    skills: [yss-research]
+    applies_when: template_source_persisted_research
+    not_applicable_reason: project_instance_or_no_persisted_research
+    repository_mode: template-source
+    completion_validator: scripts/verify-maintenance-research
+    terminal_allowed: true
+    next_routes: [work-unit.ssot-update]
+    continuation_requires: bound_user_maintenance_authorization
   work-unit.plan-opportunity:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-product-lifecycle
@@ -354,7 +377,7 @@ work_unit_routes:
     human_gate: spec-baseline
     applies_when: new_feature_or_behavior_change
     not_applicable_reason: existing_frozen_spec_is_current
-  work-unit.prototype-design:
+  work-unit.prototype-design-v2:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-prototype-stage
     supporting_skills: [prototype-review, yss-design-system, product-design:index]
@@ -362,7 +385,7 @@ work_unit_routes:
     execution_order: [yss-design-system, low-fidelity-assets, prototype-review, prototype-profile-routing, profile-adapter-build, browser-design-qa-accessibility, user-confirmation]
     profile_routing_ref: .agents/skills/yss-prototype-stage/references/prototype-profile-routing.md
     prototype_adapter_ref: .agents/skills/yss-prototype-stage/references/product-design-adapter.md
-    evidence_schema_version: 3
+    evidence_schema_version: 4
     profile_contract:
       default_when_uncertain: H2
       highest_matching_profile_wins: true
@@ -388,7 +411,7 @@ work_unit_routes:
         applies_when: new_backend_repository
         confirms: [architecture_family, exact_spring_boot_version]
         architecture_choices: [domain-driven, layered-mvc]
-        platform_source: docs/engineering/backend-platforms.json
+        platform_source: .template-spec/engineering/backend-platforms.json
         existing_repository: not-applicable-reuse-current-registration
         missing_or_stale: blocked
       branches:
@@ -438,6 +461,16 @@ work_unit_routes:
     result_schema_version: 2
     backend_design_prerequisites_required: [technical_design, data_architecture_decision, api_contract_decision, engineering_contract_approval_ref]
     must_complete_before: work-unit.ticket-decomposition
+  work-unit.service-project-initialization:
+    native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
+    primary_skill: yss-layered-mvc-scaffold-generator
+    supporting_skills: []
+    skills: [yss-layered-mvc-scaffold-generator]
+    parent_work_unit: work-unit.implementation-repository-preparation
+    return_to: work-unit.implementation-repository-preparation
+    applies_when: new_backend_project_with_approved_current_v4_mvc-data-analysis-v1_contract
+    completion_evidence: [scaffold-manifest-v4, scaffold-verification, workflow-execution-result, context-handoff-digest]
+    not_applicable_reason: existing_project_or_other_architecture_profile
   work-unit.ticket-decomposition:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-product-lifecycle
@@ -498,7 +531,7 @@ work_unit_routes:
     review_standards_route:
       unique_default_skill: code-review
       second_generic_review_skill: forbidden
-      report_template: docs/templates/review-report-template.md
+      report_template: .template-spec/templates/review-report-template.md
       contract_required_skills: required
       write_implementation: forbidden
       machine_checks:
@@ -621,21 +654,22 @@ transition_graph:
   validator: scripts/lib/lifecycle-transition.mjs
   implementation_requires_predecessor: work-unit.ticket-decomposition
   routes:
-    work-unit.ssot-update: [work-unit.skill-projection-sync, work-unit.intensity-aware-verification]
-    work-unit.skill-projection-sync: [work-unit.template-snapshot-build, work-unit.intensity-aware-verification]
-    work-unit.template-snapshot-build: [work-unit.attach-sync-integration, work-unit.intensity-aware-verification]
-    work-unit.attach-sync-integration: [work-unit.intensity-aware-verification]
-    work-unit.intensity-aware-verification: [work-unit.intensity-aware-review]
-    work-unit.intensity-aware-review: [work-unit.release-and-rollback]
+    work-unit.ssot-update: [work-unit.skill-projection-sync, work-unit.intensity-aware-verification-v2]
+    work-unit.skill-projection-sync: [work-unit.template-snapshot-build, work-unit.intensity-aware-verification-v2]
+    work-unit.template-snapshot-build: [work-unit.attach-sync-integration, work-unit.intensity-aware-verification-v2]
+    work-unit.attach-sync-integration: [work-unit.intensity-aware-verification-v2]
+    work-unit.intensity-aware-verification-v2: [work-unit.intensity-aware-review-v2]
+    work-unit.intensity-aware-review-v2: [work-unit.release-and-rollback]
     work-unit.release-and-rollback: []
     work-unit.plan-opportunity: [work-unit.plan-requirements, work-unit.domain-strategy-design, work-unit.stage-decision, work-unit.spec-synthesis]
     work-unit.plan-requirements: [work-unit.domain-strategy-design, work-unit.stage-decision, work-unit.spec-synthesis]
     work-unit.domain-strategy-design: [work-unit.stage-decision, work-unit.spec-synthesis]
     work-unit.stage-decision: [work-unit.spec-synthesis]
-    work-unit.spec-synthesis: [work-unit.prototype-design, work-unit.technical-analysis]
-    work-unit.prototype-design: [work-unit.technical-analysis]
+    work-unit.spec-synthesis: [work-unit.prototype-design-v2, work-unit.technical-analysis]
+    work-unit.prototype-design-v2: [work-unit.technical-analysis]
     work-unit.technical-analysis: [work-unit.implementation-repository-preparation]
-    work-unit.implementation-repository-preparation: [work-unit.ticket-decomposition]
+    work-unit.implementation-repository-preparation: [work-unit.service-project-initialization, work-unit.ticket-decomposition]
+    work-unit.service-project-initialization: [work-unit.implementation-repository-preparation]
     work-unit.ticket-decomposition: [work-unit.slice-implementation]
     work-unit.slice-implementation: [work-unit.frontend-implementation-verification, work-unit.code-review]
     work-unit.frontend-implementation-verification: [work-unit.code-review]
@@ -644,23 +678,23 @@ transition_graph:
     work-unit.release-and-retrospective: []
   forbidden_shortcuts:
     - {from: work-unit.spec-synthesis, to: work-unit.implementation-repository-preparation}
-    - {from: work-unit.prototype-design, to: work-unit.implementation-repository-preparation}
+    - {from: work-unit.prototype-design-v2, to: work-unit.implementation-repository-preparation}
     - {from: work-unit.spec-synthesis, to: work-unit.slice-implementation}
-    - {from: work-unit.prototype-design, to: work-unit.slice-implementation}
+    - {from: work-unit.prototype-design-v2, to: work-unit.slice-implementation}
     - {from: work-unit.technical-analysis, to: work-unit.slice-implementation}
     - {from: work-unit.technical-analysis, to: work-unit.ticket-decomposition}
 
 planning:
   entry_validator: scripts/verify-plan-spec-entry
-  review_contract: docs/plan/entry-review.md
-  check_policy: docs/process/lifecycle-registry.yaml
+  review_contract: .template-spec/plan/entry-review.md
+  check_policy: .template-spec/process/lifecycle-registry.yaml
   default_check_status: pending
   formal_spec_draft_requires_passed_entry: true
   stage: stage.plan
   record: artifact.plan-record
-  template: docs/plan/templates/plan-template.md
-  exit_policy: docs/process/lifecycle-registry.yaml
-  migration_policy: docs/process/plan-migration.md
+  template: .template-spec/plan/templates/plan-template.md
+  exit_policy: .template-spec/process/lifecycle-registry.yaml
+  migration_policy: .template-spec/process/plan-migration.md
   critical_open_questions: block-before-spec
   deferred_details_require: [noncritical_reason, owner, resolution_point, downstream_recipient]
   reuse_requires: [source_ref, current_version, applicable_scope, reason]
@@ -805,7 +839,7 @@ scaffold_architecture_decision:
       display_name: MVC 开发脚手架
       recommendation_signals: [crud, reporting-query, data-transformation, external-system-orchestration, thin-domain]
   platform_choice:
-    source: docs/engineering/backend-platforms.json
+    source: .template-spec/engineering/backend-platforms.json
     confirms: [platform_profile, spring_boot_version, java_version]
     version_format: exact-patch
     latest_or_range: forbidden
@@ -855,7 +889,7 @@ backend_scaffold:
   contract_schema:
     schema_version: 4
     current_schema_version: 4
-    schema_ref: docs/process/schemas/project-scaffold-contract.schema.json
+    schema_ref: .template-spec/process/schemas/project-scaffold-contract.schema.json
     compatible_backend_versions: [3, 4]
     frontend_minimum_version: 4
     identity: service-engineering-baseline
@@ -878,9 +912,9 @@ backend_scaffold:
       component_version_policy: per-artifact-from-verified-component-capabilities
     profiles:
       discriminant: architecture_family
-      source: docs/engineering/backend-platforms.json
+      source: .template-spec/engineering/backend-platforms.json
       platform_binding: platform_configuration-v2
-      architecture_profiles_source: docs/agents/yss-skill-registry.yaml
+      architecture_profiles_source: .template-spec/agents/yss-skill-registry.yaml
       unsupported: [old-architecture-profile, arbitrary-module-combination, unverified-platform-or-component-capability]
     module_profile:
       required: [requested_capabilities, resolved_modules, resolution_version]
@@ -1009,7 +1043,11 @@ wayfinder_mode:
   template_source_use: only-when-template-evolution-is-long-running
 
 context_engineering:
-  contract_field: slice_contract.common.context_plan
+  contract_field: slice_contract.common.context_plan # 仅运行时归一化读取别名
+  raw_v2_contract_field: slice_contract.common.context_plan
+  raw_v3_contract_field: slice_contract.scope.context_plan
+  dispatch_reading: implementation-task-view-or-review-view
+  reading_reference: .template-spec/process/contract-reading.md
   required_context: [CONTEXT.md, approved-spec, current-slice-contract, applicable-adr-or-baseline]
   on_demand_context: [specialist-references, implementation-repository-files, historical-evidence]
   stop_rule: minimal-sufficient-evidence
@@ -1048,7 +1086,7 @@ frontend_implementation_plan:
   applies_when: [ui_impact]
   required_before: [ready_for_agent]
   required: [prototype_ref, spec_ref, visual_baseline, route_and_page_inventory, baseline_case_ids, desktop_viewport, narrow_viewport, state_cases, pnpm_commands]
-  schema: docs/process/schemas/frontend-implementation-evidence.schema.json
+  schema: .template-spec/process/schemas/frontend-implementation-evidence.schema.json
   validator: scripts/verify-frontend-implementation-evidence
   acceptance: [kind_plan, template_false, status_approved, no_template_placeholders, readable_baseline_refs, approved_visual_baseline_digest_current, selected_case_ids_exist]
 
@@ -1057,7 +1095,7 @@ frontend_implementation_verification:
   required_before: [release]
   required: [prototype_ref, spec_ref, visual_baseline, route_and_page_inventory, case_results, interaction_results, console_warning_check, pnpm_commands, actual_verification, uncovered_differences, difference_owner]
   verification: [actual_command, exit_code, executed_at, evidence_ref]
-  schema: docs/process/schemas/frontend-implementation-evidence.schema.json
+  schema: .template-spec/process/schemas/frontend-implementation-evidence.schema.json
   validator: scripts/verify-frontend-implementation-evidence
   acceptance: [kind_verification, template_false, status_approved, no_template_placeholders, visual_baseline_identity_and_digest_match, case_results_pair_every_selected_case, no_unexplained_difference, console_warning_pass, pnpm_exit_codes_zero, independent_review_approved]
   blocked_when: [unexplained_visual_difference, missing_visual_evidence, typecheck_only, claimed_alignment_without_evidence]
@@ -1182,8 +1220,8 @@ behavioral_invariants:
   diagnostics_redact_secrets: true
 
 user_decision_evidence:
-  policy_ref: docs/agents/digital-human-roles.yaml#user_decision_policy
-  schema_ref: docs/process/schemas/user-decision.schema.json
+  policy_ref: .template-spec/agents/digital-human-roles.yaml#user_decision_policy
+  schema_ref: .template-spec/process/schemas/user-decision.schema.json
   protocol_ref: references/user-decisions.md
   verifier: scripts/verify-user-decision
   workflow_result_fields: [user_decisions, user_decision_not_applicable]
@@ -1195,8 +1233,8 @@ user_decision_evidence:
   basis_changed: revalidate_then_continue_only_with_independent_equivalence_evidence
 
 gate_consolidation:
-  source: docs/process/lifecycle-registry.yaml
-  check_policy: docs/agents/digital-human-roles.yaml
+  source: .template-spec/process/lifecycle-registry.yaml
+  check_policy: .template-spec/agents/digital-human-roles.yaml
   checks: automatic_or_independent_review_without_separate_user_decision
   check_failure: blocks_aggregate_gate
   plan_decision_boundary: gate.plan-approved
@@ -1220,7 +1258,7 @@ execution_scopes:
     validator: scripts/lib/lifecycle-execution-scope.mjs
     terminal_work_unit: work-unit.backend-delivery
     terminal_record: .yss-backend-delivery.json
-    allowed_work_units: [work-unit.entry-triage, work-unit.plan-opportunity, work-unit.plan-requirements, work-unit.domain-strategy-design, work-unit.stage-decision, work-unit.spec-synthesis, work-unit.prototype-design, work-unit.technical-analysis, work-unit.implementation-repository-preparation, work-unit.scaffold-generation, work-unit.ticket-decomposition, work-unit.slice-implementation, work-unit.code-review, work-unit.backend-delivery]
+    allowed_work_units: [work-unit.entry-triage, work-unit.plan-opportunity, work-unit.plan-requirements, work-unit.domain-strategy-design, work-unit.stage-decision, work-unit.spec-synthesis, work-unit.prototype-design-v2, work-unit.technical-analysis, work-unit.implementation-repository-preparation, work-unit.service-project-initialization, work-unit.scaffold-generation, work-unit.ticket-decomposition, work-unit.slice-implementation, work-unit.code-review, work-unit.backend-delivery]
     route_overrides:
       work-unit.code-review: [work-unit.slice-implementation, work-unit.backend-delivery]
       work-unit.slice-implementation: [work-unit.code-review]
@@ -1251,8 +1289,8 @@ consumer_entry_routes:
       target_work_unit: work-unit.technical-design
 
 stage_tracking:
-  contract: docs/process/stage-tracking.md
-  schema: docs/process/schemas/stage-tracking.schema.json
+  contract: .template-spec/process/stage-tracking.md
+  schema: .template-spec/process/schemas/stage-tracking.schema.json
   verifier: scripts/stage-tracking
   configuration: tracker.lifecycle_tracking_version
   machine_state_owner: checkpoint.stage_tracking