feat: make /idd-list and /idd-issue GitHub Discussions-aware (intake blind spot)

[kiki830621]

Problem

/idd-list and /idd-issue only look at GitHub Issues. But real user bug reports and feature requests frequently arrive as GitHub Discussions (Q&A category especially), which are completely invisible to the IDD workflow.

Concrete case that surfaced this: on 2026-07-04, /idd-list on PsychQuant/che-ical-mcp reported 0 open issues — a clean backlog. But a real permission bug report had been sitting in Discussions the whole time:

• Permission setup issue che-ical-mcp#105 ("Permission setup issue")

The report, the maintainer's diagnosis, and the reporter's eventual "it's fixed" confirmation all happened inside the Discussion. None of it ever touched the Issues tab, so IDD had a blind spot over the entire intake channel.

Type

feature (enhancement)

Expected

/idd-list — surface Discussions alongside Issues:

• Fetch open Discussions via gh api graphql (Discussions have no REST API).
• No-op gracefully when hasDiscussionsEnabled: false.
• Flag actionable ones: Q&A / Ideas category, answerChosenAt: null (unanswered), and not already linked to an existing issue.
• Show them in a dedicated block with a Suggested next action.
• Opt-in via a --discussions flag (avoid always-on latency + noise) or a config key.

When a Discussion describes an unresolved problem, the workflow:

1. Suggest creating an Issue from it (carry the Discussion URL as provenance).
2. After the Issue exists, post a reply in the Discussion linking the new Issue.

/idd-issue — accept a Discussion as a source:

• --from-discussion <url|number>: seed the issue body from the Discussion, record provenance, and (draft-and-confirm) post a back-reference reply.

Design constraints (learned from the che-ical-mcp discussion 105 case)

• Do NOT auto-file. That discussion was already resolved — the reporter's latest comment (2026-07-04) was "everything is fixed, thank you," and the root causes were already tracked in closed issues. A tool that mechanically files an issue for every Discussion "problem" would have created a noise issue that opens only to be closed immediately. The tool must surface + let the human judge, not auto-create.
• Dedup: a Discussion already referenced by an existing (open or closed) issue should not be re-flagged.
• Resolution detection: at minimum, don't flag Discussions whose latest activity is a maintainer answer or a reporter "fixed" confirmation. answerChosenAt != null is the cheap signal; latest-comment sentiment is a stretch goal.
• Category filter: Announcements / Show-and-tell aren't intake; only Q&A (and optionally Ideas) count.
• Outward-facing writes (the Discussion reply) are draft-and-confirm, never silent auto-post.

Current Status

Phase: closed
Last updated: 2026-07-11 by /idd-close

Key Decisions

• Complexity = Spectra（opt-out → 直接 propose）：方向已由 issue body 設計約束定案
• Conflict Class = A_parallel_safe；排 batch Wave C 尾（最重項）
• unattended 邊界：Discussion 回文 draft-only 不 auto-post

Filed 2026-07-04 from the che-ical-mcp Discussions intake gap. The two open discussions there (105 and 1) were closed out manually — replied, and 105 marked answered — as part of surfacing this.

[kiki830621]

Diagnosis

Type

feature（intake 盲點修補 — 兩 skill 擴充 + GraphQL）

Root Cause / Analysis

盲點結構因：Discussions 無 REST API、gh issue list 天然不含，IDD 所有 intake 面（idd-list 的 triage、idd-issue 的建案）只綁 Issues tab。che-ical-mcp#105 案例證明整條「report → diagnose → fixed 確認」生命週期可以完全發生在 Discussions 而 IDD 零感知。

方向已由 issue body 定案（使用者自書設計約束）：opt-in --discussions flag、hasDiscussionsEnabled:false 優雅 no-op、Q&A/Ideas category filter、answerChosenAt:null 未答信號、已被 issue 引用者 dedup、絕不 auto-file（surface + human judge）、Discussion 回文 draft-and-confirm。

實作面組件：

1. idd-list --discussions：GraphQL query（category、answerChosenAt、url、title、updatedAt）+ dedup 掃描（search issues body 引用該 discussion URL）+ 專屬區塊輸出 + suggested next
2. idd-issue --from-discussion <url|number>：GraphQL 讀 discussion → seed body（provenance 段含 URL + 原文 blockquote）→ 建案後 draft-and-confirm 回文
3. references/discussions-intake.md：GraphQL query 樣板 + 契約（no-auto-file / dedup / resolution-detection 三約束的 normative 寫法）

Impact

• skills/idd-list/SKILL.md、skills/idd-issue/SKILL.md、新 references 檔
• unattended 注意：--from-discussion 的回文是 outward-facing write — unattended 模式下 draft-only 不 post（surface 到 report），attended 才 confirm-post

Strategy

• references/discussions-intake.md：契約 + GraphQL 樣板（含 hasDiscussionsEnabled probe）
• idd-list Step 2.7（--discussions opt-in）：fetch → category/answered filter → dedup → 專屬區塊 + footer 統計
• idd-issue --from-discussion：seed + provenance + draft-and-confirm 回文（unattended = draft-only）
• 測試：GraphQL 回應 fixture（mock gh api graphql）× filter/dedup 分支
• README/usecase-routing 增補

Conflict Class

A_parallel_safe — idd-list/idd-issue SKILL.md 在 queue 內無他案共享（#117 的 idd-issue 接線已在 cluster branch，實作本案時 rebase 自然吸收）。

Complexity

Spectra（opt-out → 直接 propose）

Layer 2 命中：兩個 published skill surface 新 flag + 行為契約應成文（references 檔）。Layer 3 命中：intake channel 架構擴充。Opt-out 條件全數成立（方向已在 issue body 明確選定、命名/範圍/trade-off 零 open questions、遵循既有 flag pattern）→ 跳過 discuss，直接 spectra-propose。
[Unattended batch：SDD chain（propose → apply）依 Phase 3b 執行；本案排 Wave C 尾（最重）]

Risks

• GraphQL schema 漂移（Discussions API 較新）— references 檔記 schema 版本假設
• dedup 的 search 成本（issues body 全文找 URL）— bounded by discussions 數

Residue

「latest-comment sentiment」resolution 偵測（stretch goal）不做 — answerChosenAt 是本案的誠實邊界；sentiment 判讀留人工。

Vagueness Pre-check

• V1: 1 — Expected 與 Design constraints 由使用者自書，粒度到 flag 名與 API 欄位
• V4: 2 — 完成 = 兩 flag + references + 測試；回文行為的 unattended 邊界由本 diagnosis 補定
• Triggered: no

[Layer V: V1=1 V4=2, not triggered; unattended mode]

Sister Concerns Filed (mid-diagnose, v2.47.0+ #528)

(none — cross-repo 的 che-ical-mcp discussions 已由使用者手動收尾)

---

Source: /idd-all batch drain (unattended), 2026-07-06

[kiki830621]

Spectra change created（focused batch drain, 2026-07-11）

→ see spectra change: discussions-intake-bridge（parked — /spectra-apply discussions-intake-bridge 會 auto-unpark 並開始實作）

Artifacts：proposal / design（D1 shared reference、D2 idd-list Step 2.7、D3 provenance + draft-and-confirm + unattended draft-only、D4 drift-guard）/ spec discussions-intake（4 requirements + 5 scenarios）/ tasks（6 tasks，TDD RED-first）。spectra validate ✓；analyze 殘 4 個 design-topic 字面匹配 warning（requirement coverage 已全清）。

Per diagnosis opt-out 裁決跳過 discuss，direction 依 issue body 自書約束。實作（apply）為下一步 — 由使用者觸發。

[kiki830621]

Implementation Complete

Checklist (synced from spectra tasks.md, 6/6)

• 1.1 references/discussions-intake.md — 三約束 + 三 GraphQL query + schema 假設註記
• 1.2 drift-guard scripts/tests/discussions-intake/test.sh（30 assertions，RED-first：ref 11 綠 / SKILL 19 紅）
• 2.1 idd-list Step 2.7 — --discussions opt-in、probe→filter→dedup→actionable 區塊、降級不 abort、fetch_discussions bootstrap
• 3.1 idd-issue Step 1.7 — --from-discussion、## Provenance verbatim blockquote、draft-and-confirm 回文（unattended draft-only）、seed_from_discussion bootstrap
• 4.1 usecase-routing row 28 + README 段
• 4.2 全 plugin suite 0 fail；spectra validate ✓；state all_done

Changes

• （PR feat: Discussions intake bridge — idd-list --discussions + idd-issue --from-discussion #255 branch idd/221-discussions-intake）feat: Discussions intake bridge — via Spectra change discussions-intake-bridge

Next: verify pending — PR review 後 merge，再 /idd-close + spectra-archive

[kiki830621]

Closing Summary

Problem

IDD 的所有 intake 面（idd-list triage、idd-issue 建案）只綁 Issues tab，但真實 bug report / feature request 常以 GitHub Discussions（尤其 Q&A）抵達 — Discussions 無 REST API，gh issue list 天然不含。實證：2026-07-04 /idd-list 對 che-ical-mcp 回報 0 open issues，而一條權限 bug 的完整生命週期（回報 → 診斷 → 「已修好」確認）都在 Discussion 105 — IDD 對整條 channel 全盲。

Root Cause

盲點是結構性的：Discussions 只有 GraphQL API，且 intake 工具從未把它納入掃描面。

Solution

Spectra change discussions-intake-bridge（opt-out 跳過 discuss — 方向由 issue body 自書約束定案；PR #255，commit e6f3b28）：

• idd-list --discussions（Step 2.7，opt-in）：hasDiscussionsEnabled probe（disabled/query 失敗 → 一行 skip note，絕不 abort）→ GraphQL 抓 open discussions（first 50）→ filter（Q&A/Ideas ∧ answerChosenAt: null）→ dedup（任何 issue 引用該 URL 即剔除）→ Discussions (actionable) 區塊 + suggested next；零 actionable 印一行 note 不沉默
• idd-issue --from-discussion <url|number>（Step 1.7）：GraphQL 讀 discussion → ## Provenance（URL + author + opening post verbatim blockquote）seed 草稿 → 走正常 pipeline（不繞過任何 gate）→ 建案後 back-reference 回文 draft-and-confirm（attended 確認才 post；unattended draft-only 絕不 post）
• 鐵律 no-auto-file：bridge 只 surface、人判斷 — Discussion 105 被發現時已解決，機械建案只會製造 noise（此約束以 normative 形式進 spec + reference + 兩個 SKILL）
• 契約 + GraphQL 樣板 single-source：references/discussions-intake.md（含 schema 假設註記）

Verification

• Drift-guard discussions-intake/test.sh 30/30（RED 11/30 → GREEN）on merged main；全 plugin suite 0 fail；CI pass；spectra validate ✓、state all_done（6/6 tasks）
• 6-AI ensemble verify 未跑（Fable session 限制）— 使用者裁決以 PR review 替代後 merge

Residue Acknowledgement

「latest-comment sentiment」resolution 偵測（stretch goal）維持不做 — answerChosenAt 是機械誠實邊界，情緒判讀留人工（診斷 Residue，本次照案落地）。無 follow-up。

Changes

• e6f3b28 feat: Discussions intake bridge — via PR feat: Discussions intake bridge — idd-list --discussions + idd-issue --from-discussion #255（Spectra change discussions-intake-bridge，archive 隨後）