@tea-agent/loop-agent 0.29.3 → 0.31.0

package/dist/workflows/dag/node-execution.js

@@ -126,7 +126,7 @@ export function buildNodePrompt(spec, task, upstream, options) {
         convergenceFeedback: options?.convergenceFeedback,
     });
 }
-function buildAttemptPrompt(task, basePrompt, attemptNumber, previousFailureCategory, previousProtocolReason, recoveryTargetPaths) {
+function buildAttemptPrompt(task, basePrompt, attemptNumber, previousFailureCategory, previousProtocolReason, recoveryTargetPaths, recoveryDiagnostics) {
     if (attemptNumber <= 1)
         return basePrompt;
     if (previousFailureCategory === "protocol-invalid" &&
@@ -152,6 +152,7 @@ function buildAttemptPrompt(task, basePrompt, attemptNumber, previousFailureCate
                     maxAttempts,
                     reason: "T4",
                     targetPaths: recoveryTargetPaths,
+                    diagnostics: recoveryDiagnostics,
                 }),
             ].join("\n");
         }
@@ -180,6 +181,7 @@ function buildAttemptPrompt(task, basePrompt, attemptNumber, previousFailureCate
                     maxAttempts,
                     reason: "T3_or_T5",
                     targetPaths: recoveryTargetPaths,
+                    diagnostics: recoveryDiagnostics,
                 }),
             ].join("\n");
         }
@@ -636,12 +638,21 @@ export async function executeDagNode(input) {
             // or when no progress facts exist yet (no-op).
             const recoveryProgress = await loadBackendTestWriterProgressForRetry(runDir, task.id);
             const recoveryTargetPaths = recoveryProgress?.targetPaths;
+            // Fold per-path structural reasons (e.g. T5 "case heading at wrong
+            // level") into the retry prompt so the model fixes the exact defect
+            // instead of guessing from a generic hint.
+            const recoveryDiagnostics = recoveryProgress?.issues
+                ?.filter((i) => !!i.path && i.recoverable)
+                .reduce((acc, i) => {
+                (acc[i.path] ??= []).push(i.detail);
+                return acc;
+            }, {});
             result = await executeNode({
                 task,
                 cwd,
                 model,
                 ...(thinking ? { thinking } : {}),
-                prompt: buildAttemptPrompt(task, prompt, attemptNumber, previousFailureCategory, previousProtocolReason, recoveryTargetPaths),
+                prompt: buildAttemptPrompt(task, prompt, attemptNumber, previousFailureCategory, previousProtocolReason, recoveryTargetPaths, recoveryDiagnostics),
                 attempt: attemptNumber,
                 reportActivity,
                 timeoutMs: livenessPolicy.absoluteMaxWallClockMs,

package/dist/workflows/dag/types.js

@@ -326,6 +326,20 @@ export const dagWritePolicySchema = z.enum([
 ]);
 /** Git/post-diff write guard intensity for exclusive Pi writers. */
 export const dagWriteGuardPolicySchema = z.enum(["full", "tools-only"]);
+/**
+ * Fail-closed outcome/diff consistency contract for bounded Pi writers.
+ * The writer must begin with IMPLEMENTATION_OUTCOME: changed,
+ * already-satisfied, or blocked; the executor checks it against the
+ * run-attributed diff. Declared before the dynamic child schema so the
+ * child writerOutcomePolicy optional field can reuse it without a TDZ.
+ */
+export const dagWriterOutcomePolicySchema = z
+    .object({
+    type: z.literal("implementation-outcome-v1"),
+    /** Generation writers may forbid already-satisfied/no-diff completion. */
+    requireChangedFiles: z.boolean().optional(),
+})
+    .strict();
 export const contextPolicyIdSchema = z.enum([
     "baseline-v1",
     "role-specialized-v1",
@@ -512,7 +526,14 @@ export const dagDynamicExpansionChildTaskSchema = z.object({
     allowedPaths: z.array(z.string()).optional().default([]),
     forbiddenPaths: z.array(z.string()).optional().default([]),
     writeSet: z.array(z.string()).optional(),
+    /**
+     * Materialized-child pass-through fields for bounded Pi writer children
+     * (backend-test md/pytest case sharding). All optional so legacy
+     * read-only/frontend map children (which never set these) keep parsing.
+     */
+    writerOutcomePolicy: dagWriterOutcomePolicySchema.optional(),
     writeGuardPolicy: dagWriteGuardPolicySchema.optional(),
+    retryPolicy: dagRetryPolicySchema.optional(),
 });
 export const dagDynamicExpansionSchema = z.object({
     type: z.enum(["map_agent", "verify_agent"]),
@@ -603,13 +624,6 @@ export const dagDecisionGateSchema = z.object({
     schemaVersion: z.literal(1).optional(),
     mode: dagDecisionGateModeSchema.optional().default("record-only"),
 });
-export const dagWriterOutcomePolicySchema = z
-    .object({
-    type: z.literal("implementation-outcome-v1"),
-    /** Generation writers may forbid already-satisfied/no-diff completion. */
-    requireChangedFiles: z.boolean().optional(),
-})
-    .strict();
 /**
  * The final supervised audit is the sole runtime write authority for its
  * writer. `allowedPaths` remains a ceiling; it is never a writer fallback.

package/docs/architecture/README.md

@@ -15,6 +15,10 @@
 5. `worker-and-feature.md` — agent-worker 子进程边界、controller identity、Task Pool、Feature、Observe 与 Console。
 6. `facts-and-state.md` — `.harness/` 各根目录、canonical facts、derived read models 与不可变规则。
 7. `evolution.md` — 当前已实现能力 vs 第 3–6 月未来方向（明确标注规划/未实现）。
+8. `state-and-failure-taxonomy.md` — Task Pool、DAG、Loop 与报告共用的 canonical 状态/失败分类。
+9. `taskspec-to-loop-agent-mapping.md` / `.yaml` — TaskSpec 到 worker/runtime 的兼容合同与机器可读镜像。
+10. `knowledge-graph-and-query-spec.md` — 业务知识图谱、knowledge-links 与查询协议。
+11. `testing-knowledge-base-impl-spec.md` — 测试知识库 schema、ID、读写矩阵和校验规则。
 
 ## 事实与规划的区分
 

package/docs/architecture/dag-execution.md

@@ -44,7 +44,7 @@ src/commands/dag-validate.ts  runDagValidate
 ### 专用 taskKind 与模板选择（架构摘要）
 
 - `initHybridDagFromTask` 按 `task.json.taskKind`（及前端需求自动分类）选择专用拓扑：`frontend-implementation`、`frontend-test`、`backend-test`、`knowledge-sync`、`knowledge-graph-bootstrap` 等；默认 `standard` 走 governance profile 通用实现链。
-- **backend-test（0.17.x）**：Markdown-first 固定短链（环境硬门 → Markdown 用例/Review → 单次 pytest + HTML → 报告与 L-5）；不在本页展开节点清单，见 `docs/design/active/backend-test-workflow.md` 与 completed markdown-first plan。
+- **backend-test（0.17.x）**：Markdown-first 固定短链（环境硬门 → Markdown 用例/Review → 单次 pytest + HTML → 报告与 L-5）；不在本页展开节点清单，见 `docs/runtime/backend-test-workflow.md` 与 completed markdown-first plan。
 - 专用模板不是新的 governance profile：风险等级仍由 profile 规则判断；写边界仍受 `allowedPaths` / `forbiddenPaths` / `writeSet` 约束。
 
 ## rank 调度

package/docs/architecture/worker-and-feature.md

@@ -62,7 +62,7 @@ controller identity 与 DAG skill snapshot 是两个不同冻结层（前者跨
 - schema/validate：`src/worker/task-spec/{schema,validate}.ts`。
 - 校验验收条件、依赖、验证命令；`agent-worker task validate-feature` 等用之。
 - **0.16.0+**：可选 `execution.workflow` 映射到 loop-agent `taskKind`（如 agent-dag / frontend-implementation / backend-test / frontend-test）；typed Task Outcome 与 artifact-aware Ready 门禁见 completed `2026-07-19-taskspec-workflow-routing.md`。
-- 文档映射镜像：`docs/design/active/taskspec-to-loop-agent-mapping.md`（runtime 真源仍在 `src/worker/` 与 materialize 路径）。
+- 文档映射镜像：`docs/architecture/taskspec-to-loop-agent-mapping.md`（runtime 真源仍在 `src/worker/` 与 materialize 路径）。
 
 ### Task Pool
 

package/docs/governance/README.md

@@ -11,5 +11,8 @@
 - [`harness-methodology-verification.md`](harness-methodology-verification.md)：如何用新鲜命令结果支持完成声明。
 - [`harness-methodology-debugging.md`](harness-methodology-debugging.md)：系统化定位故障，不用猜测代替证据。
 - [`document-review-policy.md`](document-review-policy.md)：文档 freshness、`reviewTier` 与 `lastReviewed` 更新边界。
+- [`lightweight-github-collaboration.md`](lightweight-github-collaboration.md)：短分支、简短 PR、CI 与 Squash Merge 的轻量协作规则。
+- [`研发模式.md`](研发模式.md)：Feature 团队推进、交付和知识回写方法论。
+- [`腾讯实践对当前项目的指引.md`](腾讯实践对当前项目的指引.md)：外部工程实践与本仓库治理/能力边界的映射。
 
 架构事实见 [`../architecture/README.md`](../architecture/README.md)，运行手册见 [`../runtime/README.md`](../runtime/README.md)，日常维护操作见 [`../operations/README.md`](../operations/README.md)。

package/docs/operations/README.md

@@ -8,5 +8,6 @@
 - [`branch-merge-guideline.md`](branch-merge-guideline.md)：按风险选择合并模式并留下 source-SHA 证据。
 - [`github-collaboration.md`](github-collaboration.md)：仓库内 GitHub 协作约定及自动/人工发布通道。
 - [`production-readiness.md`](production-readiness.md)：交付前的生产就绪判断。
+- [`backend-test-jacoco-coverage.md`](backend-test-jacoco-coverage.md)：Java 被测服务挂载 JaCoCo tcpserver agent 的 Maven、`java -jar` 与 Docker 操作手册。
 
 验证命令仍以 [`../governance/verification-matrix.md`](../governance/verification-matrix.md) 为准。