cluster: chain follow-ups (#49 docs cross-link + #53 jq regex anchor)

[kiki830621]

Refs #49 #53

Summary

Cluster of 2 chain follow-up issues from #47 verify cycle:

• fix: idd-all-chain Step 0.4 jq filter use anchored regex (avoid false-positive on quoted text) #53 (bug fix) — /idd-all-chain Step 0.4 jq filter use anchored regex test("(?m)^## Diagnosis") instead of contains("## Diagnosis") to avoid false-positive on quoted history / mid-text mentions
• docs: clarify #37 close reason — supersession by #44 chain-solve? (sister from #48 diagnosis) #49 (docs) — references/usecase-routing.md row 27 added: chain-solve vs bulk-solve semantic 差異 + feature: /idd-all (無參數) bulk-solve mode — AI 自動 sequence + bundle 所有 open issue #37 parked status confirmation + feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 future cross-link

Per-issue checklist

#53

• SKILL.md Step 0.4 jq filter regex anchor
• Smoke test 4/4 PASS (canonical / quoted / mid-text / real-comment-body)

#49

• usecase-routing.md row 27 + semantic 差異 prose
• feature: /idd-all (無參數) bulk-solve mode — AI 自動 sequence + bundle 所有 open issue #37 parked-not-superseded confirmation cross-link

Verification

• Pre-merge: idd-verify pending (run /idd-verify --pr <N>)
• Manual smoke test 4/4 PASS for fix: idd-all-chain Step 0.4 jq filter use anchored regex (avoid false-positive on quoted text) #53 jq regex behavior
• docs: clarify #37 close reason — supersession by #44 chain-solve? (sister from #48 diagnosis) #49 doc renders properly (markdown table + blockquote)

Checklist

• Diagnose ✓ (both issues, batch diagnosed 2026-05-10)
• Implement (2 commits, sister)
• Verify (run /idd-verify --pr <N>)
• Pending: human review of cluster PR + /idd-close #49 #53 after merge

---

🤖 Generated by /idd-implement cluster-PR mode. Do NOT add 'Closes #N' trailers — IDD discipline requires manual /idd-close per issue after merge for checklist gate + per-issue closing summary。

[kiki830621]

Verify Report — PR #58

Engine

Agent Team (5 Claude reviewers: requirements / logic / security / regression / devils-advocate) + Codex CLI (gpt-5.5 xhigh)

Aggregate

PASS — 0 blocking, 7 follow-up advisories (file as P3 issues)

Scope coverage

PR refs: #49, #53
Verified scope: #49, #53
Cluster integrity: ✓ (2 commits, single-file each, Refs #N discipline preserved)

---

#53 — chain-shell diagnosis-readiness false-positive on quoted comments

Requirements coverage: 5/5 FULLY met

#	Severity	Finding	Source	Action
1	P3	Leading whitespace narrowing — ## Diagnosis (CommonMark legitimate 1-3 space indent) 從 substring true → 新 anchored regex false。Canonical IDD diagnosis comments 為 col-0,實務上不會踩到;但若 user 手動 paste 帶 indent 會 false-negative	team:devils-advocate (HIGH self-rated) + codex (ACCEPTED RISK)	Follow-up
2	P3	Fenced code block 內 col-0 ## Diagnosis 仍 match true(documentation-style example commit body)。修法需 markdown-aware parser,屬 over-engineering	team:devils-advocate + codex	Follow-up
3	P3	Sister substring scans 仍存在 — idd-all/SKILL.md:441,524 (Python substring), idd-list/SKILL.md:115, idd-update/SKILL.md:120 用 ## Diagnosis 做 phase 推斷,同樣 false-positive 風險	team:regression + codex	Follow-up (out-of-scope per Implementation Plan)
4	P3	Repo 缺 test infra(tests/ / *.bats zero hit)— 4/4 smoke test 是 self-reported, 半年後無法 reproduce。建議加 shell test fixture	team:devils-advocate (HIGH structural debt)	Follow-up

Backward-compat verification:

• gh issue view 44/46/48 既有 canonical diagnosis comments — old contains 與新 test() 結果完全一致 ✓
• jq 1.8.1 本機驗證 (?m)^ multiline mode 行為正確 ✓
• 4 條 smoke test PASS(line-start true / quoted false / mid-text false / canonical with sub-headings true)✓

---

#49 — chain-solve vs bulk-solve disambiguation in usecase-routing.md

Requirements coverage: 5/6 FULLY + 1 PARTIAL

#	Severity	Finding	Source	Action
5	P3	Decision tree section (line 11-26) 未補 chain vs bulk note。Implementation Plan 提及但實作 narrow 到 row 27 + blockquote。Acceptance 已透過 row 27 達成,但與 plan letter 有微小落差	team:requirements (49.5) + team:regression + codex	Follow-up (or accept as plan-internal scope narrowing)
6	P3	Row 61 plain text #44 chain-solve 沒給 issue URL。GitHub auto-linker 在 web UI 會 render,raw markdown viewer 不會。建議補 [#44](url) 達 cross-link 一致性	team:regression + codex	Follow-up (cosmetic)
7	P3	Cluster-PR relatedness criterion 弱:#49 (docs) + #53 (jq fix) 是 unrelated #47 follow-ups,non-overlap file/skill。建議在 references/batch-and-cluster.md formalize "cluster-PR eligibility = same-file OR same-skill OR same-root-issue (chain only)"	team:devils-advocate (MEDIUM)	Follow-up (convention-level)

Cross-cutting verifications:

• Markdown table column count 5/5/5 (header / row / separator) ✓
• Cross-link URLs https://github.com/PsychQuant/issue-driven-development/issues/{37,46} 正確 ✓
• feature: /idd-all (無參數) bulk-solve mode — AI 自動 sequence + bundle 所有 open issue #37 CLOSED (parked) + feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 OPEN — state 與 prose claim 一致 ✓
• Row 1-26 沒有 conflicting "all unresolved" / "bulk" 字眼 ✓

---

Devil's Advocate adversarial review summary

DA 對 7 個 challenge 實際嘗試 break design,結論:

• 1 confirmed regression (Challenge 2 leading whitespace) — Codex 獨立判定為 ACCEPTED RISK,canonical 未踩到,降為 P3 follow-up
• 1 structural debt (Challenge 6 — no test infra) — P3 follow-up
• 1 partial gap (Challenge 7 — fenced-code false-positive) — P3 follow-up,markdown-aware 屬 over-engineering
• 4 challenges 嘗試但 break 不掉(jq compat / row 27 redundancy / blockquote 位置 / cluster-PR — 都是 architectural trade-offs)

DA verdict: "FAIL with concerns";aggregate 上方 PASS — 因 5/6 sources 不認為 leading whitespace 阻擋(canonical 不踩到,narrowing 是設計意圖)。

Security & Regression

Security: PASS (6/6 checks)

• jq regex pattern hardcoded、anchored、無 backtracking 風險
• Cross-link URLs verified,non-typosquat
• Shell quoting 正確(既有,本 PR 未動)
• Numeric guard 保留 ([[ "$HAS_DIAGNOSIS" =~ ^[0-9]+$ ]])

Regression: PASS (7/7 checks)

• Existing ## Diagnosis comments backward-compat ✓
• Cluster-PR Refs #N discipline ✓ (ef4686a Refs fix: idd-all-chain Step 0.4 jq filter use anchored regex (avoid false-positive on quoted text) #53 / 4659c3e Refs docs: clarify #37 close reason — supersession by #44 chain-solve? (sister from #48 diagnosis) #49)
• 2 commits 各動 1 file,無 cross-issue contamination

Scope Compliance

無 scope creep。兩 commits 完全 follow Implementation Plan,改動 31 lines / 2 files。

Next: Merge → /idd-close #49 #53

Per cluster-PR mode discipline:

1. gh pr merge 58 --squash --repo PsychQuant/issue-driven-development
2. /idd-close #49 #53 — 各自獨立 closing summary(per references/batch-and-cluster.md)
3. Step 5b triage 上述 7 個 follow-up advisories 是否 file 為新 issue