coding-agent-harness 1.0.5 → 1.0.6

package/templates/integrations/event-contract.md

@@ -13,7 +13,7 @@ Event
 
 | Service Profile | Development Context | Contract Index | Last Verified | Confidence |
 | --- | --- | --- | --- | --- |
-| `docs/03-ARCHITECTURE/services/<service-key>.md` | `docs/04-DEVELOPMENT/external-context/<service-key>.md` | `docs/06-INTEGRATIONS/README.md` | unknown | low |
+| `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 |
 
 ## Topic / Channel
 
@@ -43,4 +43,4 @@ Event
 
 ## Placement Rule
 
-This file describes one event contract only. Put service responsibility in `03-ARCHITECTURE`; put local mock/stub/debug details in `04-DEVELOPMENT`.
+This file describes one event contract only. Put service responsibility in `context/architecture`; put local mock/stub/debug details in `context/development`.

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

@@ -13,7 +13,7 @@ Third-party service
 
 | Service Profile | Development Context | Contract Index | Last Verified | Confidence |
 | --- | --- | --- | --- | --- |
-| `docs/03-ARCHITECTURE/services/<vendor-key>.md` | `docs/04-DEVELOPMENT/external-context/<vendor-key>.md` | `docs/06-INTEGRATIONS/README.md` | unknown | low |
+| `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 |
 
 ## Auth
 
@@ -39,4 +39,4 @@ Third-party service
 
 ## Placement Rule
 
-This file describes one third-party integration only. Put account/permission/SDK/limit facts here; put business responsibility and system topology in `03-ARCHITECTURE`.
+This file describes one third-party integration only. Put account/permission/SDK/limit facts here; put business responsibility and system topology in `context/architecture`.

package/templates/integrations/webhook-contract.md

@@ -13,7 +13,7 @@ Webhook
 
 | Service Profile | Development Context | Contract Index | Last Verified | Confidence |
 | --- | --- | --- | --- | --- |
-| `docs/03-ARCHITECTURE/services/<service-key>.md` | `docs/04-DEVELOPMENT/external-context/<service-key>.md` | `docs/06-INTEGRATIONS/README.md` | unknown | low |
+| `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 |
 
 ## Auth
 
@@ -38,4 +38,4 @@ Webhook
 
 ## Placement Rule
 
-This file describes one webhook contract only. Put service responsibility in `03-ARCHITECTURE`; put local mock/stub/debug details in `04-DEVELOPMENT`.
+This file describes one webhook contract only. Put service responsibility in `context/architecture`; put local mock/stub/debug details in `context/development`.

package/templates/ledger/Harness-Ledger.md

@@ -12,7 +12,7 @@ Repo Governance / CI-CD changes remain routed through their reference standards
 
 | ID | Scope | Module | Task | State | Queues | Plan | Review | Lessons Check | Closeout | Residual | Updated |
 | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| HL-YYYY-MM-DD-001 | task | none | Short operational title | planned | none | docs/09-PLANNING/TASKS/.../task_plan.md | pending | pending | pending | none | YYYY-MM-DD |
+| HL-YYYY-MM-DD-001 | task | none | Short operational title | planned | none | coding-agent-harness/planning/tasks/.../task_plan.md | pending | pending | pending | none | YYYY-MM-DD |
 
 ## Field Rules
 

package/templates/planning/INDEX.md

@@ -49,6 +49,7 @@ Task Contract: harness-task/v1
 | `task_plan.md` | Current task goal, scope, selected budget, acceptance, and operating decisions. |
 | `visual_map.md` | Phase map, evidence status, next lifecycle commands, and supporting diagrams. |
 | `progress.md` | Execution log, verification evidence, decisions, and handoff notes. |
+| `walkthrough.md` | Task-local closeout summary, verification, review disposition, residual risk, and links. |
 
 ## Standard Task Files
 

package/templates/planning/module_session_prompt.md

@@ -39,7 +39,7 @@ Do not edit shared SSoT files, coordinator-owned integration files, or unrelated
 
 ## Shared Sync Rule
 
-Do not update Module Registry, Harness Ledger, Closeout SSoT, Regression SSoT, or Cadence Ledger from a worker session unless the coordinator assigned the shared lock.
+Do not update Module Registry, Harness Ledger, Closeout Index, Regression SSoT, or Cadence Ledger from a worker session unless the coordinator assigned the shared lock.
 
 ## Stop Rule
 

package/templates/planning/task_plan.md

@@ -69,4 +69,4 @@ Rationale: [why this budget fits this task]
 
 - Global sync owner: coordinator / n/a
 - Global sync status: pending-coordinator-pass / synced / n/a
-- Shared updates needed: [Module Registry / Harness Ledger / Closeout SSoT / Regression SSoT / none]
+- Shared updates needed: [Module Registry / Harness Ledger / Closeout Index / Regression SSoT / none]

package/templates/planning/walkthrough.md

@@ -0,0 +1,47 @@
+# Walkthrough: {{TASK_TITLE}}
+
+## Summary
+
+Pending closeout.
+
+## Scope
+
+| Area | Details |
+| --- | --- |
+| Changed modules | pending |
+| New files | pending |
+| Removed files | pending |
+| Out of scope | pending |
+
+## Verification
+
+| Check | Command or Procedure | Result | Evidence |
+| --- | --- | --- | --- |
+| pending | pending | not run | pending |
+
+## Review Disposition
+
+| Source | Material Findings | Resolution | Evidence |
+| --- | --- | --- | --- |
+| pending | pending | pending | `review.md` |
+
+## Residual Risk
+
+| Risk | Owner | Accepted? | Follow-up |
+| --- | --- | --- | --- |
+| pending | owner | pending | pending |
+
+## Lessons Reflection
+
+| Question | Answer |
+| --- | --- |
+| Was a lesson candidate reviewed? | pending |
+| Lessons detail doc | `lesson_candidates.md` |
+
+## Closeout Links
+
+| Artifact | Link |
+| --- | --- |
+| Task plan | `task_plan.md` |
+| Review | `review.md` |
+| Progress | `progress.md` |

package/templates/reference/docs-library-standard.md

@@ -20,16 +20,16 @@ Use these directories as a low-entropy context system:
 
 | Directory | Owns | Must Not Own | Required Schema Signals |
 | --- | --- | --- | --- |
-| `docs/03-ARCHITECTURE/` | system structure, service responsibility, ownership, service catalog, critical flows, ADRs | endpoint payloads, mock instructions, task logs | `Context Doc Type`, `Source Evidence`, `Last Verified`, `Confidence` |
-| `docs/04-DEVELOPMENT/` | local setup, codebase map, external development context, external source packs, mocks, stubs, cross-repo debugging | long-lived architecture facts, API payload contracts, undigested external document dumps | `Context Doc Type`, `Development Use`, `Do Not Assume`, `Mocks / Stubs`, `Source Evidence`, `Last Verified`, `Confidence` |
-| `docs/06-INTEGRATIONS/` | API/event/webhook/SDK/third-party contracts, auth, payloads, errors, contract tests | global topology, service ownership catalog, debugging notes | `Context Doc Type`, `Contract Type`, `Auth`, `Payload`, `Errors`, `Contract Tests`, `Source Evidence`, `Last Verified`, `Confidence` |
+| `coding-agent-harness/context/architecture/` | system structure, service responsibility, ownership, service catalog, critical flows, ADRs | endpoint payloads, mock instructions, task logs | `Context Doc Type`, `Source Evidence`, `Last Verified`, `Confidence` |
+| `coding-agent-harness/context/development/` | local setup, codebase map, external development context, external source packs, mocks, stubs, cross-repo debugging | long-lived architecture facts, API payload contracts, undigested external document dumps | `Context Doc Type`, `Development Use`, `Do Not Assume`, `Mocks / Stubs`, `Source Evidence`, `Last Verified`, `Confidence` |
+| `coding-agent-harness/context/integrations/` | API/event/webhook/SDK/third-party contracts, auth, payloads, errors, contract tests | global topology, service ownership catalog, debugging notes | `Context Doc Type`, `Contract Type`, `Auth`, `Payload`, `Errors`, `Contract Tests`, `Source Evidence`, `Last Verified`, `Confidence` |
 
 Concrete split:
 
-- `03-ARCHITECTURE/service-catalog.md` gives only the service summary and links.
-- `06-INTEGRATIONS/<service>-api-contract.md` owns payload bodies, auth, errors, and contract tests.
-- `04-DEVELOPMENT/external-context/<service>.md` owns mocks, stubs, unsafe assumptions, and debug notes.
-- `04-DEVELOPMENT/external-source-packs/` owns external source indexes, digests, and projection status only; final facts must be written back to `03/04/06`.
+- `coding-agent-harness/context/architecture/service-catalog.md` gives only the service summary and links.
+- `coding-agent-harness/context/integrations/<service>-api-contract.md` owns payload bodies, auth, errors, and contract tests.
+- `coding-agent-harness/context/development/external-context/<service>.md` owns mocks, stubs, unsafe assumptions, and debug notes.
+- `coding-agent-harness/context/development/external-source-packs/` owns external source indexes, digests, and projection status only; final facts must be written back to `context/{architecture,development,integrations}`.
 
 ## External Source Intake
 
@@ -51,7 +51,7 @@ Raw external material that has not been digested and projected must not become e
 - Generated or private artifacts are excluded or explicitly separated.
 - Cross-links point to the source of truth for each subject.
 - New standards include closeout and evidence expectations.
-- `03/04/06` documents use the required schema signals and route misplaced content back to the correct directory.
+- `context/{architecture,development,integrations}` documents use the required schema signals and route misplaced content back to the correct directory.
 - External source packs, when present, have a registry, digests, projection targets, and residuals.
 
 ## Closeout Expectations

package/templates/reference/external-source-intake-standard.md

@@ -7,10 +7,10 @@ This standard defines how agents receive, filter, organize, and project large ex
 ## Core Model
 
 ```text
-external source material -> source pack index -> digest -> 03/04/06 execution projection
+external source material -> source pack index -> digest -> context/{architecture,development,integrations} execution projection
 ```
 
-`03-ARCHITECTURE`, `04-DEVELOPMENT`, and `06-INTEGRATIONS` only hold facts that have been distilled enough to guide work. Raw external files, long documents, screenshots, exported chats, diagrams, and historical packets first go through `docs/04-DEVELOPMENT/external-source-packs/`.
+`context/architecture`, `context/development`, and `context/integrations` only hold facts that have been distilled enough to guide work. Raw external files, long documents, screenshots, exported chats, diagrams, and historical packets first go through `coding-agent-harness/context/development/external-source-packs/`.
 
 ## When To Ask The User
 
@@ -32,27 +32,27 @@ Recommended questions:
 
 | Case | Storage |
 | --- | --- |
-| Only 1-4 stable external documents | No separate source pack is required; link them from `Source Evidence` in the relevant `03/04/06` docs |
-| More than 5 documents, multiple topics, or continuing growth | Create `docs/04-DEVELOPMENT/external-source-packs/<source-key>/` |
+| Only 1-4 stable external documents | No separate source pack is required; link them from `Source Evidence` in the relevant `context/{architecture,development,integrations}` docs |
+| More than 5 documents, multiple topics, or continuing growth | Create `coding-agent-harness/context/development/external-source-packs/<source-key>/` |
 | Material contains secrets, customer data, private links, or cannot be committed | Do not copy raw files; record external location, owner, access condition, and digest only |
 | Material is safe to commit | Raw files may go under `raw/`, but only digested facts may be projected into execution docs |
 
 Recommended structure:
 
 ```text
-docs/04-DEVELOPMENT/external-source-packs/<source-key>/
+coding-agent-harness/context/development/external-source-packs/<source-key>/
 ├── README.md              # source index and projection status
 ├── digests/               # digest for each source or source group
 ├── raw/                   # commit-safe raw material only
 └── raw-index.md           # path/URL/owner index when raw material cannot be committed
 ```
 
-Do not replicate a full `03/04/06` tree for every microservice. The source pack is the intake layer. The stable execution entries remain:
+Do not replicate a full `context/{architecture,development,integrations}` tree for every microservice. The source pack is the intake layer. The stable execution entries remain:
 
-- `docs/03-ARCHITECTURE/service-catalog.md`
-- `docs/03-ARCHITECTURE/services/<service-key>.md`
-- `docs/04-DEVELOPMENT/external-context/<service-key>.md`
-- `docs/06-INTEGRATIONS/<contract>.md`
+- `coding-agent-harness/context/architecture/service-catalog.md`
+- `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`
 
 ## Intake Flow
 
@@ -60,7 +60,7 @@ Do not replicate a full `03/04/06` tree for every microservice. The source pack
 2. **Classify**: tag each source as architecture, development, integration, security, operations, product, or unknown.
 3. **Sanitize**: check for secrets, tokens, customer data, personal information, internal accounts, and private links; keep non-committable material as references only.
 4. **Digest**: extract facts, questions, unsafe assumptions, and evidence with the digest template.
-5. **Project**: move stable facts into `03/04/06`, then mark the source as projected in the source pack README.
+5. **Project**: move stable facts into `context/{architecture,development,integrations}`, then mark the source as projected in the source pack README.
 6. **Verify**: use code evidence, contract tests, owner confirmation, or runtime checks where feasible; update `Last Verified` and `Confidence`.
 7. **Residual**: keep unverified or conflicting facts in the source pack or in `Do Not Assume`; do not treat them as execution facts.
 
@@ -68,14 +68,14 @@ Do not replicate a full `03/04/06` tree for every microservice. The source pack
 
 | Source Content | Projection Target |
 | --- | --- |
-| Service responsibility, upstream/downstream relationship, owner, data ownership, topology | `03-ARCHITECTURE/service-catalog.md` or `services/<service-key>.md` |
-| Local mocks, stubs, startup, debugging, cross-repo development behavior | `04-DEVELOPMENT/external-context/<service-key>.md` |
-| Endpoint, payload, auth, error, event, webhook, SDK, contract test | `06-INTEGRATIONS/<contract>.md` |
+| Service responsibility, upstream/downstream relationship, owner, data ownership, topology | `coding-agent-harness/context/architecture/service-catalog.md` or `services/<service-key>.md` |
+| Local mocks, stubs, startup, debugging, cross-repo development behavior | `coding-agent-harness/context/development/external-context/<service-key>.md` |
+| Endpoint, payload, auth, error, event, webhook, SDK, contract test | `coding-agent-harness/context/integrations/<contract>.md` |
 | Unconfirmed, conflicting, stale, or background-only material | Keep in source pack README / digest; do not project into execution docs |
 
 ## Prohibited
 
-- Do not copy large external document sets directly into `03-ARCHITECTURE`, `04-DEVELOPMENT`, or `06-INTEGRATIONS`.
+- Do not copy large external document sets directly into `context/architecture`, `context/development`, or `context/integrations`.
 - Do not treat an external-source digest as verified fact without `Source Evidence`, `Last Verified`, and `Confidence`.
 - Do not keep long raw excerpts, chat logs, or meeting transcripts inside execution docs.
 - Do not commit secrets, production tokens, customer data, personal information, or non-public raw material.

package/templates/reference/repo-governance-standard.md

@@ -12,7 +12,7 @@ Define repository-level rules for branches, commits, pull requests, ownership, g
 4. Generated files, caches, build output, local runtime state, and secrets must be ignored or stored in the approved location.
 5. Commit verified, meaningful slices proactively. Deferred commits require an explicit no-commit reason, owner, and next step.
 6. Do not mix unrelated dirty changes into a task commit. CLI-owned Harness writes should use the local Harness commands so their locked, allowlisted auto-commit can protect shared governance files.
-7. Pull requests must follow `docs/11-REFERENCE/pull-request-standard.md` and describe intent, changed surfaces, version impact, checks run, checks not run, review status, references, and residual risk.
+7. Pull requests must follow `coding-agent-harness/governance/standards/pull-request-standard.md` and describe intent, changed surfaces, version impact, checks run, checks not run, review status, references, and residual risk.
 8. Required checks and material review findings block merge unless an approved exception is recorded.
 9. Merge or release ownership must be explicit when several branches or workers contribute to the same outcome.
 

package/templates/ssot/Module-Registry.md

@@ -20,7 +20,7 @@ Track module ownership, write scope, branch or worktree assignment, and coordina
 
 | 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 | docs/09-PLANNING/TASKS/.../task_plan.md | none | none | pending | none | YYYY-MM-DD |
+| 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
 

package/templates/walkthrough/walkthrough-template.md

@@ -56,8 +56,8 @@ One sentence describing what changed and why it matters.
 
 | Artifact | Link |
 | --- | --- |
-| Task plan | docs/09-PLANNING/TASKS/.../task_plan.md |
+| Task plan | coding-agent-harness/planning/tasks/.../task_plan.md |
 | Feature or Delivery SSoT | F-000 or D-000 |
 | Harness Ledger | HL-YYYY-MM-DD-001 |
-| Closeout SSoT | CO-YYYY-MM-DD-001 |
+| Task-local closeout | walkthrough.md |
 | Pull request or commit | link or hash |

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

@@ -1,7 +1,7 @@
 # [项目名称]
 
 这个文件是 Agent 进入本仓库时的工作入口。它只负责说明硬规则和阅读路由；
-详细规范放在 `docs/11-REFERENCE/`，不要把操作手册全部塞进这里。
+详细规范放在 `coding-agent-harness/governance/standards/`，不要把操作手册全部塞进这里。
 
 ## 项目概况
 
@@ -13,9 +13,9 @@
 
 ## 不可违反的规则
 
-1. 遵守 `docs/11-REFERENCE/engineering-standard.md` 中的架构边界。
+1. 遵守 `coding-agent-harness/governance/standards/engineering-standard.md` 中的架构边界。
 2. 不提交密钥、令牌、私有接口、用户隐私数据或生产凭据。
-3. 非平凡任务先用 Harness CLI 在 `docs/09-PLANNING/TASKS/` 下建立任务目录。
+3. 非平凡任务先用 Harness CLI 在 `coding-agent-harness/planning/tasks/` 下建立任务目录。
 4. 声称完成前必须记录证据。
 5. 保护无关工作区改动，不回滚任务范围外文件。
 6. 已验证的、有意义的工作切片要主动提交。除非用户明确暂停提交、检查失败、dirty 归属不清，或安全边界导致无法形成干净提交，否则不要把已完成工作只留在未提交文件里；不能提交时，必须在 progress、handoff 或 closeout 中写明 no-commit reason、owner 和下一步。不要把无关 dirty 改动混入本任务提交。
@@ -27,23 +27,23 @@
 
 | 任务类型 | 先读文件 |
 | --- | --- |
-| 架构、核心模块、跨模块改动 | `docs/11-REFERENCE/engineering-standard.md` |
-| 系统地图、服务职责、外部系统关系 | `docs/03-ARCHITECTURE/README.md`、`docs/03-ARCHITECTURE/service-catalog.md` |
-| 本地开发、mock、stub、跨仓调试 | `docs/04-DEVELOPMENT/README.md`、`docs/04-DEVELOPMENT/codebase-map.md` |
-| API、event、webhook、SDK、第三方契约 | `docs/06-INTEGRATIONS/README.md` 和相关契约文件 |
-| 测试、冒烟、回归 | `docs/11-REFERENCE/testing-standard.md`、`docs/05-TEST-QA/Regression-SSoT.md` |
-| 开发执行、提交、PR、发布 | `docs/11-REFERENCE/execution-workflow-standard.md`、`docs/11-REFERENCE/repo-governance-standard.md`、`docs/11-REFERENCE/pull-request-standard.md`、`docs/11-REFERENCE/ci-cd-standard.md` |
-| 创建或推进任务 | `docs/09-PLANNING/TASKS/` 下的当前任务目录；如果本项目已配置 Harness CLI，使用 `harness new-task` / lifecycle 命令 |
+| 架构、核心模块、跨模块改动 | `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 命令 |
 | Brief、Execution Strategy、Visual Map | 当前任务的 `brief.md`、`execution_strategy.md`、`visual_map.md` |
-| 长程任务 | `docs/11-REFERENCE/long-running-task-standard.md` |
-| reviewer、subagent、对抗性审查 | `docs/11-REFERENCE/review-routing-standard.md`、`docs/11-REFERENCE/adversarial-review-standard.md` |
-| 多人协作、多仓交付、阶段性交付 | `docs/11-REFERENCE/delivery-operating-model-standard.md`、`docs/09-PLANNING/Delivery-SSoT.md` |
-| 模块并行 | `docs/09-PLANNING/Module-Registry.md` 和相关 module plan |
-| 文档治理或 Harness 更新 | `docs/11-REFERENCE/docs-library-standard.md`、`.harness-capabilities.json` |
-| 外部资料摄取 | `docs/11-REFERENCE/external-source-intake-standard.md` |
-| Regression SSoT 维护 | `docs/11-REFERENCE/regression-ssot-governance.md` |
-| 收口、walkthrough、Lessons | `docs/11-REFERENCE/walkthrough-standard.md`、`docs/10-WALKTHROUGH/Closeout-SSoT.md`、当前任务 `lesson_candidates.md`、`docs/01-GOVERNANCE/lessons/` |
-| Worktree、并行开发隔离 | `docs/11-REFERENCE/worktree-standard.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` |
 
 ## 标准执行流程
 
@@ -72,14 +72,14 @@
 
 ## 单一事实源
 
-- Harness Ledger：`docs/Harness-Ledger.md`（任务生命周期总账，由 CLI 生成）
-- Delivery SSoT：`docs/09-PLANNING/Delivery-SSoT.md`
-- Module Registry：`docs/09-PLANNING/Module-Registry.md`
-- Regression SSoT：`docs/05-TEST-QA/Regression-SSoT.md`
-- Cadence Ledger：`docs/05-TEST-QA/Cadence-Ledger.md`
+- 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`
 - Lesson Candidates：当前任务 `lesson_candidates.md`
-- Lesson Detail Docs：`docs/01-GOVERNANCE/lessons/`
-- Closeout SSoT：`docs/10-WALKTHROUGH/Closeout-SSoT.md`
+- Lesson Detail Docs：`coding-agent-harness/governance/lessons/`
+- Generated Closeout Index：`coding-agent-harness/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. 只加载必要的 `docs/11-REFERENCE/` 标准文件和任务目录上下文。
+3. 只加载必要的 `coding-agent-harness/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 细节放 `docs/06-INTEGRATIONS/`。
-- 本地启动、mock、stub、跨仓调试经验放 `docs/04-DEVELOPMENT/`。
+- Payload、endpoint 参数、event schema、SDK 细节放 `coding-agent-harness/context/integrations/`。
+- 本地启动、mock、stub、跨仓调试经验放 `coding-agent-harness/context/development/`。
 
 ## Structure Contract
 
@@ -46,6 +46,6 @@ Keep the English field names and file names because CLI checks rely on them.
 
 1. 这个服务负责什么、拥有什么数据。
 2. 它和本仓有什么关系。
-3. Agent 修改本仓前还需要读哪些 `04-DEVELOPMENT` 和 `06-INTEGRATIONS` 文档。
+3. Agent 修改本仓前还需要读哪些 `context/development` 和 `context/integrations` 文档。
 
-不要在 `03-ARCHITECTURE` 里堆接口字段、mock 指令或临时调试记录。那些内容分别放到 `06-INTEGRATIONS` 和 `04-DEVELOPMENT`。
+不要在 `context/architecture` 里堆接口字段、mock 指令或临时调试记录。那些内容分别放到 `context/integrations` 和 `context/development`。

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

@@ -12,6 +12,6 @@ Confidence: low
 
 ## Boundary Rule
 
-这个目录只放服务责任、接口摘要和跳转链接。Payload、auth、error code、event schema 放 `docs/06-INTEGRATIONS/`。
+这个目录只放服务责任、接口摘要和跳转链接。Payload、auth、error code、event schema 放 `coding-agent-harness/context/integrations/`。
 
-一个服务或微服务只占一行。只要该服务影响本仓开发或判断，就补 `services/<service-key>.md`、`docs/04-DEVELOPMENT/external-context/<service-key>.md` 和相关 `docs/06-INTEGRATIONS/<contract>.md` 链接。
+一个服务或微服务只占一行。只要该服务影响本仓开发或判断，就补 `services/<service-key>.md`、`coding-agent-harness/context/development/external-context/<service-key>.md` 和相关 `coding-agent-harness/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 |
 | --- | --- | --- | --- | --- | --- |
-| `docs/03-ARCHITECTURE/service-catalog.md` | `docs/04-DEVELOPMENT/external-context/<service-key>.md` | `docs/04-DEVELOPMENT/external-source-packs/<source-key>/README.md` 或 N/A | `docs/06-INTEGRATIONS/<contract>.md` | unknown | low |
+| `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 |
 
 ## 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、跨仓调试放这里。
-- 长期系统结构放 `docs/03-ARCHITECTURE/`。
-- API、event、webhook 等具体契约放 `docs/06-INTEGRATIONS/`。
+- 长期系统结构放 `coding-agent-harness/context/architecture/`。
+- API、event、webhook 等具体契约放 `coding-agent-harness/context/integrations/`。
 
 ## Structure Contract
 
@@ -32,21 +32,21 @@ Keep the English field names and section headings because CLI checks rely on the
 
 如果本仓依赖多个微服务，不要把所有外部知识写进一个大文档。只要某个外部服务会影响本仓开发或测试，就创建：
 
-- `docs/03-ARCHITECTURE/services/<service-key>.md`：该服务是什么、负责什么。
-- `docs/04-DEVELOPMENT/external-context/<service-key>.md`：本仓开发时如何 mock、stub、调试它。
-- `docs/06-INTEGRATIONS/<contract>.md`：具体 API/event/webhook 契约。
+- `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 契约。
 
-`04-DEVELOPMENT` 只放“开发时怎么处理这个外部服务”。不要在这里维护完整系统拓扑，也不要把 payload schema 塞进来。
+`context/development` 只放“开发时怎么处理这个外部服务”。不要在这里维护完整系统拓扑，也不要把 payload schema 塞进来。
 
 ## External Source Pack Rule
 
-如果外部团队给了多份文档、截图、导出包、会议纪要或链接，不要直接塞进 `03/04/06`。先读 `docs/11-REFERENCE/external-source-intake-standard.md`，再决定是否创建 `external-source-packs/<source-key>/`。
+如果外部团队给了多份文档、截图、导出包、会议纪要或链接，不要直接塞进 `context/{architecture,development,integrations}`。先读 `coding-agent-harness/governance/standards/external-source-intake-standard.md`，再决定是否创建 `external-source-packs/<source-key>/`。
 
 `external-source-packs/` 只负责资料索引、摘要和投影状态。稳定结论必须回写到：
 
-- `docs/03-ARCHITECTURE/services/<service-key>.md`
-- `docs/04-DEVELOPMENT/external-context/<service-key>.md`
-- `docs/06-INTEGRATIONS/<contract>.md`
+- `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`
 
 ## External Context Index
 

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

@@ -8,9 +8,9 @@ Confidence: low
 ## Debug Flow
 
 1. 先定位失败的 interface 或 flow。
-2. 读 `docs/03-ARCHITECTURE/service-catalog.md`，确认归属和上下游服务。
-3. 读对应的 `docs/06-INTEGRATIONS/` 契约。
-4. 读 `docs/04-DEVELOPMENT/external-context/<service-key>.md`，使用其中的 mock、stub 和本地调试说明。
+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 和本地调试说明。
 
 ## 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 |
 | --- | --- | --- | --- | --- |
-| `docs/03-ARCHITECTURE/services/<service-key>.md` | `docs/04-DEVELOPMENT/external-source-packs/<source-key>/README.md` 或 N/A | `docs/06-INTEGRATIONS/<contract>.md` | unknown | low |
+| `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 |
 
 ## Development Use
 
@@ -30,4 +30,4 @@ Confidence: low
 
 ## Placement Rule
 
-本文件只写本仓开发、测试、调试这个外部服务时需要的上下文。服务职责放 `03-ARCHITECTURE`，接口字段和 schema 放 `06-INTEGRATIONS`。
+本文件只写本仓开发、测试、调试这个外部服务时需要的上下文。服务职责放 `context/architecture`，接口字段和 schema 放 `context/integrations`。

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

@@ -7,18 +7,18 @@ Confidence: low
 
 ## Purpose
 
-这个目录只承载外部资料的摄取、索引和摘要。稳定事实必须投影到 `03-ARCHITECTURE`、`04-DEVELOPMENT/external-context` 或 `06-INTEGRATIONS` 后才算进入 Harness 执行上下文。
+这个目录只承载外部资料的摄取、索引和摘要。稳定事实必须投影到 `context/architecture`、`coding-agent-harness/context/development/external-context` 或 `context/integrations` 后才算进入 Harness 执行上下文。
 
-先读 `docs/11-REFERENCE/external-source-intake-standard.md`，再新增资料包。
+先读 `coding-agent-harness/governance/standards/external-source-intake-standard.md`，再新增资料包。
 
 ## Source Packs
 
-| Source Key | External Project / Service | Raw Storage Mode | Source Count | Digest Status | Projected To 03/04/06 | Owner | Last Verified | Confidence |
+| Source Key | External Project / Service | Raw Storage Mode | Source Count | Digest Status | Projected To context/{architecture,development,integrations} | Owner | Last Verified | Confidence |
 | --- | --- | --- | --- | --- | --- | --- | --- | --- |
 
 ## Placement Rule
 
-- 资料量小于 5 份时，优先在 `03/04/06` 的 `Source Evidence` 中引用，不必建资料包。
+- 资料量小于 5 份时，优先在 `context/{architecture,development,integrations}` 的 `Source Evidence` 中引用，不必建资料包。
 - 资料很多、跨多个主题或会持续增长时，创建 `<source-key>/README.md` 和 `digests/`。
 - `raw/` 只能放允许入仓、无密钥、无隐私、无客户数据的原始材料。
 - 不能入仓的资料只记录外部路径、owner、访问条件和 digest。

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
 
-- 服务拓扑和职责归属放 `docs/03-ARCHITECTURE/`。
-- 开发 mock 和调试说明放 `docs/04-DEVELOPMENT/`。
+- 服务拓扑和职责归属放 `coding-agent-harness/context/architecture/`。
+- 开发 mock 和调试说明放 `coding-agent-harness/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
 
 每个接口契约必须是独立文件，并链接回对应服务：
 
-- 服务职责和上下游关系：`docs/03-ARCHITECTURE/service-catalog.md` 或 `services/<service-key>.md`
-- 本地 mock / stub / debug：`docs/04-DEVELOPMENT/external-context/<service-key>.md`
+- 服务职责和上下游关系：`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`
 - 具体 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 |
 | --- | --- | --- | --- | --- |
-| `docs/03-ARCHITECTURE/services/<service-key>.md` | `docs/04-DEVELOPMENT/external-context/<service-key>.md` | `docs/06-INTEGRATIONS/README.md` | unknown | low |
+| `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 |
 
 ## Auth
 
@@ -39,4 +39,4 @@ API
 
 ## Placement Rule
 
-本文件只写一个 API 契约。服务职责放 `03-ARCHITECTURE`，本地 mock/stub/debug 放 `04-DEVELOPMENT`。
+本文件只写一个 API 契约。服务职责放 `context/architecture`，本地 mock/stub/debug 放 `context/development`。

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

@@ -13,7 +13,7 @@ Event
 
 | Service Profile | Development Context | Contract Index | Last Verified | Confidence |
 | --- | --- | --- | --- | --- |
-| `docs/03-ARCHITECTURE/services/<service-key>.md` | `docs/04-DEVELOPMENT/external-context/<service-key>.md` | `docs/06-INTEGRATIONS/README.md` | unknown | low |
+| `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 |
 
 ## Topic / Channel
 
@@ -43,4 +43,4 @@ Event
 
 ## Placement Rule
 
-本文件只写一个 event 契约。服务职责放 `03-ARCHITECTURE`，本地 mock/stub/debug 放 `04-DEVELOPMENT`。
+本文件只写一个 event 契约。服务职责放 `context/architecture`，本地 mock/stub/debug 放 `context/development`。

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 |
 | --- | --- | --- | --- | --- |
-| `docs/03-ARCHITECTURE/services/<vendor-key>.md` | `docs/04-DEVELOPMENT/external-context/<vendor-key>.md` | `docs/06-INTEGRATIONS/README.md` | unknown | low |
+| `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 |
 
 ## Auth
 
@@ -39,4 +39,4 @@ Third-party service
 
 ## Placement Rule
 
-本文件只写一个第三方集成。账号/权限/SDK/限制放这里；业务职责和系统拓扑放 `03-ARCHITECTURE`。
+本文件只写一个第三方集成。账号/权限/SDK/限制放这里；业务职责和系统拓扑放 `context/architecture`。