agent-harness GitHub

Harness extension notes

Status: proposed, 2026-09-23. Parent: #299. Spike: #302.

Extend the existing workbench

Review evidence and its v0 template remain canonical. The #301 flood profile is a review view, not another receipt authority.

Proposed paths: docs/evals/{TAXONOMY,MERGE_BOUNDARY,REVIEW_UNDER_FLOOD}.md (#300/ #304/#301); docs/observability/AGENT_LOOP_SPANS.md (#303) owns trace vocabulary. Use issue links until those files land.

Read-only adapter contracts, not implementations: PR/base/head/stack references map to identity; deterministic run/fixture references map to retained observations; expected check IDs map to observed/missing evidence; optional trace IDs map to advisory diagnostics. Unknowns and prior attempts survive projection. Packet commands remain data.

Before implementing, reconcile the pending #295 reader and #296 accounting contracts. No pending API is promised. Reader diagnostics retain execution_verified=false and merge_verdict=null. A private control-plane issue indexes evidence, never promotes authority. Only executed measurements enter BENCHMARKS.

Sequence and exclusions

Review #301, then this note; curate the real cohort separately. #295/#296/ #298 Verify-red work does not block docs. Do not change CI or waive merge requirements.

Defer the private skills/workflow packaging issue until source-of-truth docs and packet mapping stabilize. No packaging PR now.

No second harness, runner, collector, opentelemetry-sdk, runtime-schema migration, private product PR, product rewrite, UX scoring, or LLM merge gate.