improve-harness

# Improve Harness Improve one bounded future-agent behavior without turning every difficult task into permanent process. Keep consumer truth with its owner and require a fresh rerun before claiming improvement. ## Establish Authority - Read `AGENTS.md`, `docs/WORKFLOW.md`, and applicable local instructions. - Confirm the request authorizes changing Harness behavior. Inspection or a request to report friction does not authorize edits. - Record the initial repository root, revision, branch, status, and unrelated changes. Preserve all existing work. - Treat invocation as authority for this bounded experiment, not for changing product policy, weakening proof, adding credentials, or mutating external systems. ## 1. Preserve The Baseline Use an observed task trajectory when available. Record: - the representative job and accepted outcome; - the concrete failure and evidence; - human steering, relay, or recovery required; - the worker, repository revision, relevant external state, tools, and authority; and - existing proof and known limitations. Do not diagnose a worker limitation from one run. If no observed baseline exists, stop with an experiment proposal; do not manufacture one. Copy `docs/templates/harness-improvement.md` to `docs/plans/active/harness-improvement-<slug>.md`. Reuse an existing active record for the same experiment. ## 2. Locate The Earliest Gap Trace the failure upstream to the first owner that could have prevented or exposed it: - **Context...