@tea-agent/loop-agent 0.41.0-next.1 → 0.41.0-next.2

package/CHANGELOG.md

@@ -2,6 +2,7 @@
 
 ## [Unreleased]
 
+- backend-test 新增 `backendTest.executeTimeoutMs`，可为 readiness 授权的单次 pytest/HTML 执行节点配置 1 分钟至 2 小时的每命令超时；省略时仍为 5 分钟，不影响其他节点、DAG 外层 wall-clock 或 fail-closed 判定。
 - 对话中的长时间 DAG 执行现在会保留一条实时状态：持续显示总运行时间、当前阶段、完成步数和最近一次有效进展；重复等待不再堆叠，点击状态可以直接查看对应 DAG。模型仍会在阶段变化、重要发现、失败恢复和结束时，用自然语言说明刚完成什么、下一步做什么。
 
 ## [0.40.0] - 2026-08-31

package/dist/build-stamp.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "version": "0.41.0-next.1",
-  "gitSha": "082093199826919c9699608265a26e4840207421",
-  "builtAt": "2026-08-31T02:28:34.598Z"
+  "version": "0.41.0-next.2",
+  "gitSha": "0e7de8cc6c6055949135d7a7fba05139fe36fc23",
+  "builtAt": "2026-08-31T02:58:17.929Z"
 }

package/dist/task/config-types.js

@@ -149,6 +149,8 @@ export const backendTestConfigSchema = z
     executeScope: z.enum(["affected", "all"]).optional(),
     /** Backend-test-only workspace mutation control; omitted means Git guard. */
     workspaceControl: z.enum(["git", "filesystem-only"]).optional(),
+    /** Per-command timeout for the readiness-authorized pytest/HTML execution node. */
+    executeTimeoutMs: z.number().int().min(60_000).max(7_200_000).optional(),
 })
     .strict()
     .optional();

package/dist/workflows/dag/init-hybrid.js

@@ -4357,7 +4357,7 @@ async function buildBackendTestGapFillDag(sources) {
             commands: [],
             backendTestPipeline: "markdown-execute-html",
             cwd: ".",
-            timeoutMs: 300000,
+            timeoutMs: taskConfig.backendTest?.executeTimeoutMs ?? 300000,
             envAllowlist,
         },
     };
@@ -4833,7 +4833,7 @@ async function buildBackendTestHybridDag(sources) {
         'mkdir -p "${HARNESS_DAG_RUN_DIR}/reports"',
         'echo "pytest targets are resolved at runtime from execution-readiness v2 eligibleItemIds"',
     ].join("; ");
-    const execute = shellNode("execute-backend-pytest-and-html-report-shell", [manifest.id], "markdown-execute-html", "Read canonical contracts/backend-test-execution-readiness.json v2, verify final asset and eligibility-input hashes, then execute exactly its `eligibleItemIds` pytest node IDs once. Never execute `excludedItems`; retain each exclusion reason as residual TestBug/automation evidence rather than ProductBug. Prefer the deterministic module one-to-one path when a mapped script is missing but the module stem file exists. Generate a native pytest-html self-contained report, then render the primary self-contained Chinese HTML report from the same pytest-html plus final Markdown case metadata without rerun. Keep 测试结论 and quality status; make node 6 Markdown validation + case coverage and node 13 traceability + Markdown-to-pytest correspondence expandable to their full escaped details; show each failure overview item with its original pytest message plus deterministic evidence-based reason analysis; list failure/error case cards before the remaining cases while preserving stable order. Each polished per-case result card includes concise scenario, automation test name, result, duration, and redacted bounded HTTP request parameters/response results for both passed and failed cases. Do not render a technical/execution evidence section in HTML; retain auditable paths and hashes in facts.", "One scoped pytest execution over readiness-authorized eligible pytest items producing a valid pytest-html report with per-case captured output, self-contained reports/backend-test.html, reports/backend-test.md, reports/backend-test-facts.md, a deterministic self-contained reports/backend-test-l5-dashboard.html (machine-computed L-5 metrics, no JSON), and an optional contracts/code-coverage-v1.json when jacocoCoverage is configured (JaCoCo TCP dump → jacoco.xml → parsed; failure-safe); exit 0/1 with valid evidence continues.", [pytestCommand], 300000);
+    const execute = shellNode("execute-backend-pytest-and-html-report-shell", [manifest.id], "markdown-execute-html", "Read canonical contracts/backend-test-execution-readiness.json v2, verify final asset and eligibility-input hashes, then execute exactly its `eligibleItemIds` pytest node IDs once. Never execute `excludedItems`; retain each exclusion reason as residual TestBug/automation evidence rather than ProductBug. Prefer the deterministic module one-to-one path when a mapped script is missing but the module stem file exists. Generate a native pytest-html self-contained report, then render the primary self-contained Chinese HTML report from the same pytest-html plus final Markdown case metadata without rerun. Keep 测试结论 and quality status; make node 6 Markdown validation + case coverage and node 13 traceability + Markdown-to-pytest correspondence expandable to their full escaped details; show each failure overview item with its original pytest message plus deterministic evidence-based reason analysis; list failure/error case cards before the remaining cases while preserving stable order. Each polished per-case result card includes concise scenario, automation test name, result, duration, and redacted bounded HTTP request parameters/response results for both passed and failed cases. Do not render a technical/execution evidence section in HTML; retain auditable paths and hashes in facts.", "One scoped pytest execution over readiness-authorized eligible pytest items producing a valid pytest-html report with per-case captured output, self-contained reports/backend-test.html, reports/backend-test.md, reports/backend-test-facts.md, a deterministic self-contained reports/backend-test-l5-dashboard.html (machine-computed L-5 metrics, no JSON), and an optional contracts/code-coverage-v1.json when jacocoCoverage is configured (JaCoCo TCP dump → jacoco.xml → parsed; failure-safe); exit 0/1 with valid evidence continues.", [pytestCommand], taskConfig.backendTest?.executeTimeoutMs ?? 300000);
     if (execute.shell) {
         execute.shell.envAllowlist = collectBackendTestShellEnvAllowlist(sources);
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tea-agent/loop-agent",
-  "version": "0.41.0-next.1",
+  "version": "0.41.0-next.2",
   "type": "module",
   "bin": {
     "loop-agent": "bin/loop-agent.js",