harness-reportlisted

# Harness Report Promote captured feedback events into digest GitHub issues on the harness repo — one issue per recurring failure pattern, so each can become a new guardrail. Capture is local and automatic; reporting is batched, reviewed by the user, and explicit. ## Flow ### 1. Load the store Fold the append-only store to current-state-per-id with the helper (it defaults a missing `kind` to `gate-failure` for back-compat): ```powershell & "${CLAUDE_PLUGIN_ROOT}/scripts/fold-events.ps1" | ConvertFrom-Json ``` Skip events that already have `reportedIssue`. If nothing is unreported, say so and stop. ### 2. Cluster (within a kind, never across) Group unreported events by recurring mistake, clustering **within a single `kind`** — never mix `gate-failure` and `review-comment` in one cluster. - `gate-failure`: same gate + template + similar failure text/note. Read the `diffs/<id>.failure.patch` / `.fix.patch` sidecars when the outputTail is not enough. - `review-comment`: same template + similar guidance across PRs/files. Read the `diffs/<id>.hunk.patch` sidecar for the code the comment was on. These are the highest-value clusters — a comment a human reviewer had to leave is a rule the toolchain did not enforce. For each `review-comment` cluster, propose a **remedy type** from the comment bodies and file paths: - layering/structure ("imports a sibling", "belongs in lib/service", dependency direction) → an arch-test fixture (.NET `tests/*.Architecture`) or a de