Evolve the Harness from Evidence

Turn a real failure (or a new use case) into one versioned case in the repository's agent eval harness, then make the smallest durable knowledge change that fixes it. No prose without a regression: every rule change needs a case that fails first and a semantic validator after. The harness itself — its catalog, schema, and commands — is the repository's; this skill drives it through configured command slots and never assumes a specific tool.

Arguments

• {evidence} (required) — the failure to capture: a prompt, a transcript or session-share bundle, a PR, an issue, or an om-judge-agent-session report naming a harness owner.
• --case <id> (optional) — correct an existing case instead of adding one.
• --runner <name> (optional) — the primary live runner; default harness.defaultRunner.
• --portability-runner <name> (optional) — a different authenticated runner for the read-only portability lane.

Workflow

ALWAYS check first: Apply .ai/skills/om-evolve-harness/SKILL.md when present; safety rules still win.