run-feedback

# Run Feedback **Purpose**: Errors from runs evaporate today — a gate fails, gets retried, and the knowledge dies with the session. This skill closes the loop: deterministic **capture** (retro step, hooks, transcript miner) → LLM **triage** → deterministic **filing** into the existing ledgers (`docs/issues/` + `docs/KNOWN_ISSUES.md` per `known-issues-format`, or the project backlog). Filed issues marked `auto_fixable: true` feed the `/heal-issues` harness. Machine state lives under the gitignored `.agent/feedback/`; the repo-visible trace is the ledgers themselves. ## 1. Red Flags (Anti-Rationalization) **STOP and READ THIS if you are thinking:** - "I'll append a line to KNOWN_ISSUES.md without creating the issue file" -> **WRONG**. Lockstep or nothing — the `file` subcommand writes both or neither. Never hand-edit one side. Scope of this ban: issue files and the index's `- **ID**` issue lines. The prefix→category TABLE row in the index preamble is the ONE hand-edit that is yours (§7 step 6) — the script cannot write it. - "This finding is obviously a dup, I'll file it anyway for completeness" -> **WRONG**. A duplicate goes to `--as noise --reason "duplicate of <ID>"`; the recurrence is already counted by the fingerprint merge. - "I'll classify straight from the inbox JSON without running `triage`" -> **WRONG**. Dup candidates come from the script (fingerprint + title overlap). Eyeballing misses them. - "I'll invent severity `HIGH` / status `handled` for a new i...