coding-agent-harness 1.0.5 → 1.0.6

package/docs-release/README.md

@@ -71,6 +71,7 @@ Not every document is written for the same reader.
 - `guides/migration-playbook.md` / `guides/migration-playbook.en-US.md` — smooth migration guide for existing legacy harness projects. 旧 Harness 项目的平滑迁移指南。
 - `guides/legacy-migration-agent-prompt.md` / `guides/legacy-migration-agent-prompt.zh-CN.md` — prompt contract for agents running baseline or full legacy migration. 给迁移 Agent 使用的执行合同。
 - `guides/full-legacy-migration-subagent-strategy.md` / `guides/full-legacy-migration-subagent-strategy.zh-CN.md` — full readable cutover strategy with subagent roles, adversarial review, and dashboard/CLI proof gates. 完整可读迁移的 subagent 分工、对抗审查和 Dashboard/CLI 证据门禁。
+- `guides/typescript-runtime-migration-closeout.md` — public closeout for the TypeScript runtime source-twin migration and the remaining `.mjs` shim policy. TypeScript runtime source twin 迁移收口和剩余 `.mjs` shim 策略。
 
 ## Repository Operating Models / 仓库运行模式
 

package/docs-release/architecture/overview.md

@@ -35,10 +35,10 @@ agent workflow runs over days, handoffs, reviews, and releases.
 ```mermaid
 flowchart TB
   Skill["Agent skill<br/>SKILL.md"]
-  CLI["Harness CLI<br/>scripts/harness.mjs"]
+  CLI["Harness CLI<br/>dist/harness.mjs"]
   Standards["Standards<br/>references/"]
   Templates["Scaffolds<br/>templates/ + templates-zh-CN/"]
-  Target["Target repository<br/>AGENTS.md + docs/"]
+  Target["Target repository<br/>AGENTS.md + coding-agent-harness/"]
   Scanner["Scanner and validators<br/>status/check"]
   Dashboard["Dashboard / Workbench<br/>HTML + JSON"]
   Human["Human reviewer<br/>approval and inspection"]
@@ -66,15 +66,15 @@ project facts.
 ```mermaid
 flowchart TB
   Entry["AGENTS.md<br/>agent entry and routing"]
-  Registry[".harness-capabilities.json<br/>enabled capabilities"]
+  Registry["coding-agent-harness/harness.yaml<br/>enabled capabilities"]
   Docs["docs/"]
-  Architecture["03-ARCHITECTURE<br/>system facts"]
-  Development["04-DEVELOPMENT<br/>local setup and code map"]
-  QA["05-TEST-QA<br/>regression and cadence"]
-  Integrations["06-INTEGRATIONS<br/>external contracts"]
-  Planning["09-PLANNING<br/>tasks and modules"]
-  Walkthrough["10-WALKTHROUGH<br/>closeout evidence"]
-  Reference["11-REFERENCE<br/>local operating standards"]
+  Architecture["coding-agent-harness/context/architecture<br/>system facts"]
+  Development["coding-agent-harness/context/development<br/>local setup and code map"]
+  QA["coding-agent-harness/governance/regression<br/>regression and cadence"]
+  Integrations["coding-agent-harness/context/integrations<br/>external contracts"]
+  Planning["coding-agent-harness/planning<br/>tasks and modules"]
+  Walkthrough["coding-agent-harness/planning/tasks/<task><br/>closeout evidence"]
+  Reference["coding-agent-harness/governance/standards<br/>local operating standards"]
   Ledger["Harness Ledger / SSoTs / Lessons<br/>long-lived memory"]
 
   Entry --> Docs
@@ -98,8 +98,8 @@ The target repository can be organized in three ways:
 
 | Model | Control surface | Execution surface |
 | --- | --- | --- |
-| Single repo | The same repository owns `AGENTS.md`, `docs/`, code, tests, and closeout. | The same repository. |
-| Independent multi-repo | Each repository owns its own local `AGENTS.md` and `docs/`. | Each repository runs independently. |
+| Single repo | The same repository owns `AGENTS.md`, `coding-agent-harness/`, code, tests, and closeout. | The same repository. |
+| Independent multi-repo | Each repository owns its own local `AGENTS.md` and `coding-agent-harness/`. | Each repository runs independently. |
 | Parent-control repository | A parent repository owns the global Harness control plane. | Child repositories own implementation code and local checks. |
 
 For products split across frontend, backend, SDKs, services, and upstream references,

package/docs-release/architecture/overview.zh-CN.md

@@ -29,10 +29,10 @@ Prompt engineering 改善一次模型调用。Context engineering 改善模型
 ```mermaid
 flowchart TB
   Skill["Agent Skill<br/>SKILL.md"]
-  CLI["Harness CLI<br/>scripts/harness.mjs"]
+  CLI["Harness CLI<br/>dist/harness.mjs"]
   Standards["标准<br/>references/"]
   Templates["脚手架<br/>templates/ + templates-zh-CN/"]
-  Target["目标仓库<br/>AGENTS.md + docs/"]
+  Target["目标仓库<br/>AGENTS.md + coding-agent-harness/"]
   Scanner["扫描器与校验器<br/>status/check"]
   Dashboard["Dashboard / Workbench<br/>HTML + JSON"]
   Human["人工审查者<br/>批准与检查"]
@@ -58,15 +58,15 @@ flowchart TB
 ```mermaid
 flowchart TB
   Entry["AGENTS.md<br/>Agent 入口与路由"]
-  Registry[".harness-capabilities.json<br/>已启用能力"]
+  Registry["coding-agent-harness/harness.yaml<br/>已启用能力"]
   Docs["docs/"]
-  Architecture["03-ARCHITECTURE<br/>系统事实"]
-  Development["04-DEVELOPMENT<br/>本地设置与代码地图"]
-  QA["05-TEST-QA<br/>回归与节奏"]
-  Integrations["06-INTEGRATIONS<br/>外部契约"]
-  Planning["09-PLANNING<br/>任务与模块"]
-  Walkthrough["10-WALKTHROUGH<br/>收口证据"]
-  Reference["11-REFERENCE<br/>本地运行标准"]
+  Architecture["coding-agent-harness/context/architecture<br/>系统事实"]
+  Development["coding-agent-harness/context/development<br/>本地设置与代码地图"]
+  QA["coding-agent-harness/governance/regression<br/>回归与节奏"]
+  Integrations["coding-agent-harness/context/integrations<br/>外部契约"]
+  Planning["coding-agent-harness/planning<br/>任务与模块"]
+  Walkthrough["coding-agent-harness/planning/tasks/<task><br/>收口证据"]
+  Reference["coding-agent-harness/governance/standards<br/>本地运行标准"]
   Ledger["Harness Ledger / SSoT / Lessons<br/>长期记忆"]
 
   Entry --> Docs
@@ -89,8 +89,8 @@ flowchart TB
 
 | 模式 | 控制面 | 执行面 |
 | --- | --- | --- |
-| 单仓模式 | 同一个仓库管理 `AGENTS.md`、`docs/`、代码、测试和收口。 | 同一个仓库。 |
-| 多仓独立模式 | 每个仓库都有自己的局部 `AGENTS.md` 和 `docs/`。 | 每个仓库独立执行。 |
+| 单仓模式 | 同一个仓库管理 `AGENTS.md`、`coding-agent-harness/`、代码、测试和收口。 | 同一个仓库。 |
+| 多仓独立模式 | 每个仓库都有自己的局部 `AGENTS.md` 和 `coding-agent-harness/`。 | 每个仓库独立执行。 |
 | 主控仓库模式 | 父仓库管理全局 Harness 控制面。 | 子仓库管理实现代码和局部检查。 |
 
 如果一个产品拆成前端、后端、SDK、微服务和上游参考仓库，主控仓库模式可以把 Agent 启动入口、生成的任务生命周期 Ledger、回归状态和收口证据固定在一个地方。详见 `docs-release/guides/repository-operating-models.md` 和 `docs-release/guides/parent-control-repository-pattern.md`。

package/docs-release/architecture/system-explainer/01-system-overview.md

@@ -67,7 +67,7 @@ flowchart LR
 ```
 
 - **Package**：你 `npm install` 的那个东西，包含 CLI、模板、标准文档、Preset 包
-- **Target Repo**：你的项目，harness 在里面创建 `docs/` 文档树来记录任务状态
+- **Target Repo**：你的项目，harness 在里面创建 `coding-agent-harness/` 文档树来记录任务状态
 - **Runtime**：CLI 运行时，扫描文档树、验证合规、生成 Dashboard
 - **Human**：浏览器里看 Dashboard，在 Workbench 里做审查确认
 
@@ -85,7 +85,7 @@ Human 通过 review-confirm 再写回 Target Repo**。
 flowchart TD
   PKG["📦 Package\ncoding-agent-harness@npm"]
 
-  PKG --> CLI["harness CLI\nscripts/harness.mjs\n唯一命令入口"]
+  PKG --> CLI["harness CLI\ndist/harness.mjs\n唯一命令入口"]
   PKG --> Lib["核心库\nscripts/lib/\n~30 个模块，6 个功能层"]
   PKG --> Templates["任务模板\ntemplates/\n任务骨架文件（task_plan / visual_map 等）"]
   PKG --> References["操作标准\nreferences/\n可复制到目标仓库的规范文档"]
@@ -102,17 +102,18 @@ flowchart TD
   REPO["📁 Target Repo\n你的项目仓库"]
 
   REPO --> Entry["AGENTS.md\nAgent 入口和路由\n（告诉 Agent 去哪里找上下文）"]
-  REPO --> Caps[".harness-capabilities.json\n启用了哪些能力模块"]
-  REPO --> Docs["docs/\n文档树（harness 的工作区）"]
-
-  Docs --> Planning["09-PLANNING/\n任务目录 + 模块目录"]
-  Docs --> Ledger["Harness-Ledger.md\n全局账本（所有任务汇总）"]
-  Docs --> Walkthrough["10-WALKTHROUGH/\n收口证据和 Closeout SSoT"]
-  Docs --> Reference["11-REFERENCE/\n本地操作标准（从 Package 复制过来）"]
+  REPO --> Manifest["coding-agent-harness/harness.yaml\n启用能力和目录结构"]
+  REPO --> Harness["coding-agent-harness/\nHarness 工作区"]
+  REPO --> Docs["docs/\nReference 文档和项目标准"]
+
+  Harness --> Planning["planning/\n任务目录 + 模块目录"]
+  Harness --> Ledger["governance/generated/Harness-Ledger.md\n全局账本（所有任务汇总）"]
+  Harness --> Walkthrough["任务本地 walkthrough.md\n收口证据"]
+  Docs --> Reference["coding-agent-harness/governance/standards/\n本地操作标准（从 Package 复制过来）"]
   Docs --> Governance["01-GOVERNANCE/\nLesson 沉淀库"]
 ```
 
-每个任务对应 `docs/09-PLANNING/TASKS/<task-id>/` 下的一个目录，
+每个任务对应 `coding-agent-harness/planning/tasks/<task-id>/` 下的一个目录，
 里面有 `task_plan.md`、`progress.md`、`visual_map.md`、`review.md` 等文件。
 
 ### Runtime 做什么
@@ -137,14 +138,14 @@ Runtime 是**无状态的**——每次运行都从 Markdown 文件重新读取
 
 | 概念 | 一句话解释 | 在哪里 |
 | --- | --- | --- |
-| **Task** | 一个有生命周期的工作单元 | `docs/09-PLANNING/TASKS/<id>/` |
+| **Task** | 一个有生命周期的工作单元 | `coding-agent-harness/planning/tasks/<id>/` |
 | **Budget** | 任务复杂度：`simple` / `standard` / `complex`，决定门禁严格程度 | `task_plan.md` |
 | **Phase** | Visual Map 中的执行阶段，有状态和完成度 | `visual_map.md` |
-| **Capability** | 可选功能模块，如 `dashboard`、`adversarial-review` | `.harness-capabilities.json` |
+| **Capability** | 可选功能模块，如 `dashboard`、`module-parallel` | `coding-agent-harness/harness.yaml` |
 | **Review Gate** | 阻止任务完成的审查门禁，必须人工确认才能通过 | `INDEX.md` + `review.md` |
-| **Governance Sync** | 任务状态变更时自动更新全局账本的原子操作 | `Harness-Ledger.md` |
+| **Governance Sync** | 任务状态变更时自动更新全局账本的原子操作 | `coding-agent-harness/governance/generated/Harness-Ledger.md` |
 | **Preset** | 可复用的任务方法包，如 `legacy-migration`、`module` | `presets/<id>/` |
-| **Lesson** | 从任务中沉淀的可复用经验 | `docs/01-GOVERNANCE/lessons/` |
+| **Lesson** | 从任务中沉淀的可复用经验 | `coding-agent-harness/governance/lessons/` |
 | **Tombstone** | 软删除 / 合并 / 被取代的任务标记 | `task_plan.md` 中的特殊块 |
 | **lifecycleState** | 从任务状态 + 审查状态综合派生的队列分类 | 运行时派生，不存文件 |
 

package/docs-release/architecture/system-explainer/02-module-dependency.md

@@ -6,7 +6,7 @@
 
 ```mermaid
 flowchart LR
-  User["用户 / Agent\n$ harness <command> [target]"] -->|"解析参数 + 分发"| Entry["scripts/harness.mjs\n唯一 CLI 入口"]
+  User["用户 / Agent\n$ harness <command> [target]"] -->|"解析参数 + 分发"| Entry["dist/harness.mjs\n唯一 CLI 入口"]
 ```
 
 `harness.mjs` 做两件事：解析命令行参数，然后分发给对应的 command 模块或直接调用核心库。
@@ -18,13 +18,13 @@ flowchart LR
 
 ```mermaid
 flowchart TD
-  Entry["scripts/harness.mjs"]
+  Entry["dist/harness.mjs"]
 
-  Entry -->|"dashboard\ndev"| DashCmd["scripts/dashboard-command.mjs\nDashboard 生成 + 动态服务"]
-  Entry -->|"migrate-plan\nmigrate-run\nmigrate-verify"| MigCmd["scripts/migration-command.mjs\n迁移三阶段命令"]
-  Entry -->|"new-task / task-start\ntask-phase / task-review\ntask-complete / review-confirm\ntask-tombstone"| TaskCmd["scripts/task-command.mjs\n任务生命周期命令"]
-  Entry -->|"preset catalog\npreset install\npreset uninstall"| PresetCmd["scripts/preset-command.mjs\nPreset 管理命令"]
-  Entry -->|"check / status / init\ngovernance / lesson-promote\n..."| Core["lib/harness-core.mjs\n（直接调用）"]
+  Entry -->|"dashboard\ndev"| DashCmd["dist/commands/dashboard-command.mjs\nDashboard 生成 + 动态服务"]
+  Entry -->|"migrate-plan\nmigrate-run\nmigrate-verify"| MigCmd["dist/commands/migration-command.mjs\n迁移三阶段命令"]
+  Entry -->|"new-task / task-start\ntask-phase / task-review\ntask-complete / review-confirm\ntask-tombstone"| TaskCmd["dist/commands/task-command.mjs\n任务生命周期命令"]
+  Entry -->|"preset catalog\npreset install\npreset uninstall"| PresetCmd["dist/commands/preset-command.mjs\nPreset 管理命令"]
+  Entry -->|"check / status / init\ngovernance / lesson-promote\n..."| Core["dist/lib/harness-core.mjs\n（直接调用）"]
 ```
 
 四个 command 模块各自负责一个领域，其余命令直接调用 `harness-core.mjs`。
@@ -86,7 +86,7 @@ flowchart LR
 
 ### ② 任务扫描层
 
-负责读取 `docs/09-PLANNING/TASKS/` 下的所有文件，解析出结构化数据：
+负责读取 `coding-agent-harness/planning/tasks/` 下的所有文件，解析出结构化数据：
 
 ```mermaid
 flowchart TD

package/docs-release/architecture/system-explainer/03-task-lifecycle.md

@@ -197,7 +197,7 @@ flowchart TD
 sequenceDiagram
   participant CLI as harness CLI
   participant Lock as .harness/locks/governance-sync.lock
-  participant Ledger as docs/Harness-Ledger.md
+  participant Ledger as coding-agent-harness/governance/generated/Harness-Ledger.md
   participant Git
 
   CLI->>Lock: fs.openSync(lockPath, "wx")\n（排他写入，EEXIST 则抛错）
@@ -216,7 +216,7 @@ sequenceDiagram
 | 操作 | 触发方式 | 写入目标 | 频率 |
 | --- | --- | --- | --- |
 | `syncTaskGovernance` | 自动（每次状态变更） | `Harness-Ledger.md` 对应行 | 高频 |
-| `rebuildGovernanceIndexes` | 手动（`harness governance rebuild`） | `docs/09-PLANNING/generated/` 索引表 | 低频 |
+| `rebuildGovernanceIndexes` | 手动（`harness governance rebuild`） | `coding-agent-harness/governance/generated/` 索引表 | 低频 |
 
 ---
 
@@ -272,7 +272,7 @@ Tombstone 块追加到 `task_plan.md` 末尾（不替换原内容），保留历
 ### 为什么 Tombstone 不直接删除任务目录
 
 文档库没有数据库级外键，物理删除后会留下孤儿引用
-（Ledger、Closeout SSoT、其他任务的 `Supersedes` 字段都可能指向被删任务）。
+（Ledger、Closeout Index、其他任务的 `Supersedes` 字段都可能指向被删任务）。
 Tombstone 标记让 Soft-deleted / Superseded 队列可以只读追溯"为什么这个任务不在活跃队列里"。
 
 ### 为什么 review-confirm 需要两次 Git 提交

package/docs-release/architecture/system-explainer/04-check-and-governance.md

@@ -68,7 +68,7 @@ flowchart TD
 
 ### ① validateCapabilities
 
-读取 `.harness-capabilities.json`，检查：
+读取 `coding-agent-harness/harness.yaml`，检查：
 - 声明的能力是否都是合法的能力名（在 `allowedCapabilities` 枚举中）
 - 能力的依赖是否都已启用（如 `subagent-worker` 需要先有 `module-parallel`）
 - 能力对应的 artifact 路径是否存在
@@ -187,8 +187,8 @@ flowchart TD
   Filter --> Sort["按 id 字母序排序"]
   Sort --> Gen["生成 governance surfaces"]
 
-  Gen --> TI["docs/09-PLANNING/generated/task-index.md\n所有任务的汇总索引表"]
-  Gen --> MI["docs/09-PLANNING/generated/module-index.md\n模块步骤索引表"]
+  Gen --> TI["coding-agent-harness/governance/generated/task-index.md\n所有任务的汇总索引表"]
+  Gen --> MI["coding-agent-harness/governance/generated/module-index.md\n模块步骤索引表"]
 
   TI --> Atomic["原子写入\n（governance-sync 锁 + git commit）"]
   MI --> Atomic
@@ -207,11 +207,13 @@ flowchart TD
 
 ### 为什么检查器分 failures 和 warnings 两级
 
-两级从一开始就存在，设计动机是**迁移兼容性**：
-- 新安装的项目（`strict=true`）对缺失文件报 failure 并阻断 CI
-- 旧项目在 `safe-adoption` 模式下，同样的缺失只报 `adoption-needed: ...` warning，不阻断
+两级从一开始就存在。v2 中，活跃目标项目必须从
+`coding-agent-harness/harness.yaml` 运行：
+- v2 项目对缺失必需文件报 failure，并可阻断 CI
+- legacy 结构只作为迁移输入；先运行 `migrate-structure --plan` 和
+  `migrate-structure --apply`，再进入普通 status/check/dashboard 流程
 
-这让 harness 可以在不破坏现有用户的情况下逐步收紧规范。
+这样 active runtime 保持单一形状，同时迁移命令仍能读取旧结构并生成切换计划。
 没有考虑过三级或更多级别——两级已经足够区分"必须修复"和"建议迁移"。
 
 ### 为什么 governance 表格有时间边界

package/docs-release/architecture/system-explainer/05-data-flow.md

@@ -4,7 +4,7 @@
 
 ```mermaid
 flowchart LR
-  A["📄 Markdown 文件\n（docs/ 下的源文件）"]
+  A["📄 Markdown 文件\n（coding-agent-harness/ 下的源文件）"]
   B["⚙️ Scanner\n（解析 + 验证）"]
   C["📊 Dashboard\n（HTML + JSON）"]
 
@@ -44,7 +44,7 @@ Scanner 层（`task-scanner.mjs` + `task-review-model.mjs`）把原始 Markdown
 flowchart TD
   CT["collectTasks()"]
 
-  CT --> Discover["listTaskPlanPaths()\n扫描两个根目录：\n09-PLANNING/TASKS/\n09-PLANNING/MODULES/\n过滤模板和归档目录"]
+  CT --> Discover["listTaskPlanPaths()\n扫描两个根目录：\ncoding-agent-harness/planning/tasks/\ncoding-agent-harness/planning/modules/\n过滤模板和归档目录"]
 
   Discover --> ReadFiles["对每个任务目录读取 9 个文件\ntask_plan / brief / progress\nreview / visual_map\nexecution_strategy\nlesson_candidates / findings / context"]
 
@@ -152,13 +152,13 @@ flowchart TD
 flowchart TD
   Collect["collectMarkdownDocuments()"]
 
-  Collect --> Fixed["固定路径（存在时收集）\nHarness-Ledger.md\n09-PLANNING/Module-Registry.md\n05-TEST-QA/Regression-SSoT.md\n10-WALKTHROUGH/Closeout-SSoT.md"]
+  Collect --> Fixed["固定路径（存在时收集）\nHarness-Ledger.md\ncoding-agent-harness/planning/modules/Module-Registry.md\ncoding-agent-harness/governance/regression/Regression-SSoT.md\ncoding-agent-harness/governance/generated/Closeout-Index.md"]
 
-  Collect --> Walkthrough["10-WALKTHROUGH/ 下所有 .md\n（排除 _archive/ 和 _ 开头文件）"]
+  Collect --> Walkthrough["coding-agent-harness/planning/tasks/<task>/ 下所有 .md\n（排除 _archive/ 和 _ 开头文件）"]
 
   Collect --> TaskDocs["每个任务目录下：\nbrief / task_plan / execution_strategy\nvisual_map / lesson_candidates\nprogress / review / findings\nreferences/INDEX.md / artifacts/INDEX.md"]
 
-  Collect --> ModuleDocs["09-PLANNING/MODULES/ 下：\n每个模块的 module_plan.md\n每个模块的 brief.md"]
+  Collect --> ModuleDocs["coding-agent-harness/planning/modules/ 下：\n每个模块的 module_plan.md\n每个模块的 brief.md"]
 
   Collect --> Lessons["01-GOVERNANCE/lessons/ 下所有 .md"]
 ```

package/docs-release/architecture/system-explainer/06-preset-and-migration.md

@@ -108,7 +108,7 @@ flowchart LR
 ```
 writeScopes:
   tasks:
-    path: docs/09-PLANNING/TASKS/**
+    path: coding-agent-harness/planning/tasks/**
     access: write
 ```
 
@@ -216,8 +216,6 @@ flowchart TD
   Core --> AdvReview["adversarial-review\n对抗审查报告\n（别名：review-contract）"]
   Core --> LongRunning["long-running-task\n长时间运行任务合约"]
   Core --> Dashboard["dashboard\n本地 HTML Dashboard"]
-  Core --> SafeAdoption["safe-adoption\n旧项目平滑接入"]
-
   ModParallel --> SubagentWorker["subagent-worker\ncommit-backed worker 交接协议"]
 ```
 
@@ -231,7 +229,6 @@ flowchart TD
 | `adversarial-review` | 发布、架构、安全、数据或策略风险需要独立审查产物时 |
 | `long-running-task` | Agent 可能跨多个 loop 运行而无需每步用户确认时 |
 | `dashboard` | 需要本地只读状态可视化时 |
-| `safe-adoption` | 将 v1.0 接入已有 harness 项目而不重写历史时 |
 
 ### Level 2 — Preset 资源声明（resources）
 

package/docs-release/architecture/system-explainer/en-US/01-system-overview.md

@@ -68,7 +68,7 @@ flowchart LR
 ```
 
 - **Package**: What you `npm install` — contains the CLI, templates, standards docs, and Preset packages
-- **Target Repo**: Your project, where harness creates a `docs/` tree to record task state
+- **Target Repo**: Your project, where harness creates a `coding-agent-harness/` tree to record task state
 - **Runtime**: The CLI runtime that scans the doc tree, validates compliance, and generates the Dashboard
 - **Human**: Views the Dashboard in a browser, performs review confirmation in the Workbench
 
@@ -86,7 +86,7 @@ The whole system is a read-write loop centered on Markdown files, with no hidden
 flowchart TD
   PKG["📦 Package\ncoding-agent-harness@npm"]
 
-  PKG --> CLI["harness CLI\nscripts/harness.mjs\nSingle command entry point"]
+  PKG --> CLI["harness CLI\ndist/harness.mjs\nSingle command entry point"]
   PKG --> Lib["Core library\nscripts/lib/\n~30 modules, 6 functional layers"]
   PKG --> Templates["Task templates\ntemplates/\nTask scaffold files (task_plan / visual_map etc.)"]
   PKG --> References["Operating standards\nreferences/\nSpec docs that can be copied to target repos"]
@@ -103,17 +103,18 @@ flowchart TD
   REPO["📁 Target Repo\nYour project repository"]
 
   REPO --> Entry["AGENTS.md\nAgent entry point and routing\n(tells Agents where to find context)"]
-  REPO --> Caps[".harness-capabilities.json\nWhich capability modules are enabled"]
-  REPO --> Docs["docs/\nDoc tree (harness workspace)"]
-
-  Docs --> Planning["09-PLANNING/\nTask directory + module directory"]
-  Docs --> Ledger["Harness-Ledger.md\nGlobal ledger (all tasks summarized)"]
-  Docs --> Walkthrough["10-WALKTHROUGH/\nCloseout evidence and Closeout SSoT"]
-  Docs --> Reference["11-REFERENCE/\nLocal operating standards (copied from Package)"]
+  REPO --> Manifest["coding-agent-harness/harness.yaml\nEnabled capabilities and structure"]
+  REPO --> Harness["coding-agent-harness/\nHarness workspace"]
+  REPO --> Docs["docs/\nReference docs and project standards"]
+
+  Harness --> Planning["planning/\nTask directory + module directory"]
+  Harness --> Ledger["governance/generated/Harness-Ledger.md\nGlobal ledger (all tasks summarized)"]
+  Harness --> Walkthrough["task-local walkthrough.md\nCloseout evidence"]
+  Docs --> Reference["coding-agent-harness/governance/standards/\nLocal operating standards (copied from Package)"]
   Docs --> Governance["01-GOVERNANCE/\nLesson library"]
 ```
 
-Each task corresponds to a directory under `docs/09-PLANNING/TASKS/<task-id>/`,
+Each task corresponds to a directory under `coding-agent-harness/planning/tasks/<task-id>/`,
 containing files like `task_plan.md`, `progress.md`, `visual_map.md`, `review.md`, etc.
 
 ### What the Runtime does
@@ -138,14 +139,14 @@ caching no intermediate state (except file watching in `harness dev`).
 
 | Concept | One-line explanation | Where |
 | --- | --- | --- |
-| **Task** | A unit of work with a lifecycle | `docs/09-PLANNING/TASKS/<id>/` |
+| **Task** | A unit of work with a lifecycle | `coding-agent-harness/planning/tasks/<id>/` |
 | **Budget** | Task complexity: `simple` / `standard` / `complex`, determines gate strictness | `task_plan.md` |
 | **Phase** | An execution phase in the Visual Map, with state and completion | `visual_map.md` |
-| **Capability** | Optional feature module, e.g. `dashboard`, `adversarial-review` | `.harness-capabilities.json` |
+| **Capability** | Optional feature module, e.g. `dashboard`, `module-parallel` | `coding-agent-harness/harness.yaml` |
 | **Review Gate** | A review gate that blocks task completion, requires human confirmation to pass | `review.md` |
-| **Governance Sync** | Atomic operation that auto-updates the global ledger on task state changes | `Harness-Ledger.md` |
+| **Governance Sync** | Atomic operation that auto-updates the global ledger on task state changes | `coding-agent-harness/governance/generated/Harness-Ledger.md` |
 | **Preset** | A reusable task method package, e.g. `legacy-migration`, `module` | `presets/<id>/` |
-| **Lesson** | Reusable knowledge distilled from a task | `docs/01-GOVERNANCE/lessons/` |
+| **Lesson** | Reusable knowledge distilled from a task | `coding-agent-harness/governance/lessons/` |
 | **Tombstone** | Marker for soft-deleted / merged / superseded tasks | Special block in `task_plan.md` |
 | **lifecycleState** | Queue classification derived from task state + review state combined | Derived at runtime, not stored in files |
 

package/docs-release/architecture/system-explainer/en-US/02-module-dependency.md

@@ -6,7 +6,7 @@ All commands come through a single file:
 
 ```mermaid
 flowchart LR
-  User["User / Agent\n$ harness <command> [target]"] -->|"parse args + dispatch"| Entry["scripts/harness.mjs\nSingle CLI entry point"]
+  User["User / Agent\n$ harness <command> [target]"] -->|"parse args + dispatch"| Entry["dist/harness.mjs\nSingle CLI entry point"]
 ```
 
 `harness.mjs` does two things: parses command-line arguments, then dispatches to the
@@ -19,13 +19,13 @@ It contains no business logic itself.
 
 ```mermaid
 flowchart TD
-  Entry["scripts/harness.mjs"]
+  Entry["dist/harness.mjs"]
 
-  Entry -->|"dashboard\ndev"| DashCmd["scripts/dashboard-command.mjs\nDashboard generation + dynamic serving"]
-  Entry -->|"migrate-plan\nmigrate-run\nmigrate-verify"| MigCmd["scripts/migration-command.mjs\nMigration three-phase commands"]
-  Entry -->|"new-task / task-start\ntask-phase / task-review\ntask-complete / review-confirm\ntask-tombstone"| TaskCmd["scripts/task-command.mjs\nTask lifecycle commands"]
-  Entry -->|"preset catalog\npreset install\npreset uninstall"| PresetCmd["scripts/preset-command.mjs\nPreset management commands"]
-  Entry -->|"check / status / init\ngovernance / lesson-promote\n..."| Core["lib/harness-core.mjs\n(called directly)"]
+  Entry -->|"dashboard\ndev"| DashCmd["dist/commands/dashboard-command.mjs\nDashboard generation + dynamic serving"]
+  Entry -->|"migrate-plan\nmigrate-run\nmigrate-verify"| MigCmd["dist/commands/migration-command.mjs\nMigration three-phase commands"]
+  Entry -->|"new-task / task-start\ntask-phase / task-review\ntask-complete / review-confirm\ntask-tombstone"| TaskCmd["dist/commands/task-command.mjs\nTask lifecycle commands"]
+  Entry -->|"preset catalog\npreset install\npreset uninstall"| PresetCmd["dist/commands/preset-command.mjs\nPreset management commands"]
+  Entry -->|"check / status / init\ngovernance / lesson-promote\n..."| Core["dist/lib/harness-core.mjs\n(called directly)"]
 ```
 
 Four command modules each own one domain; other commands call `harness-core.mjs` directly.
@@ -89,7 +89,7 @@ foundation that lets the whole system derive state from Markdown files.
 
 ### ② Task scanning layer
 
-Responsible for reading all files under `docs/09-PLANNING/TASKS/` and parsing them into
+Responsible for reading all files under `coding-agent-harness/planning/tasks/` and parsing them into
 structured data:
 
 ```mermaid

package/docs-release/architecture/system-explainer/en-US/03-task-lifecycle.md

@@ -204,7 +204,7 @@ Every task state change triggers `syncTaskGovernance()`, which atomically update
 sequenceDiagram
   participant CLI as harness CLI
   participant Lock as .harness/locks/governance-sync.lock
-  participant Ledger as docs/Harness-Ledger.md
+  participant Ledger as coding-agent-harness/governance/generated/Harness-Ledger.md
   participant Git
 
   CLI->>Lock: fs.openSync(lockPath, "wx")\n(exclusive write, throws EEXIST if exists)
@@ -223,7 +223,7 @@ filesystem operation. If the file already exists, `openSync` throws `EEXIST` and
 | Operation | How triggered | Write target | Frequency |
 | --- | --- | --- | --- |
 | `syncTaskGovernance` | Automatic (on every state change) | Corresponding row in `Harness-Ledger.md` | High frequency |
-| `rebuildGovernanceIndexes` | Manual (`harness governance rebuild`) | `docs/09-PLANNING/generated/` index tables | Low frequency |
+| `rebuildGovernanceIndexes` | Manual (`harness governance rebuild`) | `coding-agent-harness/governance/generated/` index tables | Low frequency |
 
 ---
 
@@ -283,7 +283,7 @@ governance concern be tracked independently.
 ### Why Tombstone doesn't physically delete the task directory
 
 The document library has no database-level foreign keys. Physical deletion would leave
-orphan references (the Ledger, Closeout SSoT, and other tasks' `Supersedes` fields may
+orphan references (the Ledger, Closeout Index, and other tasks' `Supersedes` fields may
 all point to the deleted task). Tombstone markers let the Soft-deleted / Superseded queue
 provide read-only traceability for "why isn't this task in the active queue".
 

package/docs-release/architecture/system-explainer/en-US/04-check-and-governance.md

@@ -70,7 +70,7 @@ Each validator returns `failures` (hard failures, must fix) and `warnings` (soft
 
 ### ① validateCapabilities
 
-Reads `.harness-capabilities.json` and checks:
+Reads `coding-agent-harness/harness.yaml` and checks:
 - Whether declared capabilities are all valid capability names (in the `allowedCapabilities` enum)
 - Whether capability dependencies are all enabled (e.g. `subagent-worker` requires `module-parallel` first)
 - Whether the artifact paths corresponding to capabilities exist
@@ -192,8 +192,8 @@ flowchart TD
   Filter --> Sort["Sort alphabetically by id"]
   Sort --> Gen["Generate governance surfaces"]
 
-  Gen --> TI["docs/09-PLANNING/generated/task-index.md\nSummary index table for all tasks"]
-  Gen --> MI["docs/09-PLANNING/generated/module-index.md\nModule step index table"]
+  Gen --> TI["coding-agent-harness/governance/generated/task-index.md\nSummary index table for all tasks"]
+  Gen --> MI["coding-agent-harness/governance/generated/module-index.md\nModule step index table"]
 
   TI --> Atomic["Atomic write\n(governance-sync lock + git commit)"]
   MI --> Atomic
@@ -214,12 +214,14 @@ full scan on every state change.
 
 ### Why the validator has two levels: failures and warnings
 
-Both levels existed from the start. The design motivation was **migration compatibility**:
-- Newly installed projects (`strict=true`) report failure for missing files and block CI
-- Legacy projects in `safe-adoption` mode report the same missing files as
-  `adoption-needed: ...` warnings without blocking
+Both levels existed from the start. In v2, active target projects are expected to
+run from `coding-agent-harness/harness.yaml`:
+- v2 projects report failures for missing required files and can block CI
+- legacy structures are migration input only; use `migrate-structure --plan` and
+  `migrate-structure --apply` before running normal status/check/dashboard flows
 
-This lets harness gradually tighten standards without breaking existing users.
+This keeps active runtime behavior single-shaped while still giving migration
+commands enough information to produce a cutover plan.
 Three or more levels were never considered — two levels are sufficient to distinguish
 "must fix" from "recommended migration".
 

package/docs-release/architecture/system-explainer/en-US/05-data-flow.md

@@ -4,7 +4,7 @@
 
 ```mermaid
 flowchart LR
-  A["📄 Markdown files\n(source files under docs/)"]
+  A["📄 Markdown files\n(source files under coding-agent-harness/)"]
   B["⚙️ Scanner\n(parse + validate)"]
   C["📊 Dashboard\n(HTML + JSON)"]
 
@@ -45,7 +45,7 @@ into structured objects.
 flowchart TD
   CT["collectTasks()"]
 
-  CT --> Discover["listTaskPlanPaths()\nScans two root directories:\n09-PLANNING/TASKS/\n09-PLANNING/MODULES/\nFilters out template and archive directories"]
+  CT --> Discover["listTaskPlanPaths()\nScans two root directories:\ncoding-agent-harness/planning/tasks/\ncoding-agent-harness/planning/modules/\nFilters out template and archive directories"]
 
   Discover --> ReadFiles["For each task directory, reads 9 files:\ntask_plan / brief / progress\nreview / visual_map\nexecution_strategy\nlesson_candidates / findings / context"]
 
@@ -155,13 +155,13 @@ Which files `collectMarkdownDocuments()` collects:
 flowchart TD
   Collect["collectMarkdownDocuments()"]
 
-  Collect --> Fixed["Fixed paths (collected when they exist)\nHarness-Ledger.md\n09-PLANNING/Module-Registry.md\n05-TEST-QA/Regression-SSoT.md\n10-WALKTHROUGH/Closeout-SSoT.md"]
+  Collect --> Fixed["Fixed paths (collected when they exist)\nHarness-Ledger.md\ncoding-agent-harness/planning/modules/Module-Registry.md\ncoding-agent-harness/governance/regression/Regression-SSoT.md\ncoding-agent-harness/governance/generated/Closeout-Index.md"]
 
-  Collect --> Walkthrough["All .md files under 10-WALKTHROUGH/\n(excluding _archive/ and files starting with _)"]
+  Collect --> Walkthrough["All .md files under coding-agent-harness/planning/tasks/<task>/\n(excluding _archive/ and files starting with _)"]
 
   Collect --> TaskDocs["Under each task directory:\nbrief / task_plan / execution_strategy\nvisual_map / lesson_candidates\nprogress / review / findings\nreferences/INDEX.md / artifacts/INDEX.md"]
 
-  Collect --> ModuleDocs["Under 09-PLANNING/MODULES/:\nmodule_plan.md for each module\nbrief.md for each module"]
+  Collect --> ModuleDocs["Under coding-agent-harness/planning/modules/:\nmodule_plan.md for each module\nbrief.md for each module"]
 
   Collect --> Lessons["All .md files under 01-GOVERNANCE/lessons/"]
 ```

package/docs-release/architecture/system-explainer/en-US/06-preset-and-migration.md

@@ -115,7 +115,7 @@ Each entrypoint also declares `writes` (allowed write path globs) and `reads`
 ```
 writeScopes:
   tasks:
-    path: docs/09-PLANNING/TASKS/**
+    path: coding-agent-harness/planning/tasks/**
     access: write
 ```
 
@@ -225,8 +225,6 @@ flowchart TD
   Core --> AdvReview["adversarial-review\nAdversarial review reports\n(alias: review-contract)"]
   Core --> LongRunning["long-running-task\nLong-running task contracts"]
   Core --> Dashboard["dashboard\nLocal HTML Dashboard"]
-  Core --> SafeAdoption["safe-adoption\nSmooth onboarding for legacy projects"]
-
   ModParallel --> SubagentWorker["subagent-worker\nCommit-backed worker handoff protocol"]
 ```
 
@@ -240,7 +238,6 @@ flowchart TD
 | `adversarial-review` | When release, architecture, security, data, or policy risks require independent review artifacts |
 | `long-running-task` | When Agents may run across multiple loops without per-step user confirmation |
 | `dashboard` | When local read-only state visualization is needed |
-| `safe-adoption` | When onboarding v1.0 into an existing harness project without rewriting history |
 
 ### Level 2 — Preset resource declarations (resources)