heyeddi-pr-respondlisted

# HeyEddi PR Respond **PR author response to every review source** — human teammates, bots, and **HeyEddi CI root summaries** (e.g. `heyeddi-ci` review bodies that list findings on the diff). There is **one** respond skill. Do not split human vs CI into different pipelines. ## No project scratch files **Never write** `.heyeddi/docs/pr-*` (tracking, replies, posted, comments). GitHub threads are the SSOT. | Data | Where it lives | |------|----------------| | Comment cache | System temp (`fetch_pr_comments` stdout path) | | Inventory | `build_comment_inventory` stdout (optional temp cache) | | Tracking | In chat only | | Reply drafts | `--replies-text` to `post_thread_replies` / `verify_response` | | Post log | `post_thread_replies` stdout JSON only | Delete legacy `pr-*` / `pr-*-ci-*` files under `.heyeddi/docs/` if present. ## Root review summaries (HeyEddi CI and others) Review **submission bodies** (Conversation / Files tab root comment) often list findings like: ``` **Commented on the diff** 1. 🔴 Bug title — `path/to/file.py:185` ``` **Mandatory:** 1. Run `build_comment_inventory` after fetch — it parses every review body for `` `path:line` `` bullets and links them to inline comment IDs. 2. Every **postable** item (inline + discussion) gets fix/decline analysis, a code change when needed, and a `## Comment <id>` reply draft. 3. Orphan items (listed in the root summary but no inline thread) still get fix/decline in code and must appear in `## Summary`. 4. Do **