@tea-agent/loop-agent 0.12.0 → 0.13.0-beta.0

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

@@ -1,125 +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/**`.
+# 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. **Machine-readable report** — `$HARNESS_DAG_RUN_DIR/reports/backend-test-junit.xml` (runner-owned evidence; use the path reported by `execute-backend-pytest-shell`).
+
+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

@@ -1,81 +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.
+# 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", "backend-test-analysis-contract-shell"],
+  "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 / analysis** — from the validated Backend Test Analysis v1 artifact materialized by `backend-test-analysis-contract-shell` (`contracts/backend-test-analysis.json` under the current DAG run). Do not treat free-form Markdown from `analyze-inputs-pi` as the contract.
+2. **Generated test cases** — files under `testcase/md/`.
+
+Do NOT re-read source documents. Use the validated analysis artifact and generated cases 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 the validated analysis artifact mentions auth mechanism (JWT, OAuth2, API Key, etc.)
+- **Timeout coverage**: check ONLY if the validated analysis artifact mentions timeout handling or degradation strategy
+- If not mentioned in the validated analysis artifact, 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/exec-plan.md

@@ -1,64 +1,64 @@
-# 执行计划模板
-
-## 标题
-
-## 状态
-
-- draft / active / blocked / completed
-
-## 背景
-
-- 当前问题或机会是什么：
-- 为什么值得现在做：
-
-## 目标（Objective）
-
-- 本计划希望达成什么结果：
-
-## 范围（Scope）
-
-- 包含：
-- 不包含：
-
-## 约束（Constraints）
-
-- 架构/契约约束：
-- 时间/风险约束：
-- 验证约束：
-
-## 里程碑（Milestones）
-
-| ID | Milestone | Status | Exit Criteria |
-|----|-----------|--------|---------------|
-| M1 |           | todo   |               |
-
-## 工作分解（Work Breakdown）
-
-| ID | Work Item | Status | Notes |
-|----|-----------|--------|-------|
-| W1 |           | todo   |       |
-
-## 验证关口（Verification Gates）
-
-- [ ] 文档/契约已同步
-- [ ] 最低必要测试已通过
-- [ ] 关键路径已验证
-- [ ] 风险与未覆盖项已记录
-
-## 风险 / 阻塞项
-
-- 风险：
-- 阻塞：
-
-## 回退 / 恢复（Rollback / Recovery）
-
-- 如何回退：
-- 回退后如何恢复基线：
-
-## Open Questions
-
-- 
-
-## 推荐下一步
-
-- 
+# 执行计划模板
+
+## 标题
+
+## 状态
+
+- draft / active / blocked / completed
+
+## 背景
+
+- 当前问题或机会是什么：
+- 为什么值得现在做：
+
+## 目标（Objective）
+
+- 本计划希望达成什么结果：
+
+## 范围（Scope）
+
+- 包含：
+- 不包含：
+
+## 约束（Constraints）
+
+- 架构/契约约束：
+- 时间/风险约束：
+- 验证约束：
+
+## 里程碑（Milestones）
+
+| ID | Milestone | Status | Exit Criteria |
+|----|-----------|--------|---------------|
+| M1 |           | todo   |               |
+
+## 工作分解（Work Breakdown）
+
+| ID | Work Item | Status | Notes |
+|----|-----------|--------|-------|
+| W1 |           | todo   |       |
+
+## 验证关口（Verification Gates）
+
+- [ ] 文档/契约已同步
+- [ ] 最低必要测试已通过
+- [ ] 关键路径已验证
+- [ ] 风险与未覆盖项已记录
+
+## 风险 / 阻塞项
+
+- 风险：
+- 阻塞：
+
+## 回退 / 恢复（Rollback / Recovery）
+
+- 如何回退：
+- 回退后如何恢复基线：
+
+## Open Questions
+
+- 
+
+## 推荐下一步
+
+- 

package/docs/templates/feature-spec.md

@@ -1,53 +1,53 @@
-# Feature Spec 模板
-
-## 标题
-
-## 状态
-
-- draft / active / completed
-
-## 背景（Background）
-
-- 问题背景：
-- 用户/协作者痛点：
-- 与现有系统的关系：
-
-## 目标（Goal）
-
-- 本 feature 要实现什么：
-
-## 非目标（Non-goals）
-
-- 明确本轮不做什么：
-
-## 关键场景 / 用户路径
-
-1. 
-2. 
-3. 
-
-## Feature List
-
-| ID | Feature | Priority | Status | Acceptance | Notes |
-|----|---------|----------|--------|------------|-------|
-| F1 |         | High     | todo   |            |       |
-
-## 依赖（Dependencies）
-
-- 上游依赖：
-- 下游影响：
-- 文档/契约依赖：
-
-## 风险（Risks）
-
-- 
-
-## 验证说明（Verification Notes）
-
-- 最低建议验证：
-- 加强验证：
-- 关键手工路径：
-
-## Open Questions
-
-- 
+# Feature Spec 模板
+
+## 标题
+
+## 状态
+
+- draft / active / completed
+
+## 背景（Background）
+
+- 问题背景：
+- 用户/协作者痛点：
+- 与现有系统的关系：
+
+## 目标（Goal）
+
+- 本 feature 要实现什么：
+
+## 非目标（Non-goals）
+
+- 明确本轮不做什么：
+
+## 关键场景 / 用户路径
+
+1. 
+2. 
+3. 
+
+## Feature List
+
+| ID | Feature | Priority | Status | Acceptance | Notes |
+|----|---------|----------|--------|------------|-------|
+| F1 |         | High     | todo   |            |       |
+
+## 依赖（Dependencies）
+
+- 上游依赖：
+- 下游影响：
+- 文档/契约依赖：
+
+## 风险（Risks）
+
+- 
+
+## 验证说明（Verification Notes）
+
+- 最低建议验证：
+- 加强验证：
+- 关键手工路径：
+
+## Open Questions
+
+-