harness-improvelisted

# Harness-improve: changing the protocol without meta-neuroslop BLUF: improvements to the harness are the highest-slop-risk artifact in this repo — plausible protocol text detached from incidents is neuroslop about neuroslop. Entry requires a live anchor; every change class has its own gate; a null measurement result is information, not failure. ## Stage 0 — anchor or stop Admissible anchors, in order of strength: 1. A reproduced incident — tool output from this or a documented session. 2. A structured harness-gap report (`.github/ISSUE_TEMPLATE/harness-gap.yml`). 3. A measurement — an eval run, an A/B result, a counted pattern across sessions. 4. An explicit owner decision. «Would be nice» without an anchor → record as a ROADMAP row candidate or drop. Do not proceed to implementation on an unanchored idea: critique of the harness demands the same evidence bar as critique of code. ## Stage 1 — verify against current main - Pull main; confirm the gap still exists by reading the current files, not the report. Reports go stale: the 2026-06-11 issue revision found a «missing» acceptance kit that had been merged before the issue was written. - Check `ROADMAP.md` and open issues for an existing row or tracker. A recorded decision (ADR, ROADMAP status, protocol doc) must be quoted before re-opening, and re-opening requires new evidence — not repeated association. ## Stage 2 — classify the change and pick its gate | Class | Typical diff | Gate before merge | |---|---|---| | M