@tea-agent/loop-agent 0.10.0 → 0.12.0

package/docs/templates/backend-test-dag.json

@@ -0,0 +1,276 @@
+{
+  "$schema": "./agent-dag.schema.json",
+  "version": 3,
+  "title": "Backend test DAG template",
+  "runtimeContract": {
+    "schemaVersion": 1,
+    "agentRuntime": "pi-only",
+    "repairWriterProtocol": "explicit-node-v1"
+  },
+  "objective": "End-to-end backend functional testing pipeline: analyze requirements → generate functional test cases → review cases → generate pytest automation → execute pytest → retrospective with maturity rating. Covers the full chain from requirement analysis to test maturity assessment.",
+  "successCriteria": [
+    "analyze-inputs-pi returns a read-only test analysis contract covering scope, risks, and strategy",
+    "generate-backend-functional-cases-pi produces structured test cases with BE-<MODULE>-<NNN> IDs under testcase/md/",
+    "review-backend-cases-pi returns VERDICT: pass or request-revision with coverage assessment",
+    "review-backend-cases-gate-shell blocks pytest generation unless the review verdict is VERDICT: pass",
+    "generate-backend-pytest-pi converts reviewed cases into pytest code with 1:1 traceability under testcase/",
+    "execute-backend-pytest-shell runs pytest and produces HTML report under reports/",
+    "test-retrospect-pi generates retrospective report with A/B/C/D maturity rating under docs/test-reports/",
+    "Full traceability from acceptance criteria → functional test case ID → pytest function name"
+  ],
+  "globalConstraints": [
+    "Replace every REPLACE/WITH/... placeholder with concrete repo paths before execution; do not leave template placeholders in production DAG JSON.",
+    "Do not commit runtime traces under .harness/dag-runs/.",
+    "Use only existing executors: pi, shell. Pi writer nodes must set toolProfile=write.",
+    "Read-only nodes must not write repository files, including root artifacts/**.",
+    "Exclusive writer nodes must stay within declared writeSet.",
+    "Every task must explicitly declare executor; defaults.executor is schema-only and not a runtime fallback.",
+    "Functional test case IDs must use BE-<MODULE>-<NNN> format.",
+    "pytest execution must produce HTML reports under reports/.",
+    "Backend-test-dag nodes must maintain traceability from requirements to functional cases to pytest automation.",
+    "pytest automation scripts must use test_ filename prefix for pytest discovery.",
+    "generate-backend-pytest-pi must only create new test files under testcase/; modifying existing framework files (conftest.py, pytest.ini, pyproject.toml) is forbidden.",
+    "review-backend-cases-gate-shell must block pytest generation unless the review verdict is exactly VERDICT: pass.",
+    "If a target test filename already exists under testcase/, add a numeric suffix (_01, _02, ...); never overwrite or append to existing files.",
+    "execute-backend-pytest-shell must not modify test assertions or production code to make tests pass; test failures indicate potential implementation issues and must be reported honestly.",
+    "Prompt templates must not ask main session to write artifacts; node output is the artifact and runner archives it under .harness/dag-runs/.",
+    "Actual file operation paths must be macOS/Windows compatible; use / only for stable repo refs, JSON/Markdown evidence refs, and glob conventions.",
+    "Same-rank exclusive writeSet entries must be disjoint."
+  ],
+  "defaults": {
+    "executor": "pi",
+    "contextProfile": "slim",
+    "skills": [
+      "ai-engineering-context"
+    ],
+    "writePolicy": "read-only"
+  },
+  "skillsByRole": {
+    "planner": [
+      "loop-agent"
+    ],
+    "scout": [],
+    "implementer": [
+      "test-driven-development",
+      "verification-before-completion"
+    ],
+    "reviewer": [
+      "requesting-code-review",
+      "code-review-core"
+    ],
+    "verifier": [
+      "verification-before-completion",
+      "systematic-debugging"
+    ],
+    "closeout": [
+      "loop-agent",
+      "verification-before-completion"
+    ]
+  },
+  "executorModels": {
+    "pi": {
+      "LOW": "gpt-5.3-codex-spark",
+      "MED": "glm-5.2",
+      "HIGH": "gpt-5.5"
+    }
+  },
+  "tasks": [
+    {
+      "id": "analyze-inputs-pi",
+      "depends_on": [],
+      "complexity": "MED",
+      "executor": "pi",
+      "role": "planner",
+      "writePolicy": "read-only",
+      "allowedPaths": [
+        "REPLACE/WITH/SOURCE/PATH/**"
+      ],
+      "forbiddenPaths": [
+        ".harness/**",
+        "artifacts/**"
+      ],
+      "outputContract": "Structured Markdown extracting core content from source documents. No file writes.",
+      "retryPolicy": {
+        "maxAttempts": 3,
+        "backoff": "exponential",
+        "initialDelayMs": 2000,
+        "maxDelayMs": 30000,
+        "retryCategories": [
+          "timeout",
+          "network",
+          "rate-limit",
+          "unavailable"
+        ]
+      },
+      "subtask_prompt": "Read the task source materials and extract the following structured content for downstream test generation.\n\n## Required Output Sections:\n\n### 1. API Endpoints\nList all API endpoints: Method, Path, Description, Request params, Response format.\n\n### 2. Data Model\nFor each table/collection: fields, types, constraints, descriptions.\n\n### 3. Business Logic\nCore business rules, validation rules, calculation formulas.\n\n### 4. State Transitions\nState machines (e.g. order status: pending → paid → shipped → completed).\n\n### 5. Error Scenarios & Error Codes\nAll error codes, error messages, and when they occur.\n\n### 6. External Dependencies\nThird-party services, databases, message queues. Include timeout settings if documented.\n\n### 7. Acceptance Criteria\nExtract ALL acceptance criteria from 需求.md. Number them AC-001, AC-002, etc. If not explicitly listed, derive from functional requirements.\n\n### 8. Risk Areas\nHigh-risk areas requiring extra test coverage.\n\n## Conditional Sections (include ONLY if mentioned in requirements):\n- Authentication & Authorization: include ONLY if requirements mention auth mechanism (JWT, OAuth2, API Key, etc.)\n- Timeout Handling: include ONLY if requirements mention timeout configuration or degradation strategy\n- Concurrency & Idempotency: include ONLY if requirements mention concurrency, idempotency rules, or locking mechanisms\n- State Transitions: include ONLY if requirements mention business state machines\n- If not mentioned in requirements, do NOT include these sections\n\nThis output will be used directly by downstream nodes. Be thorough and structured.\nRead-only: do not modify code, docs, artifacts, or repository files."
+    },
+    {
+      "id": "generate-backend-functional-cases-pi",
+      "depends_on": [
+        "analyze-inputs-pi"
+      ],
+      "complexity": "MED",
+      "executor": "pi",
+      "role": "implementer",
+      "toolProfile": "write",
+      "writePolicy": "exclusive",
+      "writeSet": [
+        "testcase/md/**"
+      ],
+      "allowedPaths": [
+        "testcase/md/**"
+      ],
+      "forbiddenPaths": [
+        ".harness/**",
+        "artifacts/**"
+      ],
+      "outputContract": "Structured backend functional test cases in Markdown under testcase/md/. Each case uses BE-<MODULE>-<NNN> ID format.",
+      "subtask_prompt": "Based on the upstream analyze-inputs-pi output, generate structured backend functional test cases.\n\n## Output Steps (do in order):\n1. First, output a brief summary: how many modules, how many cases planned per module\n2. Then write each test case file under testcase/md/\n\n## Format Rules:\n- Each test case ID: BE-<MODULE>-<NNN> (e.g. BE-ORDER-001)\n- Each file covers one module\n- Case structure: ID, Title, Precondition, Steps, Expected Result\n- Map each case to acceptance criteria (AC-xxx)\n\n## Coverage Requirements:\n- Positive paths: happy path for each acceptance criterion\n- Negative paths: error scenarios (invalid input, not found, state violations)\n- Boundary conditions: empty input, max length, edge values\n\n## Conditional Coverage (include ONLY if mentioned in upstream analysis):\n- State transitions: include ONLY if upstream analyze-inputs-pi mentions state machine\n- Authentication scenarios: include ONLY if upstream analyze-inputs-pi mentions auth mechanism\n- Timeout scenarios: include ONLY if upstream analyze-inputs-pi mentions timeout handling\n- Concurrency scenarios: include ONLY if upstream analyze-inputs-pi mentions concurrency/idempotency rules\n- If not mentioned, do NOT generate these test cases\n\n## Constraints:\n- Stay within writeSet: testcase/md/**\n- Do NOT re-read source documents — use the upstream analyze-inputs-pi output only\n- Do not write root artifacts/**"
+    },
+    {
+      "id": "review-backend-cases-pi",
+      "depends_on": [
+        "generate-backend-functional-cases-pi"
+      ],
+      "complexity": "HIGH",
+      "executor": "pi",
+      "role": "reviewer",
+      "writePolicy": "read-only",
+      "allowedPaths": [
+        "**"
+      ],
+      "forbiddenPaths": [
+        ".harness/**",
+        "artifacts/**"
+      ],
+      "outputContract": "Plain Markdown whose first non-empty line is VERDICT: pass or VERDICT: request-revision; followed by Findings and Coverage Assessment. No file writes.",
+      "retryPolicy": {
+        "maxAttempts": 3,
+        "backoff": "exponential",
+        "initialDelayMs": 2000,
+        "maxDelayMs": 30000,
+        "retryCategories": [
+          "timeout",
+          "network",
+          "rate-limit",
+          "unavailable"
+        ]
+      },
+      "subtask_prompt_markdown": "./backend-test-dag.review-cases.prompt.md"
+    },
+    {
+      "id": "review-backend-cases-gate-shell",
+      "depends_on": [
+        "review-backend-cases-pi"
+      ],
+      "complexity": "LOW",
+      "executor": "shell",
+      "role": "verifier",
+      "writePolicy": "read-only",
+      "allowedPaths": [
+        "**"
+      ],
+      "forbiddenPaths": [
+        ".harness/**",
+        "artifacts/**"
+      ],
+      "outputContract": "Deterministic backend case review gate: exit 0 only when review-backend-cases-pi emits VERDICT: pass.",
+      "subtask_prompt": "Deterministic gate: block pytest generation unless backend case review emitted VERDICT: pass.",
+      "shell": {
+        "commands": [],
+        "verdictGate": {
+          "fromNodeId": "review-backend-cases-pi",
+          "accept": [
+            "VERDICT: pass"
+          ],
+          "label": "backend case review",
+          "lineMode": "first-verdict-line"
+        },
+        "cwd": ".",
+        "timeoutMs": 60000
+      }
+    },
+    {
+      "id": "generate-backend-pytest-pi",
+      "depends_on": [
+        "review-backend-cases-gate-shell"
+      ],
+      "complexity": "HIGH",
+      "executor": "pi",
+      "role": "implementer",
+      "toolProfile": "write",
+      "writePolicy": "exclusive",
+      "writeSet": [
+        "testcase/**/test_*.py"
+      ],
+      "allowedPaths": [
+        "testcase/**/test_*.py"
+      ],
+      "forbiddenPaths": [
+        ".harness/**",
+        "artifacts/**"
+      ],
+      "outputContract": "Pytest test files under testcase/ with 1:1 mapping to functional test case IDs. Summary lists generated files, test function count, and any skipped cases with reasons.",
+      "subtask_prompt_markdown": "./backend-test-dag.generate-pytest.prompt.md"
+    },
+    {
+      "id": "execute-backend-pytest-shell",
+      "depends_on": [
+        "generate-backend-pytest-pi"
+      ],
+      "complexity": "LOW",
+      "executor": "shell",
+      "role": "verifier",
+      "writePolicy": "read-only",
+      "allowedPaths": [
+        "**"
+      ],
+      "forbiddenPaths": [
+        ".harness/**",
+        "artifacts/**"
+      ],
+      "outputContract": "Archived pytest stdout/stderr with exit codes and HTML report path; no source or test file modifications.",
+      "subtask_prompt": "Run pytest for the backend test suite and capture results.",
+      "shell": {
+        "commands": [
+          "python -m pytest testcase/ --html=reports/backend-test-report.html -v"
+        ],
+        "verifyEvidence": {
+          "phase": "final",
+          "quota": "full",
+          "commandSource": "inline",
+          "commandCount": 1,
+          "commandLabels": [
+            "backend pytest execution"
+          ],
+          "finalFullRequired": true
+        },
+        "cwd": ".",
+        "timeoutMs": 300000
+      }
+    },
+    {
+      "id": "test-retrospect-pi",
+      "depends_on": [
+        "execute-backend-pytest-shell"
+      ],
+      "complexity": "MED",
+      "executor": "pi",
+      "role": "closeout",
+      "toolProfile": "write",
+      "writePolicy": "exclusive",
+      "writeSet": [
+        "docs/test-reports/**"
+      ],
+      "allowedPaths": [
+        "docs/test-reports/**"
+      ],
+      "forbiddenPaths": [
+        ".harness/**",
+        "artifacts/**"
+      ],
+      "outputContract": "Markdown retrospective report under docs/test-reports/ with coverage summary, review findings, pytest results, and maturity rating (A/B/C/D).",
+      "subtask_prompt_markdown": "./backend-test-dag.retrospect.prompt.md"
+    }
+  ]
+}

package/docs/templates/backend-test-dag.retrospect.prompt.md

@@ -0,0 +1,125 @@
+# Backend Test DAG Retrospect Prompt Template
+
+## Purpose
+
+Use this prompt for a **test retrospective** node: `executor: "pi"`, `role: "closeout"`, `toolProfile: "write"`, `writePolicy: "exclusive"`. The closeout agent reads upstream review reports and pytest execution results, then generates a retrospective report with an objective maturity rating.
+
+Do **not** create a new executor type. This is a standard `executor: pi` writer node.
+
+## Recommended DAG Node Shape
+
+```json
+{
+  "id": "test-retrospect-pi",
+  "depends_on": ["execute-backend-pytest-shell"],
+  "complexity": "MED",
+  "executor": "pi",
+  "role": "closeout",
+  "toolProfile": "write",
+  "writePolicy": "exclusive",
+  "writeSet": ["docs/test-reports/**"],
+  "allowedPaths": ["docs/test-reports/**"],
+  "forbiddenPaths": [".harness/**", "artifacts/**"],
+  "outputContract": "Markdown retrospective report under docs/test-reports/ with coverage summary, review findings, pytest results, and maturity rating (A/B/C/D).",
+  "subtask_prompt_markdown": "./backend-test-dag.retrospect.prompt.md"
+}
+```
+
+## Prompt Body
+
+You are the Backend Test DAG **test retrospective** agent.
+
+Your job is to read upstream outputs (review report + pytest results) and generate a retrospective report with a maturity rating. Write the report under `docs/test-reports/` only. Stay within `writeSet`. Do not write root `artifacts/**`.
+
+### Output Steps (do in order)
+
+1. First, output the maturity rating on the first line: `Rating: A/B/C/D`
+2. Then write the full report under `docs/test-reports/`
+
+### Inputs
+
+1. **Review report** — `review-backend-cases-pi` output (VERDICT, findings, coverage assessment).
+2. **Pytest output** — `execute-backend-pytest-shell` stdout/stderr and exit code.
+3. **HTML report** — `reports/backend-test-report.html` (if generated).
+
+Do NOT re-read source documents. Use upstream outputs only.
+
+### Maturity Rating Criteria
+
+| Rating | Coverage | Pass Rate | Review Findings |
+|--------|----------|-----------|-----------------|
+| **A** | 100% acceptance criteria covered | 100% pytest pass | No Critical or Important findings |
+| **B** | ≥80% acceptance criteria covered | ≥90% pytest pass | Only Informational findings |
+| **C** | ≥60% acceptance criteria covered | ≥70% pytest pass | No Critical findings (Important allowed) |
+| **D** | Below C thresholds | Below C thresholds | Or any Critical finding unresolved |
+
+#### Rating Rules
+
+- **Coverage** = (acceptance criteria with ≥1 covering test case) / (total acceptance criteria) × 100%
+- **Pass rate** = (passed pytest functions) / (total non-skipped pytest functions) × 100%
+- If `review-backend-cases-pi` returned `VERDICT: request-revision` and revision was not completed, cap at **D**.
+- If pytest exit code is non-zero and >30% tests failed, cap at **D** regardless of coverage.
+- Skipped tests (`@pytest.mark.skip`) count as "not covered" for pass rate but not as failures.
+
+### Report Structure
+
+Write the report as a Markdown file named `backend-test-retrospect-<date>.md` under `docs/test-reports/`.
+
+```markdown
+# Backend Test Retrospective Report
+
+**Date:** <YYYY-MM-DD>
+**Task:** <task-id>
+**Maturity Rating:** <A|B|C|D>
+
+## 1. Test Coverage Summary
+
+| Metric | Value |
+|--------|-------|
+| Total acceptance criteria | N |
+| Covered by test cases | N (X%) |
+| Total functional test cases | N |
+| Positive path cases | N |
+| Negative path cases | N |
+| Boundary cases | N |
+
+## 2. Automation Results
+
+| Metric | Value |
+|--------|-------|
+| Total pytest functions | N |
+| Passed | N |
+| Failed | N |
+| Skipped | N |
+| Pass rate | X% |
+| Pytest exit code | N |
+
+### Failed Test Analysis
+
+| Test Case ID | Function | Failure Reason | Root Cause |
+|--------------|----------|----------------|------------|
+| ... | ... | ... | ... |
+
+## 3. Review Findings
+
+| Severity | Finding | Status |
+|----------|---------|--------|
+| Critical | ... | Resolved / Unresolved |
+| Important | ... | Resolved / Unresolved |
+| Informational | ... | Resolved / Unresolved |
+
+## 4. Maturity Rating Rationale
+
+Explain which threshold was met or missed, and why the specific rating was assigned.
+
+## 5. Recommendations
+
+- Actionable items for improving the rating in the next iteration.
+- Specific gaps to close (uncovered criteria, flaky tests, missing negative paths).
+```
+
+### Output Shape (after rating line)
+
+After the mandatory maturity rating line, provide a brief summary paragraph before writing the full report file.
+
+Do not include chain-of-thought. Do not write root `artifacts/**`.

package/docs/templates/backend-test-dag.review-cases.prompt.md

@@ -0,0 +1,81 @@
+# Backend Test DAG Review Cases Prompt Template
+
+## Purpose
+
+Use this prompt for a read-only **backend test case review** node: `executor: "pi"`, `role: "reviewer"`, `writePolicy: "read-only"`. The reviewer audits generated backend functional test cases for completeness, format compliance, and traceability to source requirements. Downstream `generate-backend-pytest-pi` depends on a `VERDICT: pass` to proceed.
+
+Do **not** create `executor: reviewer`. Reviewer is a **role** on `executor: pi`.
+
+## Recommended DAG Node Shape
+
+```json
+{
+  "id": "review-backend-cases-pi",
+  "depends_on": ["generate-backend-functional-cases-pi"],
+  "complexity": "HIGH",
+  "executor": "pi",
+  "role": "reviewer",
+  "writePolicy": "read-only",
+  "allowedPaths": ["**"],
+  "forbiddenPaths": [".harness/**", "artifacts/**"],
+  "outputContract": "Plain Markdown whose first non-empty line is VERDICT: pass or VERDICT: request-revision; followed by Findings and Coverage Assessment. No file writes.",
+  "subtask_prompt_markdown": "./backend-test-dag.review-cases.prompt.md"
+}
+```
+
+## Prompt Body
+
+You are the Backend Test DAG **test case reviewer** (read-only).
+
+Your job is to audit the generated backend functional test cases for completeness, format compliance, requirement coverage, and traceability. You are **not** an implementer or test generator. Do not edit repository files, including root `artifacts/**`.
+
+### Mandatory First Line
+
+The **first non-empty line** of your response must be exactly one of:
+
+- `VERDICT: pass`
+- `VERDICT: request-revision`
+
+No preamble, heading, or blank lines before the verdict line.
+
+### Inputs to Review
+
+1. **Acceptance criteria** — from upstream `analyze-inputs-pi` output (AC-001, AC-002, ...).
+2. **Generated test cases** — files under `testcase/md/`.
+
+Do NOT re-read source documents. Use upstream outputs only.
+
+### Review Checklist
+
+| Area | Check | Severity if Missing |
+|------|-------|---------------------|
+| **ID format** | Every test case ID matches `BE-<MODULE>-<NNN>` (e.g. `BE-ORDER-001`) | Critical |
+| **Positive path coverage** | Happy-path scenarios for each acceptance criterion | Critical |
+| **Negative path coverage** | Error/exception scenarios (invalid input, not found, state violations) | Important |
+| **Boundary conditions** | Edge cases (empty input, max length, edge values) | Important |
+| **State transitions** | Illegal state changes covered | Important |
+| **Requirement traceability** | Each acceptance criterion (AC-xxx) maps to at least one test case ID | Critical |
+| **Case structure** | Each case has: ID, Title, Precondition, Steps, Expected Result | Important |
+| **No duplicate IDs** | All test case IDs are unique across files | Critical |
+
+### Conditional Coverage (check ONLY if mentioned in upstream analysis)
+
+- **Authentication coverage**: check ONLY if `analyze-inputs-pi` mentions auth mechanism (JWT, OAuth2, API Key, etc.)
+- **Timeout coverage**: check ONLY if `analyze-inputs-pi` mentions timeout handling or degradation strategy
+- If not mentioned in upstream analysis, do NOT flag as missing
+
+### Verdict Rules
+
+| Condition | Verdict |
+|-----------|---------|
+| All Critical checks pass, Important checks have no more than 2 findings | `VERDICT: pass` |
+| Any Critical check fails | `VERDICT: request-revision` |
+| More than 2 Important findings | `VERDICT: request-revision` |
+| Only Informational findings | `VERDICT: pass` (with findings listed) |
+
+### Output Shape (after verdict line)
+
+1. **Coverage Assessment** — table mapping each AC to covering test case IDs (or "uncovered").
+2. **Findings** — bullet list tagged `Critical`, `Important`, or `Informational`.
+3. **Statistics** — total case count, positive/negative/boundary breakdown, module distribution.
+4. **Required revisions** (only when `request-revision`) — numbered items for the upstream generator to fix.

package/docs/templates/frontend-design-contract.md

@@ -0,0 +1,33 @@
+# 前端设计契约模板
+
+## 页面目标
+
+TODO
+
+## 信息结构
+
+TODO
+
+## 组件拆分
+
+TODO
+
+## 交互规则
+
+TODO
+
+## UI 状态
+
+TODO
+
+## 样式与设计系统映射
+
+TODO
+
+## 响应式范围
+
+TODO
+
+## 风险与非目标
+
+TODO

package/docs/templates/frontend-task-constraints.md

@@ -0,0 +1,25 @@
+# 前端任务执行约束模板
+
+## 技术约束
+
+TODO
+
+## 代码风格约束
+
+TODO
+
+## 设计约束
+
+TODO
+
+## 验证约束
+
+TODO
+
+## allowedPaths
+
+TODO
+
+## forbiddenPaths
+
+TODO

package/docs/templates/frontend-task-requirement.md

@@ -0,0 +1,61 @@
+# 前端任务需求模板
+
+## 用户目标
+
+TODO
+
+## 目标页面/组件/路由
+
+TODO
+
+## 用户流程
+
+TODO
+
+## 必须状态
+
+### loading
+
+TODO
+
+### empty
+
+TODO
+
+### error
+
+TODO
+
+### success
+
+TODO
+
+### disabled
+
+TODO
+
+## 目标运行环境
+
+### desktop
+
+TODO
+
+### mobile
+
+TODO
+
+### tablet
+
+TODO
+
+## 交互要求
+
+TODO
+
+## 验收标准
+
+TODO
+
+## 非目标
+
+TODO

package/docs/templates/harness.schema.json

@@ -56,13 +56,13 @@
         "dag": {
           "type": "object",
           "additionalProperties": false,
-          "properties": {
-            "outputLanguage": {
-              "enum": ["zh-CN", "en"],
-              "description": "DAG agent 节点的默认输出语言。未配置时使用简体中文；代码、命令和机器契约不翻译。",
-              "default": "zh-CN"
-            },
-            "defaultEntry": {
+          "properties": {
+            "outputLanguage": {
+              "enum": ["zh-CN", "en"],
+              "description": "DAG agent 节点的默认输出语言。未配置时使用简体中文；代码、命令和机器契约不翻译。",
+              "default": "zh-CN"
+            },
+            "defaultEntry": {
               "enum": ["dag run-task", "run-dag"],
               "description": "默认 DAG 入口，用于任务 DAG 生成或直接 DAG 执行。",
               "default": "dag run-task"
@@ -122,8 +122,7 @@
         "principles": { "type": ["string", "null"], "description": "开发原则文档。" },
         "workflow": { "type": ["string", "null"], "description": "功能工作流文档。" },
         "verificationMatrix": { "type": ["string", "null"], "description": "验证命令矩阵。" },
-        "loopAgentHarness": { "type": ["string", "null"], "description": "harness runtime 指南。" },
-        "cursorExecutorUsage": { "type": ["string", "null"], "description": "可选 Cursor executor 使用说明。" }
+        "loopAgentHarness": { "type": ["string", "null"], "description": "harness runtime 指南。" }
       }
     },
     "artifacts": {
@@ -176,11 +175,10 @@
     },
     "executors": {
       "type": "object",
-      "description": "按 executor id 分组的执行器配置。已知 executor 包括 pi 和 cursor；项目也可以添加本地 executor key。",
+      "description": "按 executor id 分组的执行器配置。受治理 runtime 仅支持 pi；Cursor 仅通过 cursor-prompt sidecar 使用，不得配置在 executors 中。",
       "additionalProperties": { "$ref": "#/$defs/executor" },
       "properties": {
-        "pi": { "$ref": "#/$defs/executor" },
-        "cursor": { "$ref": "#/$defs/executor" }
+        "pi": { "$ref": "#/$defs/executor" }
       }
     }
   },

package/docs/templates/hybrid-dag.json

@@ -19,7 +19,7 @@
     "Add depends_on only when a child truly needs upstream output; challenge single-chain topologies during review",
     "Same-rank exclusive writeSet entries must be disjoint",
     "exclusive implementer nodes must use narrow, concrete writeSet paths; never use ** or repo root",
-    "Cursor remains an explicit optional executor; no-Cursor environments use Pi read-only scouts and Pi writer nodes with toolProfile=write",
+    "Use Pi read-only scouts and Pi writer nodes with toolProfile=write; Cursor is only available through the explicit cursor-prompt sidecar",
     "Read-only nodes must not write root artifacts/**; root artifacts/ is reserved for explicit exclusive write nodes"
   ],
   "defaults": {
@@ -53,11 +53,6 @@
     ]
   },
   "executorModels": {
-    "cursor": {
-      "LOW": "composer-2.5",
-      "MED": "composer-2.5",
-      "HIGH": "gpt-5.5"
-    },
     "pi": {
       "LOW": "gpt-5.3-codex-spark",
       "MED": "glm-5.2",

package/docs/templates/interactive-ui-round2-experiment.md

@@ -15,7 +15,7 @@ bash scripts-local/setup-drill-round2-react.sh /tmp/drill-round2-react-target
 npm run build
 node scripts-local/prepare-round2-ui-experiment.mjs \
   /tmp/drill-round2-react-target \
-  dogfood/features/F-2026-001/tasks/FE-001.yaml \
+  features/F-2026-001/tasks/FE-001.yaml \
   /tmp/round2-ui-experiment \
   loop-agent
 node scripts-local/build-round2-ui-variants.mjs \