[enhancement] idd-list cluster_leader config (lowest | primary) (sister concern from #13)

[kiki830621]

Problem

idd-list v2.51.0+ 將用 deterministic 規則選 cluster leader:lowest issue number。

但 user 心中可能期待選「最早建的 issue」、「主 issue」(label: primary)、或其他。

Type

enhancement / configurability

Why P3

• 預設 lowest number 對 99% 場景可預測且夠用
• Cluster-PR 是進階 workflow,需要 alternative leader 規則的 user 是 power-user
• v2.51.0 先 dogfood 預設規則,觀察是否真有需求再加 config

Recommendation

.claude/issue-driven-dev.local.json 加欄位:

{
  "idd_list": {
    "cluster_leader": "lowest" | "primary"
  }
}

primary mode:看 cluster member 中是否有 priority:primary label,若有則作為 leader;若無則 fall back lowest。

Source

surfaced during /idd-diagnose #13 sister concern surfacing (Step 3.6) — referenced as risk R3

Current Status

Phase: closed
Last updated: 2026-05-07 by idd-close

Resolution

• PR feat(idd-list): markdown-aware fence strip + cluster_leader config (cluster #14 #15) #43 merged → main
• cluster with [refactor] idd-list PR body parsing: ignore #N inside fenced code blocks (sister concern from #13) #14 — cluster_leader config option (lowest | primary, default lowest)

[kiki830621]

Closing Summary (cluster #15 with #14)

Problem

idd-list v2.51.0+ 用 deterministic 規則選 cluster leader:lowest issue number (min(cluster_members))。但 user 心中可能期待:

• 「最早建的 issue」(creation order)
• 「primary issue」(label-marked)
• 「first ref'd in PR body」(authoring order)

當 cluster 中 lowest issue ≠ user 心中的 primary 時,leader display 不直觀。

Root Cause

v2.51.0 設計時取 lowest 為 deterministic + 易預測 default,但 single-source-of-truth 無 user override。本 issue 是該 follow-up。

Solution

Cluster-PR with #14:

#15 part: Step 3.5 加 cluster_leader config 選項:

import json, pathlib

config_path = pathlib.Path('.claude/issue-driven-dev.local.json')
cluster_leader_rule = "lowest"  # default
if config_path.exists():
    cluster_leader_rule = json.loads(config_path.read_text()).get('cluster_leader', 'lowest')
    if cluster_leader_rule not in ('lowest', 'primary'):
        cluster_leader_rule = 'lowest'  # invalid → fallback

def get_leader(refs_list, body, rule):
    if rule == 'primary':
        first = next(
            (int(m) for m in PR_REF_RE.findall(body) if int(m) in refs_list),
            min(refs_list)
        )
        return first
    return min(refs_list)

支援值:

• cluster_leader: "lowest" (預設) — min(cluster_members),deterministic、易預測
• cluster_leader: "primary" — 第一個 ref'd 的 issue (PR body 中出現順序),適合「primary issue + tracked issues」工作流
• 任何其他值 / 缺省 → fallback to "lowest" (graceful degradation)

Backward compat

• cluster_leader 缺省 = v2.51.0 行為 (min)
• Invalid value fallback 到 "lowest",不 break

Verification

Lightweight self-verify PASS:

• Pseudocode 完整,config schema 一致(同 .claude/issue-driven-dev.local.json 既有 fields 共存)
• 對舊行為 backward compat:既有 user 不設此 field 行為不變
• Invalid value 不 crash:cluster_leader: "wrong" → fallback to "lowest" 而非 error

Changes

• 8675b82 feat(idd-list): markdown-aware fence strip + cluster_leader config (Refs [refactor] idd-list PR body parsing: ignore #N inside fenced code blocks (sister concern from #13) #14 [enhancement] idd-list cluster_leader config (lowest | primary) (sister concern from #13) #15)
• e366d53 (squash on main) cluster PR feat(idd-list): markdown-aware fence strip + cluster_leader config (cluster #14 #15) #43 merged

Related (cluster)

• [refactor] idd-list PR body parsing: ignore #N inside fenced code blocks (sister concern from #13) #14 (paired — markdown fence strip in same SKILL.md section)
• idd-list 應該顯示引用 issue 的 open PR 資訊 #13 (great-parent — primary feature, R3 acknowledged this v1 limitation)