@tea-agent/loop-agent 0.2.0 → 0.3.0

package/docs/README.md

@@ -1,62 +1,67 @@
-# Documentation Index
+# 文档索引
 
-`docs/` is the governance root for loop-agent. It contains workflow rules, methodology, verification rules, execution plans, reports, progress logs, decisions, and reusable templates.
+`docs/` 是 loop-agent 的治理根目录，包含工作流规则、方法论、验证规则、执行计划、报告、进度日志、决策记录和可复用模板。
 
-Top-level `AGENTS.md` is the operating map. Durable knowledge belongs here: decisions, contracts, plans, verification evidence, debugging notes, and reusable process rules should be recorded under `docs/` instead of staying only in chat.
+顶层 `AGENTS.md` 是操作地图。长期知识应落在此处：决策、契约、计划、验证证据、调试笔记和可复用流程规则应记录在 `docs/` 下，而不是只留在聊天里。
 
-## Core Documents
+## 核心文档
 
-- `development-principles.md` — repository development principles
-- `architecture/runtime-boundaries.md` — runtime layer boundaries and dependency direction
-- `feature-workflow.md` — bounded feature workflow
-- `verification-matrix.md` — verification command selection
-- `loop-agent-harness.md` — runtime and command surface overview
-- `agent-dag-runner.md` — Agent DAG runner guide
-- `cursor-executor-usage.md` — Cursor executor usage
-- `dynamic-workflow-dag-engine-roadmap.md` — Dynamic Workflow DAG Engine roadmap and fit analysis
+- `development-principles.md` — 仓库开发原则
+- `architecture/runtime-boundaries.md` — runtime 层边界与依赖方向
+- `feature-workflow.md` — 有边界的功能工作流
+- `verification-matrix.md` — 验证命令选择
+- `production-readiness.md` — Production Readiness v0.1 范围、证据与 DAG hardening 标准
+- `loop-agent-harness.md` — runtime 与 command surface 概览
+- `agent-dag-runner.md` — Agent DAG runner 指南
+- `cursor-executor-usage.md` — Cursor executor 用法
+- `dynamic-workflow-dag-engine-roadmap.md` — Dynamic Workflow DAG Engine 路线图与适配分析
+- `init-surface.manifest.json` — npm 包范围、目标项目初始化投影与 `init check-update` surface 分类的机器校验契约
 
-## Methodology
+## 方法论
 
-- `harness-methodology-tdd.md` — TDD discipline for behavior changes and bug fixes
-- `harness-methodology-verification.md` — verification discipline before completion claims
-- `harness-methodology-debugging.md` — systematic debugging workflow before fixes
+- `harness-methodology-tdd.md` — 行为变更与 bug 修复的 TDD 纪律
+- `harness-methodology-verification.md` — 完成声明前的验证纪律
+- `harness-methodology-debugging.md` — 修复前的系统化调试工作流
 
-## Artifacts
+## 产物目录
 
-- `design/README.md` — draft design notes and implementation contracts
-- `exec-plans/active/README.md` — active execution plans
-- `exec-plans/completed/README.md` — completed execution plans
-- `progress/README.md` — progress handoff logs
-- `reports/README.md` — verification and audit reports
-- `decisions/README.md` — architecture decisions
-- `templates/` — reusable planning, reporting, and DAG templates
+- `design/README.md` — 设计草稿与实现契约
+- `exec-plans/active/README.md` — 进行中的执行计划
+- `exec-plans/completed/README.md` — 已完成的执行计划
+- `progress/README.md` — 进度交接日志
+- `reports/README.md` — 验证与审计报告
+- `decisions/README.md` — 架构决策
+- `skills/README.md` — repo-local skill registry and vetting notes
+- `templates/` — 可复用的规划、报告与 DAG 模板
 
-## Repository Skills
+## 仓库 Skills
 
-- `../skills/loop-agent/` — loop-agent's own skill instructions and references.
-- Each additional skill uses its own subdirectory under repository-root `../skills/`; these local copies are referenced by DAG templates so maintenance does not depend on external agent skill directories.
+- `../skills/loop-agent/` — loop-agent 自身的 skill 指令与参考资料
+- 每个额外 skill 在仓库根 `../skills/` 下使用独立子目录；这些本地副本由 DAG 模板引用，维护不依赖外部 agent skill 目录
 
-## Templates
+## 模板
 
-- `templates/project-start-checklist.md` — pre-work checklist
-- `templates/feature-spec.md` — bounded feature specification
-- `templates/sprint-contract.md` — implementation contract and acceptance criteria
-- `templates/exec-plan.md` — execution plan for non-trivial work
-- `templates/progress-log.md` — progress and handoff log
-- `templates/qa-report.md` — verification and QA evidence
-- `templates/adr.md` — architecture decision record
+- `templates/project-start-checklist.md` — 开工前检查清单
+- `templates/feature-spec.md` — 有边界的功能规格
+- `templates/sprint-contract.md` — 实现契约与验收标准
+- `templates/exec-plan.md` — 非平凡工作的执行计划
+- `templates/progress-log.md` — 进度与交接日志
+- `templates/qa-report.md` — 验证与 QA 证据
+- `templates/production-readiness-checklist.md` — 低/中风险单仓库 DAG readiness 检查清单
+- `templates/init-evolution-review.md` — 初始化能力演化审查报告模板
+- `templates/adr.md` — 架构决策记录（ADR）
 
-## Maintenance
+## 维护
 
-After docs changes, run:
-
-```bash
-bash scripts/check-repo.sh
-```
-
-On Windows, run Bash scripts through Git Bash or a configured compatible Bash. Use platform-native paths for actual file operations; reserve `/` for repo refs, JSON/Markdown evidence refs, and glob conventions.
-
-For a full local gate, run:
+文档变更后运行：
+
+```bash
+bash scripts/check-repo.sh
+```
+
+Windows 上通过 Git Bash 或已配置的兼容 Bash 运行脚本。实际文件操作使用平台原生路径；`/` 仅用于 repo 引用、JSON/Markdown 证据引用和 glob 约定。
+
+完整本地门禁：
 
 ```bash
 bash scripts/ci.sh

package/docs/agent-dag-recovery-playbook.md

@@ -1,4 +1,4 @@
-# Agent DAG Recovery Playbook
+# Agent DAG Recovery Playbook（恢复手册）
 
 > **关联**：[`agent-dag-runner.md`](agent-dag-runner.md)（CLI 与 run 语义）· [`templates/agent-dag-decision-gate.prompt.md`](templates/agent-dag-decision-gate.prompt.md)（Decision Gate 消费 recovery 证据）
 
@@ -6,6 +6,17 @@
 
 Agent DAG **recovery planning 是只读、派生、advisory** 的。`dag report` 与 `buildDagDecisionGateEvidence()` 从 `.harness/dag-runs/` 的 canonical facts 聚合 `normalizedFailureCategory` → `recoveryRecommendation`，供人工或 Decision Gate prompt 消费。
 
+Production Readiness v0.1 在 normalized DAG category 之上增加 product-line routing。Report 与 doctor 输出应保留 raw DAG fact 并派生，不重写已完成 facts：
+
+```text
+raw_failure_category
+dag_normalized_failure_category
+product_line_failure_category
+recommended_follow_up
+```
+
+Product-line taxonomy 定义见 `design/state-and-failure-taxonomy.md`。
+
 **非目标（本 playbook 不覆盖、runner 不实现）：**
 
 - 自动 retry / resume 节点执行
@@ -47,7 +58,7 @@ npm run dev -- dag decision inspect --run-id <run-id> [--node-id <node-id>]
 npm run dev -- dag decision validate --run-id <run-id> [--node-id <node-id>]
 ```
 
-### Paused run 操作员路径
+### Paused run operator 路径
 
 1. `dag report --paused-latest --json` 或 `dag doctor` — 定位最新 paused run 与 `primaryRecovery`
 2. `dag status --run-id <id>` — 读 `approvalFlow`、`escalationArtifactPath`、`pendingNodes`
@@ -79,7 +90,22 @@ Decision Gate prompt 侧：`buildDagDecisionGateEvidence()`（`./src/core/dag-de
 | `inspect-upstream` | 先查上游失败 | SKIPPED 下游节点 |
 | `unknown` | 未映射类别（不应出现在正常派生路径） | 内部兜底 |
 
-## 类别 → 动作 → 操作员指引
+## Product-Line Routing v0.1
+
+| Product-line category | Default follow-up |
+|---|---|
+| `SpecUnclear` | `spec-clarification` |
+| `ContractMismatch` | `architecture-contract-fix` |
+| `ProductBug` | `dev-fix` |
+| `TestBug` | `qa-fix-test` |
+| `EnvFailure` | `env-fix` 或 retry verify |
+| `FlakyTest` | `flaky-test-analysis` |
+| `RiskyChange` | `human-review` / `architecture-review` |
+| `DependencyFailure` | unblock dependency |
+| `NeedsHuman` | `human-review` |
+| `Unknown` | human triage |
+
+## 类别 → 动作 → operator 指引
 
 | Normalized category | Recovery action | Operator guidance | Anti-patterns |
 |---------------------|-----------------|-------------------|---------------|
@@ -107,9 +133,9 @@ Decision Gate prompt 侧：`buildDagDecisionGateEvidence()`（`./src/core/dag-de
 1. **Primary Failure** — `primaryFailure`（node 或 run scope）
 2. **Recovery Action** — `primaryRecovery`（action、summary、reason、flags、commandHint）
 3. **Blocked Downstream / Skipped Nodes** — `downstreamSkippedNodes`
-4. **Recommended Operator Action** — 面向操作员的步骤摘要
+4. **Recommended Operator Action** — 面向 operator 的步骤摘要
 
-保存 handoff 时重定向到平台临时目录或 `docs/reports/`，不要写入 `.harness/dag-runs/`。
+保存 handoff 时重定向到平台临时目录或 `docs/reports/`，不要写入 `.harness/dag-runs/`。
 
 ## Decision Gate 消费约定
 
@@ -123,7 +149,7 @@ Decision Gate prompt 侧：`buildDagDecisionGateEvidence()`（`./src/core/dag-de
 
 `dag doctor` 与 `dag status` 通过 `detectDagRunHealthIssues()` 检测 lifecycle 不一致，**不** mutate run facts。
 
-| Code | 典型场景 | 操作员指引 |
+| Code | 典型场景 | operator 指引 |
 |------|----------|------------|
 | `terminal-in-active` | run 已完成但 `active/<run-id>/` 残留 | 对照 `completed/` canonical facts；手动 archive 或删除 stale 目录 |
 | `paused-in-active` | pause 后目录未迁至 `paused/` | `dag doctor` 诊断；修复 facts 后再 approve/resume |

package/docs/agent-dag-runner.md

@@ -1,40 +1,42 @@
 # Agent DAG Runner
 
-Agent DAG is loop-agent's declarative orchestration runtime. A DAG decomposes work into nodes, runs eligible ranks in order, records artifacts, and uses gates for review and verification.
+Agent DAG 是 loop-agent 的声明式编排 runtime。DAG 将工作拆为节点、按序执行 eligible ranks、记录 artifacts，并用 gate 做 review 与验证。
 
-## Basic Use
+## 基本用法
 
 ```bash
-loop-agent dag run-task <task-id> --profile auto --strict-models --output <temp-dir>/<task-id>-dag.json
-loop-agent dag validate --dag <temp-dir>/<task-id>-dag.json --strict-models --strict-governance
-loop-agent run-dag --dag <temp-dir>/<task-id>-dag.json --cwd .
-```
-
-`<temp-dir>` is the platform-native temp directory. On Windows, pass native paths for actual `--output`, `--dag`, and `--cwd` values.
+loop-agent dag run-task <task-id> --profile auto --strict-models --output <temp-dir>/<task-id>-dag.json
+loop-agent dag validate --dag <temp-dir>/<task-id>-dag.json --strict-models --strict-governance
+loop-agent run-dag --dag <temp-dir>/<task-id>-dag.json --cwd .
+```
+
+`<temp-dir>` 为平台原生临时目录。Windows 上 `--output`、`--dag`、`--cwd` 的实际值用原生路径。
 
 ## Executors
 
-- `static`: deterministic generated artifacts or notes
-- `shell`: verification and file-system checks
-- `pi`: planning, review, diagnosis, and bounded writing when a node sets `toolProfile: "write"`
-- `cursor`: optional bounded write backend when explicitly enabled
+- `static`：确定性生成的 artifacts 或 notes
+- `shell`：验证与文件系统检查
+- `pi`：规划、review、诊断；节点设 `toolProfile: "write"` 时有界写入
+- `cursor`：显式启用时的可选有界写后端
 
 ## Skills
 
-DAG specs may declare `defaults.skills`, `skillsByRole`, and node-level `skills`. The runner resolves local instructions from `skills/<skill-name>/SKILL.md` and records resolution metadata in each node's `skills.json` artifact.
+DAG spec 可声明 `defaults.skills`、`skillsByRole` 与节点级 `skills`。Runner 从 `skills/<skill-name>/SKILL.md` 解析本地指令，并在各节点 `skills.json` artifact 中记录解析元数据。
+
+执行前可用 `dag validate --strict-skills` 做 opt-in skill audit；该门禁会在 missing/error/truncated skill 或 unresolved reference 出现时失败。默认 role skill 应来自 `docs/skills/vetted-skill-registry.md` 中记录的 repo-local wrapper。
 
-The `loop-agent` skill lives at `skills/loop-agent/SKILL.md`. The legacy root `skill/SKILL.md` path is retained only as a compatibility fallback for older worktrees.
+`loop-agent` skill 位于 `skills/loop-agent/SKILL.md`。遗留根路径 `skill/SKILL.md` 仅为旧 worktree 保留兼容 fallback。
 
 ## Artifacts
 
-DAG artifacts belong under:
+DAG artifacts 位于：
 
 ```text
 .harness/dag-runs/<state>/<run-id>/artifacts/<node-id>/
 ```
 
-Root `artifacts/` is not a valid default DAG artifact location.
+根目录 `artifacts/` 不是有效的默认 DAG artifact 位置。
 
 ## Shell Gates
 
-- `shell.verdictGate` reads `$HARNESS_DAG_RUN_DIR/<fromNodeId>.json` from the injected current run directory; 不应自行发现 active run paths.
+- `shell.verdictGate` 从注入的当前 run 目录读取 `$HARNESS_DAG_RUN_DIR/<fromNodeId>.json`；不应自行发现 active run paths。

package/docs/architecture/runtime-boundaries.md

@@ -112,7 +112,7 @@ Runner / Loop         ──(迁移中)──>  逐步改为仅经 Store / Appli
 
 `scripts/check-architecture-boundaries.sh` 的 transitional allowlist 保持为空。任何新增的 `workflows/executors -> commands` import 必须导致检查 **exit 1**；如果未来确有临时例外，必须先写入 active exec plan，说明移除时间和验证门禁。
 
-## Governance hooks
+## Governance 钩子
 
 以下脚本由 `scripts/check-repo.sh` 调用（Phase 0 起）：
 

package/docs/cursor-executor-usage.md

@@ -1,8 +1,8 @@
-# Cursor Executor Usage
+# Cursor Executor 用法
 
-Cursor is used for bounded write implementation. Every Cursor write task must define scope explicitly.
+Cursor 用于有界写实现。每个 Cursor 写任务必须显式定义 scope。
 
-## Required Prompt Fields
+## Prompt 必填字段
 
 - task id
 - objective
@@ -10,7 +10,7 @@ Cursor is used for bounded write implementation. Every Cursor write task must de
 - forbidden paths
 - constraints
 - expected verification
-- instruction to preserve unrelated changes
+- 保留无关变更的指令
 
 ## One-Shot Helper
 
@@ -22,4 +22,4 @@ loop-agent cursor-prompt \
   "<bounded task prompt>"
 ```
 
-After Cursor returns, the main session must inspect the diff and run the relevant verification commands.
+Cursor 返回后，主会话必须检查 diff 并运行相关验证命令。

package/docs/decisions/README.md

@@ -1,3 +1,3 @@
-# Decisions
+# 决策
 
-Use this directory for architecture decision records.
+本目录存放架构决策记录（ADR）。

package/docs/design/README.md

@@ -1,36 +1,36 @@
-# Design Notes
+# 设计笔记
 
-`docs/design/` contains planning notes for using `loop-agent` as the repo-local runtime inside a larger product-line agent platform. These documents are design inputs, not proof that the capability already exists in `src/`.
+`docs/design/` 存放将 `loop-agent` 作为更大产品线 agent 平台内仓库本地 runtime 的规划笔记。这些是设计输入，不是 `src/` 已具备该能力的证明。
 
-## Documents
+## 文档
 
-| Document | Purpose |
+| 文档 | 用途 |
 |---|---|
-| `产品线共享知识库.md` | Product-line docs repository as the upstream source of truth |
-| `研发模式.md` | 10-working-day Feature team workflow |
-| `1个月规划.md` | First-month landing plan |
-| `1月wbs.md` | First-month WBS and ownership |
-| `六个月规划.md` | Six-month roadmap and target architecture |
-| `taskspec-to-loop-agent-mapping.md` | Contract for adapting product-line TaskSpec into `loop-agent` tasks |
-| `state-and-failure-taxonomy.md` | Canonical status and failure taxonomy across docs, Task Pool, DAG, and Loop |
+| `产品线共享知识库.md` | 产品线文档仓库作为上游事实源 |
+| `研发模式.md` | 10 个工作日 Feature 团队工作流 |
+| `1个月规划.md` | 首月落地计划 |
+| `1月wbs.md` | 首月 WBS 与分工 |
+| `六个月规划.md` | 六个月路线图与目标架构 |
+| `taskspec-to-loop-agent-mapping.md` | 将产品线 TaskSpec 适配为 `loop-agent` task 的契约 |
+| `state-and-failure-taxonomy.md` | 文档、Task Pool、DAG、Loop 共用的 canonical status 与 failure taxonomy |
 
-## Current Implementation Boundary
+## 当前实现边界
 
-`loop-agent` currently owns a repo-local harness, Agent DAG generation/validation/execution, shell verification, artifacts, reports, and Loop state. It is not the product-line Task Pool, Orchestrator, docs-sync service, Git/CI platform, or artifact store.
+`loop-agent` 当前拥有：仓库本地 harness、Agent DAG 生成/验证/执行、shell 验证、artifacts、reports、Loop state。它不是产品线 Task Pool、Orchestrator、docs-sync 服务、Git/CI 平台或 artifact store。
 
-The design documents use two kinds of profile names:
+设计文档使用两类 profile 名称：
 
-- Business task profiles: `backend-feature`, `frontend-feature`, `qa-casegen`, `qa-testcode`, `reviewer-gate`.
-- `loop-agent dag run-task --profile` governance profiles: `auto`, `minimal`, `standard`, `reviewed`, `supervised`.
+- **Business task profiles**：`backend-feature`、`frontend-feature`、`qa-casegen`、`qa-testcode`、`reviewer-gate`
+- **`loop-agent dag run-task --profile` governance profiles**：`auto`、`minimal`、`standard`、`reviewed`、`supervised`
 
-Do not pass business task profiles directly to `loop-agent dag run-task --profile` unless the CLI is explicitly extended to support them. Use `taskspec-to-loop-agent-mapping.md` to route business profiles to current governance profiles.
+除非 CLI 显式扩展支持，否则不要把 business task profile 直接传给 `loop-agent dag run-task --profile`。用 `taskspec-to-loop-agent-mapping.md` 将 business profile 路由到当前 governance profile。
 
-## Maintenance Rules
+## 维护规则
 
-When these design notes change:
+设计笔记变更时：
 
-1. Keep TaskSpec fields, status names, failure categories, and command examples consistent with the contract docs.
-2. Mark future platform components as target architecture unless they exist in `src/` or `scripts/`.
-3. Update `taskspec-to-loop-agent-mapping.md` whenever `src/task/config-types.ts` or DAG profile routing changes.
-4. Update `state-and-failure-taxonomy.md` whenever DAG report categories, Loop failure classes, or Task Pool states change.
-5. Run `bash scripts/check-repo.sh`.
+1. 保持 TaskSpec 字段、status 名称、failure category 与命令示例与契约文档一致
+2. 未来平台组件标为目标架构，除非已存在于 `src/` 或 `scripts/`
+3. `src/task/config-types.ts` 或 DAG profile routing 变更时更新 `taskspec-to-loop-agent-mapping.md`
+4. DAG report category、Loop failure class 或 Task Pool state 变更时更新 `state-and-failure-taxonomy.md`
+5. 运行 `bash scripts/check-repo.sh`

package/docs/development-principles.md

@@ -1,71 +1,71 @@
-# Development Principles
+# 开发原则
 
-loop-agent is a workflow runtime for agentic coding work. The repository should stay small, explicit, and verifiable.
+loop-agent 是面向 agentic coding 的工作流 runtime。仓库应保持小而显式、可验证。
 
-## Operating Stance
+## 操作立场
 
-The project uses a human-led, agent-executed engineering model. Agents may implement, verify, and summarize, but durable intent and completion evidence must live in the repository.
+项目采用「人类掌舵、智能体执行」的工程模型。Agent 可实现、验证与总结，但持久意图与完成证据必须落在仓库中。
 
-- The repository is the record system. Decisions, contracts, plans, tests, reports, and handoffs belong in tracked files.
-- `AGENTS.md` is an operating map, not a knowledge dump. Long-lived methodology and decisions belong under `docs/`.
-- Work advances in small, reversible, verifiable increments.
-- Baseline verification comes before new work when the current state is uncertain.
-- Completion is defined by fresh evidence, not by intent or confidence.
+- 仓库是记录系统。决策、契约、计划、测试、报告与交接属于 tracked files。
+- `AGENTS.md` 是操作地图，不是知识 dump。长期方法论与决策属于 `docs/`。
+- 工作以小步、可逆、可验证的增量推进。
+- 状态不确定时，先跑基线验证再开新工。
+- 完成由新鲜证据定义，而非意图或信心。
 
-## Principles
+## 原则
 
-1. One task advances one bounded work block.
-2. Search existing code, docs, scripts, and tests before designing new behavior.
-3. Shell verification is the completion authority.
-4. Runtime state belongs in `.harness/`; durable decisions belong in `docs/`.
-5. Pi writer nodes and optional Cursor write execution must be bounded by explicit allowed and forbidden paths.
-6. Pi review/planning paths are advisory unless followed by deterministic verification.
-7. Repeated constraints should become docs, tests, scripts, checks, or templates.
-8. Do not keep hidden process state only in chat.
-9. Do not add placeholders as completed implementation.
-10. Prefer existing local patterns before adding new abstractions.
+1. 一次任务只推进一个有边界的工作块。
+2. 设计新行为前先搜索现有代码、文档、脚本与测试。
+3. Shell 验证是完成权威。
+4. Runtime 状态在 `.harness/`；持久决策在 `docs/`。
+5. Pi writer 节点与可选 Cursor 写执行必须由显式 allowed/forbidden paths 约束。
+6. Pi review/planning 路径是 advisory，除非后跟确定性验证。
+7. 反复出现的约束应固化为文档、测试、脚本、检查或模板。
+8. 不要把隐藏流程状态只留在聊天里。
+9. 不要把占位实现当作已完成交付。
+10. 新增抽象前先沿用现有局部模式。
 
-## Repository Shape
+## 仓库结构
 
-- Source lives in `src/`.
-- Tests live in `test/`.
-- Skill instructions live in `skills/`.
-- Verification and maintenance scripts live in `scripts/`.
-- Governance and handoff artifacts live in `docs/`.
+- 源码：`src/`
+- 测试：`test/`
+- Skill 指令：`skills/`
+- 验证与维护脚本：`scripts/`
+- 治理与交接产物：`docs/`
 
-## Change Discipline
+## 变更纪律
 
-For behavior changes, update tests. For workflow or command changes, update docs and examples. For governance changes, update `harness.json` and the relevant check scripts.
+行为变更要更新测试；工作流或命令变更要更新文档与示例；治理变更要更新 `harness.json` 与相关检查脚本。
 
-When work affects requirements, behavior, cross-command contracts, or harness rules, update the corresponding durable artifact:
+当工作影响需求、行为、跨命令契约或 harness 规则时，更新对应持久产物：
 
-- design or contract docs for changed expectations
-- tests or verification scripts for changed behavior
-- progress logs or reports for non-trivial handoff evidence
-- ADRs for architecture or public contract decisions
-- templates when a repeated process becomes reusable
+- 设计/契约文档 — 变更后的预期
+- 测试或验证脚本 — 变更后的行为
+- progress log 或 report — 非平凡交接证据
+- ADR — 架构或公开契约决策
+- 模板 — 重复流程可复用时
 
-Do not mix unrelated refactors, new features, and broad documentation migration in one work block unless the contract explicitly says why they must move together.
+除非 contract 明确说明必须一起移动，否则不要在一个工作块里混合无关重构、新功能与大规模文档迁移。
 
-## Search And Reuse
+## 搜索与复用
 
-Before implementing, inspect the existing system:
+实现前先检视现有系统：
 
-- Use CodeGraph first when the repository is indexed and the task needs code understanding.
-- Use `rg` for text search and `fd` for file discovery when available.
-- Read nearby tests and helpers before introducing new helpers.
-- Prefer structured parsers and existing local APIs over ad hoc string manipulation.
+- 仓库已索引且任务需要理解代码时，优先用 CodeGraph。
+- 可用时用 `rg` 做文本搜索、`fd` 找文件。
+- 引入新 helper 前先读邻近测试与 helper。
+- 优先结构化 parser 与现有本地 API，避免 ad hoc 字符串处理。
 
-Assume the system may already contain a partial solution until search proves otherwise.
+在搜索证明否则之前，假设系统可能已有部分解法。
 
-## Completion Discipline
+## 完成纪律
 
-A completion claim must answer:
+完成声明必须回答：
 
-- what changed
-- why this approach was chosen
-- which command verified it and what the result was
-- whether contracts, docs, tests, or scripts were affected
-- what risk or follow-up remains
+- 改了什么
+- 为何选此方案
+- 哪条命令验证、结果如何
+- 是否影响契约、文档、测试或脚本
+- 剩余风险或后续项
 
-If verification fails, report the failing command and observed state instead of softening the completion definition.
+验证失败时，报告失败命令与观察到的状态，而不是软化完成定义。

package/docs/dynamic-workflow-dag-engine-roadmap.md

@@ -147,11 +147,11 @@ LLM / profile 生成 WorkflowSpec JSON
 
 本次复核依据的关键代码与文档：
 
-- `docs/feature-workflow.md`
-- 源码仓库历史 completed execution plan: remove-level1-fallback
-- `src/workflows/dag/types.ts`
-- `src/workflows/dag/validate.ts`
-- `src/workflows/dag/runner.ts`
+- `docs/feature-workflow.md`
+- 源码仓库历史 completed execution plan: remove-level1-fallback
+- `src/workflows/dag/types.ts`
+- `src/workflows/dag/validate.ts`
+- `src/workflows/dag/runner.ts`
 - `src/workflows/dag/lifecycle.ts`
 - `src/workflows/dag/report.ts`
 - `src/workflows/dag/init-hybrid.ts`
@@ -1744,6 +1744,6 @@ https://code.claude.com/docs/en/workflows
 
 [3] 用户上传文档：`2026-07-02-repository-analysis.md`，关于当前 `loop-agent` 仓库结构、DAG 主路径、Loop 语义、治理边界与健康度的分析报告。
 
-[4] 当前源码仓库历史 completed execution plan，关于删除 Level 1 fallback、抽取 shell verification、建立 DAG-oriented task read model 的完成记录；发布包只携带 execution plan 目录说明，不携带具体历史计划正文。
+[4] 当前源码仓库历史 completed execution plan，关于删除 Level 1 fallback、抽取 shell verification、建立 DAG-oriented task read model 的完成记录；发布包只携带 execution plan 目录说明，不携带具体历史计划正文。
 
 [5] 当前源码复核：`src/workflows/dag/types.ts`、`src/workflows/dag/validate.ts`、`src/workflows/dag/runner.ts`、`src/workflows/loop/actions.ts`、`src/task/read-model.ts`、`src/cli/catalog.ts`。

package/docs/exec-plans/README.md

@@ -1,6 +1,6 @@
-# Execution Plans
+# 执行计划
 
-- `active/README.md` lists currently active plans.
-- `completed/README.md` lists completed plans.
+- `active/README.md` — 当前进行中的计划
+- `completed/README.md` — 已完成的计划
 
-Use an execution plan for changes that affect multiple files, public command behavior, or repository governance.
+影响多文件、公开命令行为或仓库治理的变更应使用 execution plan。

package/docs/exec-plans/active/README.md

@@ -1,9 +1,7 @@
-# Active Execution Plans
-
-Use this directory for execution plans that are currently in progress.
-
-Source repositories may keep concrete active plan files next to this README. The npm package carries this README as a directory contract and does not copy loop-agent source-history active plans; target repositories generate their own active plans.
-
-Current active plans:
-
-- [2026-07-04-dag-role-skill-alignment.md](2026-07-04-dag-role-skill-alignment.md)
+# 进行中的执行计划
+
+本目录存放当前进行中的 execution plan。
+
+源码仓库可在本 README 旁保留具体 active plan 文件。npm 包只携带本 README 作为目录契约，不复制 loop-agent 源码历史的 active plan；目标仓库自行生成 active plan。
+
+当前 active plan：无。

package/docs/exec-plans/completed/README.md

@@ -1,9 +1,11 @@
-# Completed Execution Plans
+# 已完成的执行计划
 
-Completed plans are moved here after their implementation and verification finish.
-
-The npm package carries this README as a directory contract. Concrete completed plans are target-repository history and are not copied from loop-agent's source history.
-
-- [`2026-07-02-loop-agent-subject-restructure.md`](2026-07-02-loop-agent-subject-restructure.md) — promoted the former `tools/code-agent` runtime to the repository root, renamed it to `loop-agent`, and removed the old memory plugin product lines.
-- [`2026-07-04-remove-level1-fallback.md`](2026-07-04-remove-level1-fallback.md) — removed the historical sequential Level 1 fallback and converged the runtime, docs, and command surface on DAG execution.
-- [`2026-07-04-runtime-boundary-remediation.md`](2026-07-04-runtime-boundary-remediation.md) — consolidated CLI/skill/runtime boundaries, extracted DAG/Loop runtime seams, and centralized harness store/guard policy.
+实现与验证结束后，已完成计划移入此目录。
+
+npm 包携带本 README 作为目录契约。具体 completed plan 属于目标仓库历史，不从 loop-agent 源码历史复制。
+
+- [`2026-07-02-loop-agent-subject-restructure.md`](2026-07-02-loop-agent-subject-restructure.md) — 将原 `tools/code-agent` runtime 提升到仓库根、重命名为 `loop-agent`，移除旧 memory plugin 产品线
+- [`2026-07-04-remove-level1-fallback.md`](2026-07-04-remove-level1-fallback.md) — 移除历史顺序 Level 1 fallback，runtime、文档与 command surface 收敛到 DAG 执行
+- [`2026-07-04-runtime-boundary-remediation.md`](2026-07-04-runtime-boundary-remediation.md) — 整合 CLI/skill/runtime 边界，抽出 DAG/Loop runtime seam，集中 harness store/guard 策略
+- [`2026-07-04-dag-role-skill-alignment.md`](2026-07-04-dag-role-skill-alignment.md) — 对齐 DAG/Dynamic Workflow role 与 repo-local vetted skills，新增 strict skill audit
+- [`2026-07-06-production-readiness-hardening.md`](2026-07-06-production-readiness-hardening.md) — 冻结 Production Readiness v0.1，打磨 DAG 主路径 next steps、failure routing、doctor/report/failure handoff 与 dogfood 验证