@tea-agent/loop-agent 0.1.0-fe-test.0

package/docs/templates/product-line/scaffold-samples/frontend-only/design.md

@@ -0,0 +1,14 @@
+# Design — Scaffold sample — frontend-only
+
+## Goals
+
+Generated snapshot for docs/templates/product-line/scaffold-samples. Not a live dogfood Feature.
+
+## Paths
+
+- Frontend allowed paths:
+  - `apps/web/src/sample-frontend/**`
+
+## Artifacts
+
+- `FE-IMPL-001` produces `frontend-impl`

package/docs/templates/product-line/scaffold-samples/frontend-only/feature.yaml

@@ -0,0 +1,14 @@
+schema_version: 1
+feature_id: F-2099-902
+profile: generic
+acceptance_policy:
+  schema_version: 1
+  authority: feature-verify-final
+  independent_qa_required: true
+  coverage_writer: feature-verify-final
+  final_verification:
+    command: agent-worker feature verify-final
+  delivery_sequence:
+    - verify-final
+    - delivery
+    - closeout

package/docs/templates/product-line/scaffold-samples/frontend-only/requirement.md

@@ -0,0 +1,6 @@
+# Scaffold sample — frontend-only
+
+Generated snapshot for docs/templates/product-line/scaffold-samples. Not a live dogfood Feature.
+
+Feature ID: `F-2099-902`
+Template: `frontend-only`

package/docs/templates/product-line/scaffold-samples/frontend-only/tasks/FE-IMPL-001.yaml

@@ -0,0 +1,85 @@
+schema_version: 1
+id: FE-IMPL-001
+feature_id: F-2099-902
+title: Scaffold sample — frontend-only — 前端实现
+description: Generated snapshot for
+  docs/templates/product-line/scaffold-samples. Not a live dogfood Feature.
+repo:
+  name: loop-agent
+  path_ref: .
+  default_branch: main
+type: frontend-feature
+priority: P2
+risk_level: medium
+capabilities:
+  - interactive-ui
+depends_on: []
+source_docs:
+  requirement: ../requirement.md
+  acceptance: ../acceptance.yaml
+  design: ../design.md
+acceptance_refs:
+  - AC-001
+scope:
+  goals:
+    - 实现前端变更并满足验收
+  non_goals:
+    - 不扩展到模板外的 Task 节点（无 BE-TEST/FE-TEST/FINAL-VERIFY）
+  assumptions:
+    - verify.commands 由 scaffold 调用方显式提供
+  open_questions: []
+constraints:
+  allowed_paths:
+    - apps/web/src/sample-frontend/**
+    - docs/progress/F-2099-902/fe/status.md
+    - docs/progress/F-2099-902/fe/**
+  forbidden_paths:
+    - config/prod/**
+    - .env
+    - .env.*
+    - secrets/**
+    - services/**
+  hard_constraints:
+    - 不读取生产密钥
+    - 不绕过 scaffold 冻结的 depends/produces/consumes
+execution:
+  workflow: frontend-implementation
+verify:
+  preset: standard
+  mode: serial
+  quota: full
+  commands:
+    - id: verify-1
+      label: npm run typecheck
+      command: npm run typecheck
+      required: true
+      timeout_ms: 300000
+    - id: verify-2
+      label: npm test
+      command: npm test
+      required: true
+      timeout_ms: 300000
+worker:
+  execution_mode: generate-validate-run
+  max_attempts: 1
+  timeout_ms: 7200000
+  require_clean_worktree: true
+  require_human_review: true
+  create_worktree: false
+loop_agent:
+  profile_policy: mapped
+  strict_models: true
+  strict_governance: true
+  max_concurrent: 1
+outputs:
+  required:
+    - dag_json
+    - dag_validate_json
+    - run_record
+    - dag_report_json
+    - shell_verification
+    - closeout_or_failure_handoff
+failure_policy:
+  failed_run_promote: false
+  generate_closeout_draft: true
+  create_followup_task: true

package/docs/templates/product-line/scaffold-samples/frontend-only/tasks/task-graph.yaml

@@ -0,0 +1,14 @@
+schema_version: 1
+feature_id: F-2099-902
+nodes:
+  - id: FE-IMPL-001
+    task: FE-IMPL-001.yaml
+    type: frontend-feature
+    depends_on: []
+    produces:
+      - kind: frontend-impl
+        schemaId: frontend-impl-v1
+        path: apps/web/src/sample-frontend
+parallel_policy:
+  max_parallel_tasks: 1
+  disallow_same_file_parallel_writes: true

package/docs/templates/product-line/task-graph.yaml

@@ -0,0 +1,23 @@
+schema_version: 1
+feature_id: F-YYYY-NNN
+nodes:
+  - id: BE-001
+    task: BE-001.yaml
+    type: backend-feature
+    depends_on: []
+    # Optional artifact-aware edges (Ready Planner envelope-level gate):
+    # produces:
+    #   - kind: backend-impl
+    #     schemaId: backend-impl-v1
+  - id: QA-001
+    task: QA-001.yaml
+    type: qa-execute
+    depends_on:
+      - BE-001
+    # consumes:
+    #   - kind: backend-impl
+    #     schemaId: backend-impl-v1
+    #     producerTaskId: BE-001
+parallel_policy:
+  max_parallel_tasks: 2
+  disallow_same_file_parallel_writes: true

package/docs/templates/product-line/task.yaml

@@ -0,0 +1,68 @@
+schema_version: 1
+id: BE-001
+feature_id: F-YYYY-NNN
+title: <Bounded tracer-bullet task>
+description: <Observable delivery>
+repo:
+  name: <repository-name>
+  path_ref: <repository-path-reference>
+  default_branch: main
+type: backend-feature
+priority: P1
+risk_level: medium
+depends_on: []
+source_docs:
+  requirement: ../requirement.md
+  acceptance: ../acceptance.yaml
+  design: ../design.md
+  test_plan: ../test-plan.md
+acceptance_refs:
+  - AC-FEATURE-001
+scope:
+  goals:
+    - <goal>
+  non_goals:
+    - <non-goal>
+constraints:
+  allowed_paths:
+    - <owned/path/**>
+  forbidden_paths:
+    - <protected/path/**>
+  hard_constraints:
+    - Do not access production secrets
+# Explicit runtime workflow → taskKind. For fullstack-v1 packets this should be set
+# on every TaskSpec. Allowed: agent-dag | frontend-implementation | backend-test | frontend-test
+execution:
+  workflow: agent-dag
+verify:
+  preset: standard
+  mode: serial
+  commands:
+    - id: focused-test
+      label: Focused deterministic verification
+      command: <project-specific verification command>
+      required: true
+      timeout_ms: 300000
+worker:
+  execution_mode: generate-validate-run
+  max_attempts: 1
+  timeout_ms: 7200000
+  require_clean_worktree: true
+  require_human_review: true
+  create_worktree: false
+loop_agent:
+  profile_policy: mapped
+  strict_models: true
+  strict_governance: true
+  max_concurrent: 1
+outputs:
+  required:
+    - dag_json
+    - run_record
+    - shell_verification
+    - diff_patch
+    - closeout_or_failure_handoff
+failure_policy:
+  failed_run_promote: false
+  generate_closeout_draft: true
+  create_followup_task: true

package/docs/templates/product-line/test-plan.md

@@ -0,0 +1,7 @@
+# Test plan — <Feature title>
+
+| Test ID | Acceptance | Level | Scenario | Deterministic command |
+|---|---|---|---|---|
+| TC-001 | AC-FEATURE-001 | integration | happy path and primary failure | `<project-specific command>` |
+
+Include negative cases, regression scope, environment assumptions, and evidence locations. Commands must match the target project's real toolchain.

package/docs/templates/production-readiness-checklist.md

@@ -0,0 +1,57 @@
+# Production Readiness 检查清单
+
+声称 Production Readiness v0.1 的低/中风险单仓库 DAG 任务使用本清单。
+
+## 范围
+
+- [ ] 单仓库
+- [ ] 单任务或小范围有边界任务
+- [ ] 低或中风险
+- [ ] 无生产 secret 或生产数据库访问
+- [ ] 无自动 merge 或 release
+- [ ] 无 DAG runtime 之外的第二套 runner
+- [ ] 无可写 Dynamic Workflow sharded migration
+
+## Task Contract
+
+- [ ] Task source 存在于 `.harness/tasks/<task-id>/source/`
+- [ ] `allowedPaths` 显式
+- [ ] `forbiddenPaths` 显式
+- [ ] `writeSet` 或预期写 scope 显式
+- [ ] Shell 验证命令显式
+- [ ] 非目标显式
+
+## DAG 主路径
+
+- [ ] 已运行 `loop-agent task advance <task-id> "Task title" --prd <prd.md> --allowed-path "<glob>" --json`（或 task 已存在且契约就绪）
+- [ ] `task advance` 产出/刷新 `.harness/tasks/<task-id>/dag.json` 并打开 writeSet gate
+- [ ] `loop-agent dag validate --dag <dag-path> --strict-models --strict-governance` 通过
+- [ ] `loop-agent task advance <task-id> --approve-gate "write-set-review:<digest>" --json` 产出 run id / lifecycle 事实（advanced arbitrary DAG 才用 `dag execute`）
+- [ ] `loop-agent dag report --run-id <run-id> --markdown` 可读
+- [ ] `loop-agent dag doctor --run-id <run-id>` 能解释失败或 paused run
+
+## 证据
+
+- [ ] 记录 DAG spec path
+- [ ] 记录 DAG validation 输出
+- [ ] 记录 run id
+- [ ] Shell 验证输出是新鲜的
+- [ ] 成功路径有 promotion 与 closeout 证据
+- [ ] 失败路径有 failure handoff 证据
+
+## Failure Routing
+
+- [ ] 存在时保留 raw failure category
+- [ ] 失败 run 有 DAG normalized failure category
+- [ ] 失败 run 有 product-line failure category
+- [ ] 失败 run 有 recommended follow-up
+- [ ] 派生 category 未覆盖已完成 DAG facts
+- [ ] `Unknown` 已说明或为 fixture 有意接受
+
+## 最终门禁
+
+- [ ] `npm run typecheck`
+- [ ] 相关定向 Vitest 文件
+- [ ] `bash scripts/check-repo.sh`
+- [ ] website/docs 变更时 `npm run docs:build`
+- [ ] 最终 sprint closeout 前 `bash scripts/ci.sh`

package/docs/templates/progress-log.md

@@ -0,0 +1,27 @@
+# 进度日志模板
+
+> 仅在确实需要跨会话交接时复制到 `docs/progress/YYYY-MM-DD-<topic>.md`。
+> 当前交接入口由 `docs/progress/README.md` 维护；完整验证证据写到 `docs/reports/`。
+
+## 生命周期
+
+- **新建**：当前任务尚未结束、下一次会话需要明确恢复步骤、且 active plan 状态不足以安全交接时，才在此新增 `YYYY-MM-DD-<topic>.md`，并更新 `docs/progress/README.md`。
+- **进行中**：只写当前事实、剩余风险和下一步；不写完整合同正文或长期报告。
+- **结束**：任务结束后，把仍有长期价值的交接迁入 `docs/reports/handoffs/`，更新 `docs/reports/handoffs/README.md` 索引；没有长期价值的临时交接不应继续占据当前入口。
+- **入口唯一**：`docs/progress/` 是当前交接入口；已结束的历史交接一律从 `docs/reports/handoffs/` 查找。`harness.json.artifacts.progressDir` 继续指向本目录，目标项目初始化契约保持不变。
+
+## 日期 / 会话
+
+## 变更内容
+
+## 已验证项
+
+## 新发现的 Bug / 技术债 / 漂移
+
+- Bugs:
+- Debt:
+- Drift:
+
+## 已知缺口 / 风险
+
+## 推荐下一步

package/docs/templates/project-start-checklist.md

@@ -0,0 +1,9 @@
+# 项目开工检查清单
+
+- [ ] 确认 `pwd`
+- [ ] 阅读 `README.md`、`harness.json`，以及 `harness.json.governanceRoot` 指向的 `README.md`
+- [ ] 检查 `git status --short --branch`
+- [ ] 确定单一工作块
+- [ ] 从治理根目录下的 `verification-matrix.md` 选择验证命令
+- [ ] 保留无关用户变更
+- [ ] 非平凡工作时记录 handoff 证据

package/docs/templates/qa-report.md

@@ -0,0 +1,48 @@
+# QA 报告模板
+
+## 日期 / 会话
+
+## 测试范围
+
+## 相关 Contract / Plan
+
+## 测试方法
+
+- 自动化测试：
+- 构建 / 类型检查：
+- Smoke / 手工路径：
+- 其他证据：
+
+## Smoke / 手工检查
+
+- CLI smoke：
+- DAG smoke：
+- Loop workflow smoke：
+- Executor smoke：
+- 结果：pass / blocked / fail
+
+## 通过标准
+
+## 发现项
+
+| ID | Severity | Finding | Evidence | Suggested Fix |
+|----|----------|---------|----------|---------------|
+
+## Failure Routing
+
+| Run / Scenario | Raw Failure | DAG Normalized Category | Product-line Category | Recommended Follow-up | Evidence |
+|---|---|---|---|---|---|
+|  |  |  |  |  |  |
+
+## 新发现的 Bug / 漂移
+
+- 新发现 bug：
+- 发现的契约漂移：
+- 发现的文档/测试不一致：
+
+## 最终结论
+
+- 结论：pass / partial / fail
+- 结论依据：
+
+## 后续项

package/docs/templates/sprint-contract.md

@@ -0,0 +1,29 @@
+# Sprint Contract
+
+## 目标（Objective）
+
+描述有边界的工作块。
+
+## 交付物（Deliverables）
+
+- 
+
+## 非目标（Non-goals）
+
+- 
+
+## 验证（Verification）
+
+```bash
+bash scripts/check-repo.sh
+npm run typecheck
+npm test
+```
+
+Windows 上通过 Git Bash 或已配置的兼容 Bash 运行脚本。实际文件操作用平台原生路径。
+
+## 失败条件（Failure Conditions）
+
+- 必需验证无法运行或失败
+- 工作需要超出本 contract 的范围
+- 实现改动了无关文件

package/docs/templates/worker-dogfood-evidence.md

@@ -0,0 +1,80 @@
+# Worker Dogfood Evidence
+
+## Sample identity
+
+| Field | Value |
+|---|---|
+| Date | |
+| Feature / Task | |
+| Target repo | disposable path or sanitized reference |
+| Controller package/version | |
+| Agent-worker package/version (same npm install) | |
+| Controller requested entry / real entry | sanitized reference; keep machine-local absolute value in runtime evidence |
+| Controller launch command / args prefix | sanitized reference |
+| Controller binary SHA-256 | |
+| Controller package fingerprint | `sha256:<hex>` |
+| Expected controller version / fingerprint | n/a / exact values |
+| Provider/model / override | |
+| Batch ID | |
+| Worker run ID | |
+| Retry of worker run ID | n/a / |
+| Candidate commit / tarball SHA-256 | n/a / |
+
+## Baseline
+
+- Baseline commit and `git status`:
+- Existing failing behavior or missing capability:
+- Preflight (`loop-agent --version`, `inspect`, `docs audit`, `check-repo`):
+
+## Run evidence
+
+| Artifact | Path / link | Result |
+|---|---|---|
+| TaskSpec / source-doc copies | | |
+| DAG spec | | |
+| DAG report JSON / Markdown | | |
+| DAG skill snapshot ref / SHA-256 / mode | | |
+| shell verification | | |
+| diff | | |
+| closeout or Failure Handoff | | |
+| morning report | | |
+| Observe snapshot / events | | |
+| Controller identity in Worker / Task Pool / batch / Feature evidence | | |
+
+## Candidate takeover evidence (if applicable)
+
+| Field | Value / result |
+|---|---|
+| Candidate isolated slot containment | |
+| `loop-agent` entry / binary SHA-256 / reported version | |
+| `agent-worker` entry / binary SHA-256 / reported version | |
+| Shared package fingerprint | |
+| Full init / doctor / inspect / docs audit / target check-repo | |
+| `agent-worker` skill and `.agents/skills` mirror hashes | |
+| Feature validation / `feature run --dry-run` | |
+| DAG executors | expected: `static`, `shell` only |
+| PATH trap invocations | expected: none |
+| Pi/model executor observed | expected: false; derive from actual DAG nodes |
+| Feature dry-run executed tasks | expected: empty |
+| Canary verdict / evidence path | |
+
+Do not use a deterministic canary result as proof that live Pi/model/provider execution succeeded. Record run-owned skill snapshot evidence and any explicitly authorized live run separately.
+
+## Acceptance and QA coverage
+
+| Acceptance | Test case(s) | Test file / verification | Result |
+|---|---|---|---|
+| | | | |
+
+## Failure / retry (if applicable)
+
+| Raw failure | Product-line category | Recommended follow-up | Root cause evidence | Retry result |
+|---|---|---|---|---|
+| | | | | |
+
+## Conclusion
+
+- Verdict: pass / fail / blocked
+- Review notes:
+- Follow-up task(s):
+- Evidence limitations (for example deterministic-only, no Pi executor/live takeover):

package/docs/templates/worker-dogfood-setup.md

@@ -0,0 +1,68 @@
+# Worker Dogfood Setup Template
+
+Use this template to create a disposable target repository for a real `agent-worker` sample. It is deliberately a target-repo recipe, not a substitute for product requirements.
+
+## Preconditions
+
+- Install one published controller version and record it:
+
+  ```bash
+  npm install -g @tea-agent/loop-agent@<version>
+  npm list -g @tea-agent/loop-agent --depth=0
+  loop-agent --version
+  agent-worker --version
+  agent-worker --help
+  ```
+
+- Before any write-capable Worker command, resolve one controller identity for the batch. Record its package version, absolute launch entry, binary SHA-256, and portable package fingerprint. If the run is part of a release or self-hosting train, carry the expected version/fingerprint as explicit CLI gates.
+- Create a clean, disposable target repository. Do not use `npm link`, `npm run dev`, or a workspace controller for a real-evidence run.
+- Put requirement, acceptance, design, test plan, and QA case matrix next to the TaskSpec. `agent-worker` materializes immutable copies into the harness task source before DAG generation.
+
+## Setup checklist
+
+- [ ] Target has a committed baseline and a passing `loop-agent init --profile full --merge` preflight.
+- [ ] Existing test demonstrates the desired behavior is missing or unimplemented.
+- [ ] TaskSpec has narrow `allowed_paths` and explicit `forbidden_paths`.
+- [ ] Task Pool dependencies are either backed by real prior runs or intentionally recorded as pre-existing evidence.
+- [ ] The chosen model/provider and `--pi-model` smoke override, if any, are recorded.
+- [ ] `--loop-agent-bin` resolves to the intended published package, and expected controller version/fingerprint are recorded before target writes.
+- [ ] If this is a self-hosting run, published N remains fixed for the whole batch; candidate N+1 is installed and verified in a separate slot.
+
+## Execute
+
+```bash
+agent-worker batch run-ready \
+  --feature-dir <feature-dir> \
+  --repo <target-repo> \
+  --loop-agent-bin <published-loop-agent-entry> \
+  --expected-controller-version <version> \
+  --expected-controller-fingerprint <sha256:value> \
+  --limit 1 \
+  --check-repo \
+  [--pi-model <model>]
+
+agent-worker observe snapshot --repo <target-repo> > <evidence-dir>/observe-snapshot.json
+agent-worker report morning --repo <target-repo> --output <evidence-dir>/morning-report.md
+```
+
+For a failed task, do not delete state or alter JSONL evidence. Fix the external/root cause, then make the retry explicit:
+
+```bash
+agent-worker task retry <task-id> --repo <target-repo> --reason "<root cause corrected>"
+agent-worker batch run-ready --feature-dir <feature-dir> --repo <target-repo> --limit 1 --check-repo
+```
+
+The retry run must have a distinct `workerRunId` and retain `retryOfWorkerRunId` in its Task Pool evidence.
+
+## Versioned self-hosting takeover
+
+From a source checkout, use the repo-maintainer deterministic canary after building or packing candidate N+1:
+
+```bash
+npm run self-host:canary -- \
+  --deterministic \
+  --tarball <candidate.tgz> \
+  --output <candidate-canary-evidence.json>
+```
+
+The deterministic canary must prove isolated-slot containment, both candidate bin identities, package fingerprint, full init/governance checks, a zero-execution Feature dry-run, static/shell-only observed DAG executors, and no PATH controller fallback. It does not claim to trap every possible Pi SDK/absolute path and does not replace a separately authorized live Pi run or the DAG skill-snapshot tests.