run-feedbacklisted

# 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, both of them thin indexes over record files per `known-issues-format`: defects to `docs/issues/` + `docs/KNOWN_ISSUES.md`, work-items to `docs/backlog/` + `docs/BACKLOG.md`. 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, for **both** ledgers. Never hand-edit one side. Scope of this ban: record files and the index's `- **ID**` pointer 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. - "A work-item is small, its body can just live in the backlog index line" -> **WRONG**. Both indexes are **pointer** indexes: one line per record, body in `docs/backlog/<slug>.md`. An inlined body is how a single entry once reached 7 849 characters — unreadable, undiffable, impossible to close in parts. If a repo really runs a one-file b