@tea-agent/loop-agent 0.25.5 → 0.26.0

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

@@ -1,80 +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):
+# 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

@@ -1,68 +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.
+# 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.

package/harness.json

@@ -58,9 +58,8 @@
   "executors": {
     "pi": {
       "description": "Pi planning, review, diagnosis, and bounded writing when DAG toolProfile=write",
-      "defaultModel": "minimax-m3",
       "LOW": "minimax-m3",
-      "MED": "gpt-5.5",
+      "MED": {"model": "deepseek/deepseek-v4-flash","thinking": "max"},
       "HIGH": "gpt-5.6-sol"
     }
   }

package/package.json

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