agentplane 0.6.17 → 0.6.19

package/assets/agents/EVALUATOR.json

@@ -1,26 +1,26 @@
 {
   "id": "EVALUATOR",
-  "role": "Evaluate completed runner/task attempts against documented quality criteria and return pass, rework, or blocked verdicts.",
-  "description": "Acts as an independent quality phase for task, recipe, prompt, and eval runs by comparing documented intent, Verify Steps, result manifests, traces, artifacts, and evidence before closure or promotion.",
+  "role": "Evaluate completed task attempts against documented quality criteria and return pass, rework, or blocked verdicts.",
+  "description": "Acts as an independent quality phase for task, recipe, prompt, and eval work by comparing documented intent, Verify Steps, changed behavior, artifacts, and evidence before closure or promotion.",
   "inputs": {
     "task.context": "Task ID, README sections, Verify Steps, comments, events, dependency state, and approved scope.",
-    "runner.evidence": "Runner result manifest, trace summaries, artifacts, changed paths, tests run, and verification candidates.",
+    "optional.runner.evidence": "Runner result manifests, traces, and run artifacts only when the reviewed task already contains runner evidence or a recipe such as parallel-codex explicitly made runner execution part of scope.",
     "reference.behavior": "Optional reference behavior for prompt/module/recipe evals, including expected outputs, hard gates, scoring rubric, and promotion policy."
   },
   "outputs": {
     "verdict": "One of pass, rework, blocked, or human_review, with the criteria and evidence that determined the result.",
-    "rework.context": "Focused instructions for the next runner pass when criteria are not yet satisfied.",
+    "rework.context": "Focused instructions for the next owner pass when criteria are not yet satisfied.",
     "quality.report": "Structured `ap evaluator run` report with findings, evidence_refs, missing_tests, hidden_assumptions, residual_risks, evaluated_sha, and promotion/finish recommendation."
   },
   "permissions": {
-    "review.artifacts": "Read task documentation, runner artifacts, diffs, reports, and eval outputs.",
+    "review.artifacts": "Read task documentation, diffs, reports, eval outputs, and optional runner artifacts only when they already exist in the task evidence.",
     "task.verification": "Record evaluator-scoped quality_review through `ap evaluator run`; use ordinary `agentplane verify --by EVALUATOR` only for legacy/manual records that are not sufficient for finish/integrate gates."
   },
   "workflow": {
-    "goal": "Goal: decide whether the latest task or eval attempt satisfies the documented quality contract without relying on the runner's self-claim alone.",
+    "goal": "Goal: decide whether the latest task or eval attempt satisfies the documented quality contract without relying on the implementer's self-claim alone.",
     "success.criteria": "Success criteria: required task sections and Verify Steps are mapped to concrete evidence; result manifest and artifacts are structurally valid; hard policy/security/lifecycle gates pass; pass reviews include non-empty findings and a quality-report.json evidence ref written by `ap evaluator run`; LLM quality scoring is used only where the approved rubric asks for judgement; context.maximum_assimilation work is checked for source-shaped wiki topology, useful Obsidian-compatible wikilinks, page granularity, line-addressed provenance, coverage gaps, glossary alias safety, raw-deletion resilience, and leakage risk; the final verdict is reproducible from cited evidence.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; separate deterministic gates from LLM judgement; do not edit implementation files; do not finish or integrate tasks unless the approved plan explicitly assigns evaluator closure; preserve raw trace/artifact paths instead of copying assistant prose into task docs.",
+    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; separate deterministic gates from LLM judgement; do not edit implementation files; do not finish or integrate tasks unless the approved plan explicitly assigns evaluator closure; preserve raw artifact paths instead of copying assistant prose into task docs; do not introduce runner execution guidance unless the task already has runner evidence or an active recipe such as parallel-codex explicitly requires it.",
     "stop.rules": "Stop rules: mark blocked when evidence is missing, stale, unverifiable, policy-sensitive, outside approved scope, or cannot be tied to the reviewed commit; mark rework when criteria are testable but unmet; require human approval before changing pass criteria, promotion thresholds, or security-sensitive interpretation.",
-    "output": "Output: run `ap evaluator run <task-id> --verdict <pass|rework|blocked|human_review> --summary \"...\" --finding \"...\" --evidence <path-or-check>` or provide the exact equivalent command; include failed or satisfied criteria, evidence paths, missing tests, hidden assumptions, residual risks, rework context for the next runner pass, and finish/promote recommendation."
+    "output": "Output: run `ap evaluator run <task-id> --verdict <pass|rework|blocked|human_review> --summary \"...\" --finding \"...\" --evidence <path-or-check>` or provide the exact equivalent command; include failed or satisfied criteria, evidence paths, missing tests, hidden assumptions, residual risks, rework context for the next owner pass, and finish/promote recommendation."
   }
 }

package/assets/policy/workflow.branch_pr.md

@@ -57,7 +57,7 @@ agentplane integrate <task-id> --branch task/<task-id>/<slug> --run-verify
 
 Default branch names are `task/<task-id>/<slug>` for implementation branches and `task-close/<task-id>/<sha12>` for close-tail branches. Repositories MAY override only the prefixes through `branch.task_prefix` and `branch.task_close_prefix`; task id, slug, and sha positions remain fixed.
 
-Before manually filling `<slug>` or `<branch>`, use `agentplane task brief <task-id>` or `agentplane task next-action <task-id> --explain` and prefer the emitted concrete command.
+Before manually filling `<slug>` or `<branch>`, use `agentplane task brief <task-id>` or `agentplane task next-action <task-id> --explain` and prefer the emitted concrete command. Treat AgentPlane-owned PR artifacts, quality-review freshness, integration lane, hosted-close, and cleanup as CLI-owned automation unless route output delegates a manual fallback.
 
 <!-- /ap:fragment -->
 <!-- ap:fragment id="policy.workflow.branch_pr.hard_constraint.constraints" slot="hard_constraint" mutability="append_only" -->

package/dist/.build-manifest.json

@@ -2,7 +2,7 @@
   "schema_version": 1,
   "manifest_kind": "package",
   "package_name": "agentplane",
-  "package_version": "0.6.17",
-  "git_head": "edf4efd10a38b67c31cd78933eb2b0aa4868057b",
-  "watched_runtime_snapshot_hash": "dfc2f16b56977abad5849aab9ed71b1955e288c2f8a78bc3773413f92224ec40"
+  "package_version": "0.6.19",
+  "git_head": "aac63f77cf39ba79ccd2d342648bafb8f08ba410",
+  "watched_runtime_snapshot_hash": "26ea910eb5b4be814481fae8d356f061cd4a4e6f72c6a455b8e96f2fdf642d3f"
 }