coding-agent-harness 1.0.7 → 1.1.0

package/templates/ssot/Module-Registry.md

@@ -1,43 +1,9 @@
 # Module Registry
 
-## Purpose
-
-Track module ownership, write scope, branch or worktree assignment, and coordinator sync state for parallel agent work.
-
-## Status Legend
-
-| Status | Meaning | Required Next Step |
-| --- | --- | --- |
-| unassigned | Module exists but has no active owner. | Assign owner before work starts. |
-| reserved | Owner and scope are assigned. | Open worktree or begin planning. |
-| active | Module work is in progress. | Keep branch, plan, and blockers current. |
-| handoff | Worker has produced a reviewable result. | Coordinator reviews and integrates. |
-| merged | Module changes are integrated. | Link merge evidence and close residuals. |
-| blocked | Module cannot proceed. | Record blocker owner and unblock condition. |
-| archived | Module assignment is historical. | Keep archive pointer if needed. |
+Generated from `harness.yaml` `modules.items`. Do not edit this view directly.
 
 ## Active Modules
 
-| ID | Module | Path Scope | Owner | Status | Branch or Worktree | Task Plan | Shared Files | Depends On | Handoff Evidence | Residual | Updated |
-| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| M-000 | Module title | src/module/** or docs/area/** | owner | reserved | branch or worktree path | coding-agent-harness/planning/modules/<module>/tasks/.../task_plan.md | none | none | pending | none | YYYY-MM-DD |
-
-## Shared-File Register
-
-| File | Current Owner | Coordination Rule | Active Consumers | Last Sync |
-| --- | --- | --- | --- | --- |
-| path/to/shared-file | coordinator | only coordinator edits, workers propose patches | M-000, M-001 | YYYY-MM-DD |
-
-## Routing Rules
-
-1. Define module path scope before assigning a worker.
-2. Workers must not edit outside their assigned scope without coordinator approval.
-3. Shared files need an explicit owner and sync rule before parallel work starts.
-4. Move a module to `handoff` only when the worker provides evidence, residuals, and integration notes.
-5. The coordinator owns final merge, shared-file reconciliation, and Delivery SSoT updates.
-
-## Archive Rules
-
-- Keep active, blocked, and handoff rows visible until integration completes.
-- Archive merged module rows after the delivery or release closeout is stable.
-- Preserve branch, worktree, task plan, and handoff evidence in the archive row.
+| ID | Key | Title | Prefix | Branch | Current Step | Status | Owner | Scope | Shared | Depends On | Plan | Brief | Updated |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| none | none | none | none | none | none | planned | none | none | none | none | none | none | none |

package/templates/walkthrough/walkthrough-template.md

@@ -56,7 +56,7 @@ One sentence describing what changed and why it matters.
 
 | Artifact | Link |
 | --- | --- |
-| Task plan | coding-agent-harness/planning/tasks/.../task_plan.md |
+| Task plan | {{paths.harnessRoot}}/planning/tasks/.../task_plan.md |
 | Feature or Delivery SSoT | F-000 or D-000 |
 | Harness Ledger | HL-YYYY-MM-DD-001 |
 | Task-local closeout | walkthrough.md |

package/templates-zh-CN/AGENTS.md.template

@@ -1,7 +1,7 @@
 # [项目名称]
 
 这个文件是 Agent 进入本仓库时的工作入口。它只负责说明硬规则和阅读路由；
-详细规范放在 `coding-agent-harness/governance/standards/`，不要把操作手册全部塞进这里。
+详细规范放在 `{{paths.harnessRoot}}/governance/standards/`，不要把操作手册全部塞进这里。
 
 ## 项目概况
 
@@ -13,9 +13,9 @@
 
 ## 不可违反的规则
 
-1. 遵守 `coding-agent-harness/governance/standards/engineering-standard.md` 中的架构边界。
+1. 遵守 `{{paths.harnessRoot}}/governance/standards/engineering-standard.md` 中的架构边界。
 2. 不提交密钥、令牌、私有接口、用户隐私数据或生产凭据。
-3. 非平凡任务先用 Harness CLI 在 `coding-agent-harness/planning/tasks/` 下建立任务目录。
+3. 非平凡任务先用 Harness CLI 在 `{{paths.harnessRoot}}/planning/tasks/` 下建立任务目录。
 4. 声称完成前必须记录证据。
 5. 保护无关工作区改动，不回滚任务范围外文件。
 6. 已验证的、有意义的工作切片要主动提交。除非用户明确暂停提交、检查失败、dirty 归属不清，或安全边界导致无法形成干净提交，否则不要把已完成工作只留在未提交文件里；不能提交时，必须在 progress、handoff 或 closeout 中写明 no-commit reason、owner 和下一步。不要把无关 dirty 改动混入本任务提交。
@@ -27,23 +27,23 @@
 
 | 任务类型 | 先读文件 |
 | --- | --- |
-| 架构、核心模块、跨模块改动 | `coding-agent-harness/governance/standards/engineering-standard.md` |
-| 系统地图、服务职责、外部系统关系 | `coding-agent-harness/context/architecture/README.md`、`coding-agent-harness/context/architecture/service-catalog.md` |
-| 本地开发、mock、stub、跨仓调试 | `coding-agent-harness/context/development/README.md`、`coding-agent-harness/context/development/codebase-map.md` |
-| API、event、webhook、SDK、第三方契约 | `coding-agent-harness/context/integrations/README.md` 和相关契约文件 |
-| 测试、冒烟、回归 | `coding-agent-harness/governance/standards/testing-standard.md`、`coding-agent-harness/governance/regression/Regression-SSoT.md` |
-| 开发执行、提交、PR、发布 | `coding-agent-harness/governance/standards/execution-workflow-standard.md`、`coding-agent-harness/governance/standards/repo-governance-standard.md`、`coding-agent-harness/governance/standards/pull-request-standard.md`、`coding-agent-harness/governance/standards/ci-cd-standard.md` |
-| 创建或推进任务 | `coding-agent-harness/planning/tasks/` 下的当前任务目录；如果本项目已配置 Harness CLI，使用 `harness new-task` / lifecycle 命令 |
+| 架构、核心模块、跨模块改动 | `{{paths.harnessRoot}}/governance/standards/engineering-standard.md` |
+| 系统地图、服务职责、外部系统关系 | `{{paths.harnessRoot}}/context/architecture/README.md`、`{{paths.harnessRoot}}/context/architecture/service-catalog.md` |
+| 本地开发、mock、stub、跨仓调试 | `{{paths.harnessRoot}}/context/development/README.md`、`{{paths.harnessRoot}}/context/development/codebase-map.md` |
+| API、event、webhook、SDK、第三方契约 | `{{paths.harnessRoot}}/context/integrations/README.md` 和相关契约文件 |
+| 测试、冒烟、回归 | `{{paths.harnessRoot}}/governance/standards/testing-standard.md`、`{{paths.harnessRoot}}/governance/regression/Regression-SSoT.md` |
+| 开发执行、提交、PR、发布 | `{{paths.harnessRoot}}/governance/standards/execution-workflow-standard.md`、`{{paths.harnessRoot}}/governance/standards/repo-governance-standard.md`、`{{paths.harnessRoot}}/governance/standards/pull-request-standard.md`、`{{paths.harnessRoot}}/governance/standards/ci-cd-standard.md` |
+| 创建或推进任务 | `{{paths.harnessRoot}}/planning/tasks/` 下的当前任务目录；如果本项目已配置 Harness CLI，使用 `harness new-task` / lifecycle 命令 |
 | Brief、Execution Strategy、Visual Map | 当前任务的 `brief.md`、`execution_strategy.md`、`visual_map.md` |
 | 长程任务 | 当前任务的 `long-running-task-contract.md`（如存在） |
-| reviewer、subagent、对抗性审查 | 当前任务 `review.md`、`coding-agent-harness/governance/standards/review-routing-standard.md` |
-| 多人协作、多仓交付、阶段性交付 | `coding-agent-harness/governance/standards/delivery-operating-model-standard.md`、`coding-agent-harness/planning/Delivery-SSoT.md` |
-| 模块并行 | `coding-agent-harness/planning/modules/Module-Registry.md` 和相关 module plan |
-| 文档治理或 Harness 更新 | `coding-agent-harness/governance/standards/docs-library-standard.md`、`coding-agent-harness/harness.yaml` |
-| 外部资料摄取 | `coding-agent-harness/governance/standards/external-source-intake-standard.md` |
-| Regression SSoT 维护 | `coding-agent-harness/governance/standards/regression-ssot-governance.md` |
-| 收口、walkthrough、Lessons | `coding-agent-harness/governance/standards/walkthrough-standard.md`、当前任务 `walkthrough.md`、当前任务 `lesson_candidates.md`、`coding-agent-harness/governance/lessons/` |
-| Worktree、并行开发隔离 | `coding-agent-harness/governance/standards/worktree-standard.md` |
+| reviewer、subagent、对抗性审查 | 当前任务 `review.md`、`{{paths.harnessRoot}}/governance/standards/review-routing-standard.md` |
+| 多人协作、多仓交付、阶段性交付 | `{{paths.harnessRoot}}/governance/standards/delivery-operating-model-standard.md`、`{{paths.harnessRoot}}/planning/Delivery-SSoT.md` |
+| 模块并行 | `{{paths.harnessRoot}}/harness.yaml`、生成的 `{{paths.harnessRoot}}/planning/modules/Module-Registry.md`、模块 `brief.md` 和相关 `module_plan.md` |
+| 文档治理或 Harness 更新 | `{{paths.harnessRoot}}/governance/standards/docs-library-standard.md`、`{{paths.harnessRoot}}/harness.yaml` |
+| 外部资料摄取 | `{{paths.harnessRoot}}/governance/standards/external-source-intake-standard.md` |
+| Regression SSoT 维护 | `{{paths.harnessRoot}}/governance/standards/regression-ssot-governance.md` |
+| 收口、walkthrough、Lessons | `{{paths.harnessRoot}}/governance/standards/walkthrough-standard.md`、当前任务 `walkthrough.md`、当前任务 `lesson_candidates.md`、`{{paths.harnessRoot}}/governance/lessons/` |
+| Worktree、并行开发隔离 | `{{paths.harnessRoot}}/governance/standards/worktree-standard.md` |
 
 ## 标准执行流程
 
@@ -69,17 +69,19 @@
 - worker subagent 需要用户授权一次，并记录到 `execution_strategy.md`；之后只可在同一任务、同一范围、同一 worktree/branch 内复用。
 - 共享 ledger、registry 和 SSoT 默认由 coordinator 维护，除非明确登记锁。
 - worker 交接必须包含分支或 worktree、改动文件、检查、证据和残余风险。
+- 模块注册以 `{{paths.harnessRoot}}/harness.yaml` 的 `modules.items` 为准。`Module-Registry.md` 是生成视图，不要把它当作手写事实源。
+- 模块根目录默认只拥有 `brief.md` 和 `module_plan.md`。`execution_strategy.md`、`visual_map.md`、`review.md`、`walkthrough.md` 等执行合同属于具体任务目录，包括 `{{paths.harnessRoot}}/planning/modules/<key>/tasks/<task-id>/`。
 
 ## 单一事实源
 
-- Harness Ledger：`coding-agent-harness/governance/generated/Harness-Ledger.md`（任务生命周期总账，由 CLI 生成）
-- Delivery SSoT：`coding-agent-harness/planning/Delivery-SSoT.md`
-- Module Registry：`coding-agent-harness/planning/modules/Module-Registry.md`
-- Regression SSoT：`coding-agent-harness/governance/regression/Regression-SSoT.md`
-- Cadence Ledger：`coding-agent-harness/governance/regression/Cadence-Ledger.md`
+- Harness Ledger：`{{paths.harnessRoot}}/governance/generated/Harness-Ledger.md`（任务生命周期总账，由 CLI 生成）
+- Delivery SSoT：`{{paths.harnessRoot}}/planning/Delivery-SSoT.md`
+- Module Registry：`{{paths.harnessRoot}}/harness.yaml` 的 `modules.items`；生成视图在 `{{paths.harnessRoot}}/planning/modules/Module-Registry.md`
+- Regression SSoT：`{{paths.harnessRoot}}/governance/regression/Regression-SSoT.md`
+- Cadence Ledger：`{{paths.harnessRoot}}/governance/regression/Cadence-Ledger.md`
 - Lesson Candidates：当前任务 `lesson_candidates.md`
-- Lesson Detail Docs：`coding-agent-harness/governance/lessons/`
-- Generated Closeout Index：`coding-agent-harness/governance/generated/Closeout-Index.md`
+- Lesson Detail Docs：`{{paths.harnessRoot}}/governance/lessons/`
+- Generated Closeout Index：`{{paths.harnessRoot}}/governance/generated/Closeout-Index.md`
 
 ## 本地命令
 

package/templates-zh-CN/CLAUDE.md.template

@@ -6,7 +6,7 @@ Claude Code 开始任何任务前应当：
 
 1. 先读取 `AGENTS.md`。
 2. 按 `AGENTS.md` 的任务阅读矩阵选择当前任务需要的文件。
-3. 只加载必要的 `coding-agent-harness/governance/standards/` 标准文件和任务目录上下文。
+3. 只加载必要的 `{{paths.harnessRoot}}/governance/standards/` 标准文件和任务目录上下文。
 4. 把本文件视为 Claude Code 兼容入口，而不是第二份项目规范。
 
 不要在这里复制项目规则。长期有效的项目指令应维护在 `AGENTS.md` 及其引用文档中，避免两套规则逐渐漂移。

package/templates-zh-CN/architecture/README.md

@@ -24,8 +24,8 @@ Keep the English field names and file names because CLI checks rely on them.
 ## Boundary
 
 - 系统结构、服务责任、归属关系、关键流程放这里。
-- Payload、endpoint 参数、event schema、SDK 细节放 `coding-agent-harness/context/integrations/`。
-- 本地启动、mock、stub、跨仓调试经验放 `coding-agent-harness/context/development/`。
+- Payload、endpoint 参数、event schema、SDK 细节放 `{{paths.harnessRoot}}/context/integrations/`。
+- 本地启动、mock、stub、跨仓调试经验放 `{{paths.harnessRoot}}/context/development/`。
 
 ## Structure Contract
 

package/templates-zh-CN/architecture/service-catalog.md

@@ -12,6 +12,6 @@ Confidence: low
 
 ## Boundary Rule
 
-这个目录只放服务责任、接口摘要和跳转链接。Payload、auth、error code、event schema 放 `coding-agent-harness/context/integrations/`。
+这个目录只放服务责任、接口摘要和跳转链接。Payload、auth、error code、event schema 放 `{{paths.harnessRoot}}/context/integrations/`。
 
-一个服务或微服务只占一行。只要该服务影响本仓开发或判断，就补 `services/<service-key>.md`、`coding-agent-harness/context/development/external-context/<service-key>.md` 和相关 `coding-agent-harness/context/integrations/<contract>.md` 链接。
+一个服务或微服务只占一行。只要该服务影响本仓开发或判断，就补 `services/<service-key>.md`、`{{paths.harnessRoot}}/context/development/external-context/<service-key>.md` 和相关 `{{paths.harnessRoot}}/context/integrations/<contract>.md` 链接。

package/templates-zh-CN/architecture/services/service-template.md

@@ -9,7 +9,7 @@ Confidence: low
 
 | Catalog Row | Development Context | Source Pack | Integration Contracts | Last Verified | Confidence |
 | --- | --- | --- | --- | --- | --- |
-| `coding-agent-harness/context/architecture/service-catalog.md` | `coding-agent-harness/context/development/external-context/<service-key>.md` | `coding-agent-harness/context/development/external-source-packs/<source-key>/README.md` 或 N/A | `coding-agent-harness/context/integrations/<contract>.md` | unknown | low |
+| `{{paths.harnessRoot}}/context/architecture/service-catalog.md` | `{{paths.harnessRoot}}/context/development/external-context/<service-key>.md` | `{{paths.harnessRoot}}/context/development/external-source-packs/<source-key>/README.md` 或 N/A | `{{paths.harnessRoot}}/context/integrations/<contract>.md` | unknown | low |
 
 ## Responsibility
 

package/templates-zh-CN/development/README.md

@@ -14,8 +14,8 @@ Keep the English field names and section headings because CLI checks rely on the
 ## Boundary
 
 - 本地启动、代码地图、外部服务开发摘要、mock、stub、跨仓调试放这里。
-- 长期系统结构放 `coding-agent-harness/context/architecture/`。
-- API、event、webhook 等具体契约放 `coding-agent-harness/context/integrations/`。
+- 长期系统结构放 `{{paths.harnessRoot}}/context/architecture/`。
+- API、event、webhook 等具体契约放 `{{paths.harnessRoot}}/context/integrations/`。
 
 ## Structure Contract
 
@@ -32,21 +32,21 @@ Keep the English field names and section headings because CLI checks rely on the
 
 如果本仓依赖多个微服务，不要把所有外部知识写进一个大文档。只要某个外部服务会影响本仓开发或测试，就创建：
 
-- `coding-agent-harness/context/architecture/services/<service-key>.md`：该服务是什么、负责什么。
-- `coding-agent-harness/context/development/external-context/<service-key>.md`：本仓开发时如何 mock、stub、调试它。
-- `coding-agent-harness/context/integrations/<contract>.md`：具体 API/event/webhook 契约。
+- `{{paths.harnessRoot}}/context/architecture/services/<service-key>.md`：该服务是什么、负责什么。
+- `{{paths.harnessRoot}}/context/development/external-context/<service-key>.md`：本仓开发时如何 mock、stub、调试它。
+- `{{paths.harnessRoot}}/context/integrations/<contract>.md`：具体 API/event/webhook 契约。
 
 `context/development` 只放“开发时怎么处理这个外部服务”。不要在这里维护完整系统拓扑，也不要把 payload schema 塞进来。
 
 ## External Source Pack Rule
 
-如果外部团队给了多份文档、截图、导出包、会议纪要或链接，不要直接塞进 `context/{architecture,development,integrations}`。先读 `coding-agent-harness/governance/standards/external-source-intake-standard.md`，再决定是否创建 `external-source-packs/<source-key>/`。
+如果外部团队给了多份文档、截图、导出包、会议纪要或链接，不要直接塞进 `context/{architecture,development,integrations}`。先读 `{{paths.harnessRoot}}/governance/standards/external-source-intake-standard.md`，再决定是否创建 `external-source-packs/<source-key>/`。
 
 `external-source-packs/` 只负责资料索引、摘要和投影状态。稳定结论必须回写到：
 
-- `coding-agent-harness/context/architecture/services/<service-key>.md`
-- `coding-agent-harness/context/development/external-context/<service-key>.md`
-- `coding-agent-harness/context/integrations/<contract>.md`
+- `{{paths.harnessRoot}}/context/architecture/services/<service-key>.md`
+- `{{paths.harnessRoot}}/context/development/external-context/<service-key>.md`
+- `{{paths.harnessRoot}}/context/integrations/<contract>.md`
 
 ## External Context Index
 

package/templates-zh-CN/development/cross-repo-debugging.md

@@ -8,9 +8,9 @@ Confidence: low
 ## Debug Flow
 
 1. 先定位失败的 interface 或 flow。
-2. 读 `coding-agent-harness/context/architecture/service-catalog.md`，确认归属和上下游服务。
-3. 读对应的 `coding-agent-harness/context/integrations/` 契约。
-4. 读 `coding-agent-harness/context/development/external-context/<service-key>.md`，使用其中的 mock、stub 和本地调试说明。
+2. 读 `{{paths.harnessRoot}}/context/architecture/service-catalog.md`，确认归属和上下游服务。
+3. 读对应的 `{{paths.harnessRoot}}/context/integrations/` 契约。
+4. 读 `{{paths.harnessRoot}}/context/development/external-context/<service-key>.md`，使用其中的 mock、stub 和本地调试说明。
 
 ## Known Failure Modes
 

package/templates-zh-CN/development/external-context/service-template.md

@@ -9,7 +9,7 @@ Confidence: low
 
 | Service Profile | Source Pack | Integration Contracts | Last Verified | Confidence |
 | --- | --- | --- | --- | --- |
-| `coding-agent-harness/context/architecture/services/<service-key>.md` | `coding-agent-harness/context/development/external-source-packs/<source-key>/README.md` 或 N/A | `coding-agent-harness/context/integrations/<contract>.md` | unknown | low |
+| `{{paths.harnessRoot}}/context/architecture/services/<service-key>.md` | `{{paths.harnessRoot}}/context/development/external-source-packs/<source-key>/README.md` 或 N/A | `{{paths.harnessRoot}}/context/integrations/<contract>.md` | unknown | low |
 
 ## Development Use
 

package/templates-zh-CN/development/external-source-packs/README.md

@@ -7,9 +7,9 @@ Confidence: low
 
 ## Purpose
 
-这个目录只承载外部资料的摄取、索引和摘要。稳定事实必须投影到 `context/architecture`、`coding-agent-harness/context/development/external-context` 或 `context/integrations` 后才算进入 Harness 执行上下文。
+这个目录只承载外部资料的摄取、索引和摘要。稳定事实必须投影到 `context/architecture`、`{{paths.harnessRoot}}/context/development/external-context` 或 `context/integrations` 后才算进入 Harness 执行上下文。
 
-先读 `coding-agent-harness/governance/standards/external-source-intake-standard.md`，再新增资料包。
+先读 `{{paths.harnessRoot}}/governance/standards/external-source-intake-standard.md`，再新增资料包。
 
 ## Source Packs
 

package/templates-zh-CN/integrations/README.md

@@ -13,8 +13,8 @@ Keep the English field names and section headings because CLI checks rely on the
 
 ## Boundary
 
-- 服务拓扑和职责归属放 `coding-agent-harness/context/architecture/`。
-- 开发 mock 和调试说明放 `coding-agent-harness/context/development/`。
+- 服务拓扑和职责归属放 `{{paths.harnessRoot}}/context/architecture/`。
+- 开发 mock 和调试说明放 `{{paths.harnessRoot}}/context/development/`。
 - endpoint、payload、error、auth、event、webhook、SDK 契约放这里。
 
 ## Structure Contract
@@ -30,8 +30,8 @@ Keep the English field names and section headings because CLI checks rely on the
 
 每个接口契约必须是独立文件，并链接回对应服务：
 
-- 服务职责和上下游关系：`coding-agent-harness/context/architecture/service-catalog.md` 或 `services/<service-key>.md`
-- 本地 mock / stub / debug：`coding-agent-harness/context/development/external-context/<service-key>.md`
+- 服务职责和上下游关系：`{{paths.harnessRoot}}/context/architecture/service-catalog.md` 或 `services/<service-key>.md`
+- 本地 mock / stub / debug：`{{paths.harnessRoot}}/context/development/external-context/<service-key>.md`
 - 具体 payload、auth、error、contract test：本文件夹
 
 不要在一个“接口说明”大文档里混写多个服务。多个微服务就维护多个契约文件；README 里的 Contract Index 负责让人和 Agent 快速定位。

package/templates-zh-CN/integrations/api-contract.md

@@ -13,7 +13,7 @@ API
 
 | Service Profile | Development Context | Contract Index | Last Verified | Confidence |
 | --- | --- | --- | --- | --- |
-| `coding-agent-harness/context/architecture/services/<service-key>.md` | `coding-agent-harness/context/development/external-context/<service-key>.md` | `coding-agent-harness/context/integrations/README.md` | unknown | low |
+| `{{paths.harnessRoot}}/context/architecture/services/<service-key>.md` | `{{paths.harnessRoot}}/context/development/external-context/<service-key>.md` | `{{paths.harnessRoot}}/context/integrations/README.md` | unknown | low |
 
 ## Auth
 

package/templates-zh-CN/integrations/event-contract.md

@@ -13,7 +13,7 @@ Event
 
 | Service Profile | Development Context | Contract Index | Last Verified | Confidence |
 | --- | --- | --- | --- | --- |
-| `coding-agent-harness/context/architecture/services/<service-key>.md` | `coding-agent-harness/context/development/external-context/<service-key>.md` | `coding-agent-harness/context/integrations/README.md` | unknown | low |
+| `{{paths.harnessRoot}}/context/architecture/services/<service-key>.md` | `{{paths.harnessRoot}}/context/development/external-context/<service-key>.md` | `{{paths.harnessRoot}}/context/integrations/README.md` | unknown | low |
 
 ## Topic / Channel
 

package/templates-zh-CN/integrations/third-party/vendor-template.md

@@ -13,7 +13,7 @@ Third-party service
 
 | Service Profile | Development Context | Contract Index | Last Verified | Confidence |
 | --- | --- | --- | --- | --- |
-| `coding-agent-harness/context/architecture/services/<vendor-key>.md` | `coding-agent-harness/context/development/external-context/<vendor-key>.md` | `coding-agent-harness/context/integrations/README.md` | unknown | low |
+| `{{paths.harnessRoot}}/context/architecture/services/<vendor-key>.md` | `{{paths.harnessRoot}}/context/development/external-context/<vendor-key>.md` | `{{paths.harnessRoot}}/context/integrations/README.md` | unknown | low |
 
 ## Auth
 

package/templates-zh-CN/integrations/webhook-contract.md

@@ -13,7 +13,7 @@ Webhook
 
 | Service Profile | Development Context | Contract Index | Last Verified | Confidence |
 | --- | --- | --- | --- | --- |
-| `coding-agent-harness/context/architecture/services/<service-key>.md` | `coding-agent-harness/context/development/external-context/<service-key>.md` | `coding-agent-harness/context/integrations/README.md` | unknown | low |
+| `{{paths.harnessRoot}}/context/architecture/services/<service-key>.md` | `{{paths.harnessRoot}}/context/development/external-context/<service-key>.md` | `{{paths.harnessRoot}}/context/integrations/README.md` | unknown | low |
 
 ## Auth
 

package/templates-zh-CN/ledger/Harness-Ledger.md

@@ -12,7 +12,7 @@ Repo Governance / CI-CD 变化仍通过对应 reference 和任务证据路由。
 
 | ID | Scope | Module | Task | State | Queues | Plan | Review | Lessons Check | Closeout | Residual | Updated |
 | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| HL-YYYY-MM-DD-001 | task | none | 短任务标题 | planned | none | coding-agent-harness/planning/tasks/.../task_plan.md | pending | pending | pending | none | YYYY-MM-DD |
+| HL-YYYY-MM-DD-001 | task | none | 短任务标题 | planned | none | {{paths.harnessRoot}}/planning/tasks/.../task_plan.md | pending | pending | pending | none | YYYY-MM-DD |
 
 ## 字段规则
 

package/templates-zh-CN/lessons/lesson-arch-process-change.md

@@ -4,7 +4,7 @@
 
 - **ID**: L-[YYYY-MM-DD-NNN]
 - **日期**: YYYY-MM-DD
-- **来源**: `coding-agent-harness/planning/tasks/<task>/walkthrough.md`
+- **来源**: `{{paths.harnessRoot}}/planning/tasks/<task>/walkthrough.md`
 - **类型**: arch-change / process-change
 - **目标**: [受影响的模块、流程、reference、template 或 checker]
 - **提出者**: [agent session / model / human]

package/templates-zh-CN/lessons/lesson-new-doc.md

@@ -4,9 +4,9 @@
 
 - **ID**: L-[YYYY-MM-DD-NNN]
 - **日期**: YYYY-MM-DD
-- **来源**: `coding-agent-harness/planning/tasks/<task>/walkthrough.md`
+- **来源**: `{{paths.harnessRoot}}/planning/tasks/<task>/walkthrough.md`
 - **类型**: new-doc
-- **建议路径**: `coding-agent-harness/governance/standards/[建议文件名].md`
+- **建议路径**: `{{paths.harnessRoot}}/governance/standards/[建议文件名].md`
 - **提出者**: [agent session / model / human]
 
 ## 背景
@@ -23,7 +23,7 @@
 
 ## 建议路径
 
-`coding-agent-harness/governance/standards/[建议文件名].md`
+`{{paths.harnessRoot}}/governance/standards/[建议文件名].md`
 
 ## 建议文档内容
 

package/templates-zh-CN/lessons/lesson-ref-change.md

@@ -4,9 +4,9 @@
 
 - **ID**: L-[YYYY-MM-DD-NNN]
 - **日期**: YYYY-MM-DD
-- **来源**: `coding-agent-harness/planning/tasks/<task>/walkthrough.md`
+- **来源**: `{{paths.harnessRoot}}/planning/tasks/<task>/walkthrough.md`
 - **类型**: ref-change
-- **目标**: `coding-agent-harness/governance/standards/[目标文件].md`
+- **目标**: `{{paths.harnessRoot}}/governance/standards/[目标文件].md`
 - **提出者**: [agent session / model / human]
 
 ## 背景
@@ -42,7 +42,7 @@
 - 当前是否有其他 pending 条目指向同一目标：是 / 否
 - 如果有，涉及条目：L-[XXX]
 - 本文档是否已考虑冲突：是 / 否
-- 基于版本：当前正式 reference（`coding-agent-harness/governance/standards/[目标文件].md`）@ YYYY-MM-DD
+- 基于版本：当前正式 reference（`{{paths.harnessRoot}}/governance/standards/[目标文件].md`）@ YYYY-MM-DD
 
 ## 完整副本
 
@@ -50,7 +50,7 @@
 
 ---
 <!-- 完整副本开始 -->
-<!-- 基于: coding-agent-harness/governance/standards/[目标文件].md @ YYYY-MM-DD -->
+<!-- 基于: {{paths.harnessRoot}}/governance/standards/[目标文件].md @ YYYY-MM-DD -->
 <!-- 本副本独立于其他 pending 改动 -->
 
 [完整的修改后文档内容]

package/templates-zh-CN/modules/module_brief.md

@@ -0,0 +1,47 @@
+# {{TASK_TITLE}} 模块
+
+## 模块 Key
+
+`{{TASK_ID}}`
+
+## 创建日期
+
+{{DATE}}
+
+## 一句话结果
+
+用一句话说明这个模块持续维护什么结果。
+
+## 完成后能得到什么
+
+用 100-300 字说明这个模块健康运行时，用户、项目、coordinator 或 worker agents
+能得到什么。说明它能改善哪些决策、交付协调、验证或交接工作。聚焦模块带来的运行结果，
+不要展开内部流程。
+
+## 交付物
+
+- 可见产物：
+- 负责范围：
+- 验证证据：
+
+## 第一眼应该看什么
+
+写明人打开模块后应该先读哪个 module plan、任务列表、证据或生成产物。
+
+## 模块职责
+
+说明这个模块负责什么，以及为什么需要独立管理。
+
+## 边界
+
+- 负责：本模块拥有的目录、服务或文档区域。
+- 共享面：需要 coordinator 同步的文件。
+- 不负责：相邻模块或未声明的全局文件。
+
+## 完成判断
+
+列出能证明这个模块 brief 仍然反映当前模块合同的条件。执行细节保留在 `module_plan.md`。
+
+## 当前工作
+
+列出当前模块任务，或指向 `module_plan.md`。

package/templates-zh-CN/modules/module_plan.md

@@ -0,0 +1,48 @@
+# {{TASK_TITLE}} 模块计划
+
+## 模块身份
+
+- 模块 Key：`{{TASK_ID}}`
+- 负责人：coordinator
+- 分支：
+- 写入范围：
+- 共享面：
+- 依赖模块：
+
+## 边界
+
+- 可以编辑：
+- 禁止编辑：
+- 外部依赖：
+
+## 步骤
+
+| 步骤 ID | 名称 | 状态 | 任务计划 | 依赖 |
+| --- | --- | --- | --- | --- |
+| MOD-01 | 定义模块运行合同 | planned | none | none |
+
+## 活跃任务
+
+| 任务 | 状态 | 负责人 | 证据 | 备注 |
+| --- | --- | --- | --- | --- |
+| none | planned | coordinator | none | 有模块任务后替换此行。 |
+
+## 验证
+
+| 检查 | 命令或证据 | 必需 |
+| --- | --- | --- |
+| 模块任务合同 | `harness check --profile target-project .` | yes |
+
+## 交接
+
+- 分支：
+- Commit SHA：
+- 检查：
+- 变更文件：
+- 残余风险：
+- 需要 coordinator 同步：
+
+## 模板边界
+
+模块根目录默认只拥有 `brief.md` 和 `module_plan.md`。`execution_strategy.md`、
+`visual_map.md`、`review.md`、`walkthrough.md` 等执行合同属于具体任务目录。

package/templates-zh-CN/modules/registry_view.md

@@ -0,0 +1,9 @@
+# Module Registry
+
+由 `harness.yaml` 的 `modules.items` 生成。不要直接编辑这个视图。
+
+## 活跃模块
+
+| ID | Key | Title | Prefix | Branch | Current Step | Status | Owner | Scope | Shared | Depends On | Plan | Brief | Updated |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| none | none | none | none | none | none | planned | none | none | none | none | none | none | none |

package/templates-zh-CN/modules/session_prompt_pack.md

@@ -0,0 +1,50 @@
+# 模块会话提示词包
+
+coordinator 为已注册模块启动工作时使用这份全局提示词包。开始前用 `harness.yaml`、
+生成的 `Module-Registry.md` 和模块 `module_plan.md` 中的真实信息替换占位内容。
+
+## 上下文包
+
+- 项目：[project]
+- 模块 Key：[module]
+- 任务目录：[path]
+- 模块计划：[path]
+- 分配的 worktree：[path]
+- 分配的分支：[branch]
+
+## 目标
+
+[写一个具体的模块结果。]
+
+## 写入范围
+
+只允许编辑：
+
+- [path]
+
+除非 coordinator 明确分配范围，不要编辑共享 SSoT、coordinator 负责的集成文件或无关模块。
+
+## 必需输出
+
+- 分支名
+- Commit SHA
+- 变更文件
+- 已运行检查及结果
+- 残余风险
+- 需要 coordinator 同步的事项
+
+## 审查与状态规则
+
+- 汇报时区分 `task.state`、`lifecycleState`、`reviewStatus` 和 `closeoutStatus`。
+- `done` 只表示实现步骤完成；有 closeout 证据后才是 `closed`。
+- 使用当前任务 `visual_map.md` 阶段表作为生命周期地图。切片结束时检查当前 gate phase；只有 `Actor` 为 `agent` 的 `Exit Command` 才由 Agent 执行。
+- 需要审查时更新 `review.md`。人工审查完成必须通过本地 dashboard workbench，或由 coordinator 执行 `harness review-confirm`；存在开放 P0/P1/P2 finding 时不得确认。
+
+## 共享同步规则
+
+除非 coordinator 分配共享锁，worker 会话不得更新 Module Registry、Harness Ledger、
+Closeout Index、Regression SSoT 或 Cadence Ledger。
+
+## 暂停规则
+
+如果请求需要超出已分配范围、处理无关 dirty 文件、做产品决策或改变共享合同，暂停并汇报。

package/templates-zh-CN/planning/INDEX.md

@@ -49,6 +49,7 @@ Task Contract: harness-task/v1
 | `task_plan.md` | 当前任务目标、范围、所选预算、验收标准和执行决策。 |
 | `visual_map.md` | 阶段图、证据状态、下一步生命周期命令和支持性图表。 |
 | `progress.md` | 执行日志、验证证据、决策和交接记录。 |
+| `walkthrough.md` | 任务本地 closeout 摘要、验证、审查处置、残余风险和链接。 |
 
 ## 标准任务文件