feature: implement check_diagnosis_readiness() helper function (extract from #47 inline bash)

[kiki830621]

Problem

Source: surfaced during /idd-verify #47 (codex P3 #7).

/idd-all-chain Step 0.4 (NEW in #47) 文宣中 references/chain-flow.md 寫:

Future #46 multi-root extension: helper function design preserves N-arg shape (check_diagnosis_readiness(issue_numbers...) → [ready_list, not_ready_list])

但實際 implementation 是 inline bash,沒有 named function。這是「prose claim」而非「實際 code」,#46 multi-root 落地時無法直接 reuse。

Type

feature (refactor + future-proofing)

Expected

把 #47 Step 0.4 的 inline bash logic 抽成 named function:

check_diagnosis_readiness() {
  local issue_numbers=("$@")
  local ready=()
  local not_ready=()
  for n in "${issue_numbers[@]}"; do
    local has=$(gh issue view "$n" -R "$GITHUB_REPO" --json comments \
      | jq -r '[.comments[] | select(.body | contains("## Diagnosis"))] | length')
    if [ "$has" = "0" ]; then
      not_ready+=("$n")
    else
      ready+=("$n")
    fi
  done
  # Return as JSON for parsing
  jq -n --argjson ready "$(printf '%s
' "${ready[@]}" | jq -R . | jq -s .)" \
        --argjson not_ready "$(printf '%s
' "${not_ready[@]}" | jq -R . | jq -s .)" \
        '{ready: $ready, not_ready: $not_ready}'
}

或寫成 helper script scripts/check-diagnosis-readiness.sh。

Priority

P3 (#46 落地時會撞到;先有 #47 落地驗證單 root,再 refactor 為 N-arg 也可)

---

Current Status

Phase: closed
Last updated: 2026-05-11 by idd-close (#69 merged a7ff5f2)

Key Decisions

• Complexity = Plan (Layer P 命中: 2+ files coupled, decision-heavy Path A vs B, risk-sensitive helper signature for feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 reuse)
• Layer V untriggered (V1=2 V4=3)
• 推 Path B ( per manifest-append.sh precedent)

Blocking

• 等 user 跑 /idd-plan feature: implement check_diagnosis_readiness() helper function (extract from #47 inline bash) #51 進 EnterPlanMode 對齊 signature

[kiki830621]

Diagnosis

Type

feature (refactor — extract inline bash to named helper for reusability)

Analysis

Issue body 已含完整實作建議(named function 含 N-arg signature + jq JSON return)。

當前 #47 ship 的 idd-all-chain/SKILL.md Step 0.4 用 inline bash for single root issue。references/chain-flow.md 文宣中聲明 helper 設計成 check_diagnosis_readiness(issue_numbers...) for #46 multi-root reuse — prose claim,not actual code。本 issue refactor 把 inline → named helper,讓 #46 真的可以 reuse。

Two implementation paths:

• Path A: inline function in SKILL.md — bash function 寫在 Step 0.4 code block 上方,call 該 function。Pros:single-file,no new artifact。Cons:bash function 只在 該 invocation scope 內有效,複用度有限
• Path B: helper script scripts/check-diagnosis-readiness.sh — extract 到獨立 script,SKILL.md 內 invoke bash $CLAUDE_PLUGIN_ROOT/scripts/check-diagnosis-readiness.sh #N1 #N2 ...。Pros:cross-skill reuse(其他 skill 也可呼叫)、testable in isolation、跟 manifest-append.sh 同 pattern。Cons:多 1 個 file artifact

推 Path B — 跟 manifest-append.sh 同 pattern + #46 multi-root 真的需要跨 skill reuse。

Impact

• 影響的檔案:
  • plugins/issue-driven-dev/scripts/check-diagnosis-readiness.sh (NEW)
  • plugins/issue-driven-dev/skills/idd-all-chain/SKILL.md Step 0.4(從 inline bash → invoke helper script)
  • plugins/issue-driven-dev/references/chain-flow.md 描述同步 (prose claim 變成 actual reference)
• 影響的使用者流程:行為不變(invocation 介面相同,內部從 inline bash → helper script)
• Backward compat:既有 chain run 行為一致

Strategy

• 寫 scripts/check-diagnosis-readiness.sh accept N args (#N1 #N2 ...),support optional --repo owner/repo flag(沿用 manifest-append.sh 的 args style)
• Output JSON {ready: [N], not_ready: [N]} to stdout
• Set set -euo pipefail,handle gh/jq failure with explicit exit codes (per manifest-append.sh precedent)
• SKILL.md Step 0.4 把 inline bash 改成:READINESS=$(bash $CLAUDE_PLUGIN_ROOT/scripts/check-diagnosis-readiness.sh "#$ROOT_ISSUE"),parse JSON via jq
• 4-case smoke test:single ready / single not-ready / N=2 mixed / non-numeric / gh failure
• chain-flow.md prose:從 "Future feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 hook" 改成 "see scripts/check-diagnosis-readiness.sh for actual signature"

Complexity

Plan (Layer P 命中)

理由:

• 2+ 互依檔案(helper script + SKILL.md 同步;chain-flow.md docs 同步)
• 5+ ordered steps(write script → smoke test → SKILL.md replace inline → docs update → re-verify chain wiring)
• Decision-heavy:Path A vs Path B(本 diagnose 已 lean B 但要 user 確認)
• Risk-sensitive boundary:helper script 是 feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 multi-root 的依賴,signature 設計錯一次後續 cascade — 值得 plan-tier deliberation

Layer V 預計 untriggered(V1=2 fix explicit;V4=3 acceptance criteria 隱含但 clear) — 見 audit trail。

Risks

• Bash array passing across script boundary:scripts/check-diagnosis-readiness.sh #N1 #N2 #N3 簡單,但若 args 含 special chars(unlikely for issue numbers but worth noting)需 quote
• JSON output format breaks future caller:確定 {ready:[], not_ready:[]} schema 後就 frozen — 改 schema = breaking。Mitigation:plan tier 階段 explicit fix
• set -e 在 jq pipe 行為:若 jq 失敗,需確認 abort 不 silent。Mitigation:set -euo pipefail + numeric regex check on output

Vagueness Pre-check

• V1: 2 — fix path 已 explicit (Path B with script body in issue)
• V4: 3 — Acceptance 隱含但 clear (chain still works + feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 can reuse)
• Triggered: no

Recommended Path

Plan → /idd-plan #51(EnterPlanMode 對齊 Path A vs B + signature design)。

[kiki830621]

Implementation Plan (Plan tier)

Tier: Plan (Layer P 命中 per diagnosis) — 2+ coupled files + Path A vs B decision + #46 multi-root signature is risk-sensitive.

Files & Changes

• plugins/issue-driven-dev/scripts/check-diagnosis-readiness.sh (NEW) — N-arg helper following manifest-append.sh precedent (set -u, explicit usage, exit codes, JSON stdout). Accepts <github-repo> <issue-number> [<issue-number>...] and emits {"ready":[N],"not_ready":[N]} to stdout
• plugins/issue-driven-dev/skills/idd-all-chain/SKILL.md — Step 0.4 detection block:replace inline gh issue view ... | jq with bash $CLAUDE_PLUGIN_ROOT/scripts/check-diagnosis-readiness.sh "$GITHUB_REPO" "$ROOT_ISSUE" + parse JSON via jq. Single-arg invocation in v1 (single root issue);N-arg shape preserved for feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 reuse
• plugins/issue-driven-dev/references/chain-flow.md — prose update from "Future feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 hook (currently inline)" → "implemented as scripts/check-diagnosis-readiness.sh (see for actual signature)"

Sequencing & Dependencies

1. Write helper script first with self-contained anchor anchors (set -u, abort on bad input, no dependency on SKILL.md context)
2. Smoke test inline in dev (4 cases: single-ready / single-not-ready / N=2 mixed / non-numeric/gh-failure)
3. SKILL.md replace Step 0.4 inline bash → invoke script + parse JSON
4. chain-flow.md prose update last (depends on script existing for the cross-link to be valid)

All same commit/PR (skill ↔ helper ↔ docs drift is the IDD anti-pattern per #54 lessons).

Decision Points

D1 — Path A (inline function in SKILL.md) vs Path B (separate script):

• Decision: Path B
• Rationale: matches existing precedent (manifest-append.sh is a separate script under scripts/), enables cross-skill reuse for feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 multi-root, testable in isolation, single source of truth for the algorithm
• Alternative considered: Path A — rejected because bash function in SKILL.md fenced block is agent-interpreted instructions, not literally executed (per feature: /idd-all-chain Phase 0 pre-flight check for root issue diagnosis-readiness #47 P1 finding 2 — same lesson that bit Step 6.5 helpers in feature: /idd-close should chain to plugin-update / mcp-update / cli-update for distribution-aware close #45 round 2)

D2 — Helper script argument shape:

• Decision: check-diagnosis-readiness.sh <github-repo> <issue-number> [<issue-number>...]
  • Positional <github-repo> (owner/repo form) as first arg — explicit, no env var dependency, matches manifest-append.sh <repo-root> pattern
  • Variadic issue numbers as remaining args (single root in v1, N issues for feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46)
  • No --repo flag (positional is simpler, matches precedent)
• Rationale: explicit positional args fail-fast on misuse;variadic enables feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 multi-root without API change

D3 — Output format:

• Decision: JSON stdout {"ready":[1,2],"not_ready":[3]} (single object, two arrays of integer issue numbers)
• Rationale: machine-parseable via jq one-liner, schema explicit, integers preserve numeric ordering (not strings — caller doesn't need to coerce)
• Alternative considered: tab-separated ready=1,2\tnot_ready=3 — rejected (jq is already in IDD's hard-deps so JSON is free)

D4 — Diagnosis detection regex (port from #47):

• Decision: keep test("(?m)^## Diagnosis") line-anchored regex (per fix: idd-all-chain Step 0.4 jq filter use anchored regex (avoid false-positive on quoted text) #53 narrowing fix)
• Rationale: already validated in fix: idd-all-chain Step 0.4 jq filter use anchored regex (avoid false-positive on quoted text) #53;helper script must match SKILL.md behavior exactly (not introduce drift)

D5 — Failure modes:

• Decision (per manifest-append.sh precedent):
  • exit 0 — success (JSON written to stdout)
  • exit 1 — gh or jq failure (auth / network / non-existent issue) — print error to stderr
  • exit 2 — usage error (missing args) — print usage to stderr
• Rationale: same exit code convention as manifest-append.sh for cross-script consistency

Risks & Mitigations

Risk	Probability	Mitigation
R1 — gh issue view failures swallowed: per-issue gh call could fail silently if 2>/dev/null	Medium	set -u + explicit numeric regex check on per-issue jq output;abort with clear stderr message
R2 — JSON output schema breaks future caller: once shipped, format-frozen	Low	Plan tier explicit decision (D3);use single-line JSON not multi-line (less ambiguity)
R3 — Bash array passing across script boundary: special chars in args	Very low	Issue numbers are integers (regex-validated);quote "$@" properly
R4 — Skill ↔ script drift over time: SKILL.md inline call must match script signature	Medium	Both ship in same commit;chain-flow.md doc lists exact invocation
R5 — Empty issue list edge case: caller passes 0 issue numbers	Low	exit 2 usage error + clear message

Test Plan

(No automated test framework per #62 follow-up — manual smoke matrix:)

#	Setup	Args	Expected output	Exit
1	issue with ## Diagnosis comment (e.g. #44)	PsychQuant/issue-driven-development 44	{"ready":[44],"not_ready":[]}	0
2	issue without diagnosis (e.g. fresh #X)	PsychQuant/issue-driven-development <fresh>	{"ready":[],"not_ready":[<fresh>]}	0
3	mixed N=2	PsychQuant/issue-driven-development 44 <fresh>	{"ready":[44],"not_ready":[<fresh>]}	0
4	non-existent issue	PsychQuant/issue-driven-development 999999	(gh error to stderr)	1
5	missing args	<empty>	usage to stderr	2

Plus integration smoke: invoke chain-shell on a fresh issue + ready issue both to confirm v1 single-root path still works.

Out-of-scope (will NOT be touched)

• ✗ feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 multi-root extension — separate issue;helper signature designed for it but actual chain-shell loop refactor for N roots is feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46's job
• ✗ Removing feature: /idd-all-chain Phase 0 pre-flight check for root issue diagnosis-readiness #47 inline bash from SKILL.md beyond Step 0.4 — only Step 0.4 detection;Step 0.4 prose / AskUserQuestion stays as agent-level
• ✗ Test infra to run smoke matrix automatically — [docs] Add chain-vs-bulk note in usecase-routing.md decision tree section (verify follow-up from #49) #62 follow-up
• ✗ Caching ## Diagnosis detection across chain runs — premature optimization
• ✗ Extension to other gate checkpoints (e.g. spec-readiness for Spectra) — separate concern

Tangential Observations (filed mid-plan, v2.42.0+ #524)

Tangential Observations: none surfaced — plan captured all material concerns in Decisions / Risks / Out-of-scope. Only plausible candidate (scripts/ exit code convention drift across plugins) is spec-convention concern not #51-specific dropped sub-concern.

[kiki830621]

Implementation Complete

Checklist (synced from TaskList)

• plugins/issue-driven-dev/scripts/check-diagnosis-readiness.sh (NEW) — variadic helper <github-repo> <issue-number>... → JSON stdout, manifest-append.sh exit-code precedent, test("(?m)^## Diagnosis") regex per fix: idd-all-chain Step 0.4 jq filter use anchored regex (avoid false-positive on quoted text) #53 → commit e018465
• plugins/issue-driven-dev/skills/idd-all-chain/SKILL.md Step 0.4 — replaced inline gh+jq bash with helper invocation + JSON parse;variable rename HAS_DIAGNOSIS → NOT_READY_COUNT;downstream prose updated → commit 7d8027b
• plugins/issue-driven-dev/references/chain-flow.md — replaced "Future feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 hook (currently inline)" prose with "Implemented as scripts/check-diagnosis-readiness.sh" (variadic positional signature documented) → commit 7d8027b

Legend: - [x] done · - [~] skipped · - [-] won't fix
idd-close will refuse close if any - [ ] remains.

Changes

• e018465 feat(check-diagnosis-readiness): NEW helper script (Refs feature: implement check_diagnosis_readiness() helper function (extract from #47 inline bash) #51)
• 7d8027b refactor(idd-all-chain): Step 0.4 invokes check-diagnosis-readiness.sh helper (Refs feature: implement check_diagnosis_readiness() helper function (extract from #47 inline bash) #51)

Files Changed

 plugins/issue-driven-dev/references/chain-flow.md  |  2 +-
 plugins/issue-driven-dev/scripts/check-diagnosis-readiness.sh | 89 ++++ (NEW, executable)
 plugins/issue-driven-dev/skills/idd-all-chain/SKILL.md         | 31 +++/-14
 3 files changed, 108 insertions(+), 14 deletions(-)

Smoke Tests (manual, 7 cases — all PASS)

#	Setup	Args	Output	Exit
1	issue with ## Diagnosis (#44)	PsychQuant/issue-driven-development 44	{"ready":[44],"not_ready":[]}	0 ✓
2	issue without diagnosis (#66)	PsychQuant/issue-driven-development 66	{"ready":[],"not_ready":[66]}	0 ✓
3	mixed N=3 (#44 ready, #66 not, #51 ready)	... 44 66 51	{"ready":[44,51],"not_ready":[66]}	0 ✓
4	non-existent issue	... 999999	stderr error	1 ✓
5	missing args	(no issue numbers)	usage to stderr	2 ✓
6	malformed issue arg	... abc	usage to stderr	2 ✓
7	malformed repo arg	not-a-repo-form 44	usage to stderr	2 ✓

Decision Points (resolved per Plan)

• D1 Path B (separate script) — matches manifest-append.sh precedent
• D2 positional <github-repo> <issue-number>... — variadic, no flag
• D3 JSON {"ready":[N],"not_ready":[N]} integer arrays
• D4 detection regex: test("(?m)^## Diagnosis") (fix: idd-all-chain Step 0.4 jq filter use anchored regex (avoid false-positive on quoted text) #53 narrowing)
• D5 exit codes: 0/1/2 per manifest-append.sh

Sister Bugs Filed (mid-impl, v2.44.0+ #526)

(none surfaced — refactor was clean extraction;manifest-append.sh precedent guided structure;Implementation Plan + smoke loop captured all considerations。No grep paths revealed adjacent broken patterns。Meta-observation about #61 (sister substring scans) potentially using new helper for drift-avoidance is already covered by that issue — no new follow-up needed.)

Scope Compliance

✅ All changes within #51 scope:

• 1 NEW script + 2 EDIT files
• 2 commits, each Refs #51 only
• No accidental edits to other skills
• feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 multi-root chain integration explicitly out-of-scope per Plan (separate issue)
• Commits per IDD discipline (no Closes trailer)

Empirical Verification (round-trip)

• Helper script invoked from outside SKILL.md context → returns valid JSON for all 7 smoke cases
• SKILL.md Step 0.4 invocation pattern uses standard bash $CLAUDE_PLUGIN_ROOT/scripts/... (same as manifest-append.sh callers + process-attachments.sh)
• chain-flow.md cross-link points at actual file (no longer prose-only claim)

Next: verification pending

[kiki830621]

Verify (via PR #69) — PASS

Result: PASS — 0 P1/P2/P3 remaining (3 verify rounds: 1 P1 + 4 P3 all resolved)
Full report: #69 (comment)

This issue's findings: codex-only ensemble (Anthropic limit;Codex carried 3 rounds). Round-by-round table in master report. Empirical 7/7 smoke + 3 regression cases all PASS.

PR ready for merge + /idd-close #51 after.

[kiki830621]

Closing Summary

Problem

/idd-all-chain Step 0.4 (NEW in #47) detection logic was inline bash in SKILL.md, but references/chain-flow.md claimed the helper was designed as check_diagnosis_readiness(issue_numbers...) N-arg function for #46 multi-root chain reuse — prose claim, not actual code. #46 落地時無法 reuse 一個並未真正存在的 helper。

Surfaced during /idd-verify #47 (codex P3 #7) as a doc-vs-code drift. Plan tier issue: must fix before #46 multi-root chain ships, otherwise #46 inherits the prose-only contract.

Root Cause

When #47 implemented Step 0.4, the Implementation kept gh+jq detection inline in SKILL.md (single-root case sufficient). The "Future #46 hook" prose was added aspirationally — describing the intended N-arg shape — but no helper extraction happened. Result: chain-flow.md documented an API that only existed in plain text. Without extraction, #46 multi-root would either:

1. Re-implement detection inline (duplication + drift surface)
2. Refactor at feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 time (delays feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 + risks scope creep)

Plan tier #51 chose Path B: extract NOW, ship v1 single-root invocation, lock signature for #46.

Solution

Extract detection into plugins/issue-driven-dev/scripts/check-diagnosis-readiness.sh following manifest-append.sh precedent:

• Variadic positional signature: <github-repo> <issue-number> [<issue-number>...] — single-root in v1, N-arg ready for feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46
• JSON stdout: {"ready":[N,...],"not_ready":[N,...]} integer arrays (machine-parseable, schema locked)
• Detection regex: test("(?m)^## Diagnosis") — preserves fix: idd-all-chain Step 0.4 jq filter use anchored regex (avoid false-positive on quoted text) #53 narrowing fix (line-anchored, avoids quoted-history false-positives)
• Exit codes: 0 success / 1 gh-jq failure / 2 usage error — matches manifest-append.sh cross-script convention
• Strict input validation: positive integer regex ^[1-9][0-9]*$ (rejects 0;GitHub has no issue #0), owner/repo shape check on <github-repo>
• Defensive bash: set -u + numeric regex check on per-issue jq output, empty-array safe via nullglob + ${ARRAY[@]+...} expansion

Wire: idd-all-chain/SKILL.md Step 0.4 detection block replaced inline gh+jq with bash $CLAUDE_PLUGIN_ROOT/scripts/check-diagnosis-readiness.sh "$GITHUB_REPO" "$ROOT_ISSUE" + JSON parse via jq;variable rename HAS_DIAGNOSIS → NOT_READY_COUNT (matches script return shape).

Doc: references/chain-flow.md prose updated from "Future #46 hook (currently inline)" → "Implemented as scripts/check-diagnosis-readiness.sh (variadic positional signature)" — prose now matches code, contract is real.

Verification

• 3 verify rounds (codex-only, Anthropic API limit-blocked Claude reviewers across all rounds):
  • Round 1: 1 P1 (SKILL.md:212 stale "Future feature: /idd-all-chain accept multiple root issues with DFS/BFS traversal (default DFS) #46 hook" prose still claimed inline implementation) + 3 P3 (TaskCreate desc / chain-flow spacing / script regex allowed 0)
  • Round 2: All 4 fixed but 1 NEW P3 typo introduced (same invocation;ready spacing pattern in SKILL.md:212 — the line I just rewrote)
  • Round 3: typo fixed → PASS (0 P0/P1/P2/P3 remaining)
• Empirical 7+3 smoke matrix all PASS:
  • Detection: ready (feature: /idd-all chain-solve mode — 自動接續解 spawned issues + 單 review PR #44), not-ready ([bug] Verify common-plugins.md plugin-update Phase 1.5 cascade claim (mid-plan tangential from #45) #66), mixed N=3, non-existent (exit 1), missing args (exit 2), malformed issue (exit 2), malformed repo (exit 2)
  • Regression after regex tighten: 0 → exit 2 (rejected), positive integers still work, ready/not-ready unchanged
• 6-AI ensemble degraded mode: codex carried all 3 rounds (small scope: 162→181 line diff vs feature: /idd-close should chain to plugin-update / mcp-update / cli-update for distribution-aware close #45's 321) — converged in 2 fix rounds + 1 polish vs feature: /idd-close should chain to plugin-update / mcp-update / cli-update for distribution-aware close #45's 3 fix rounds

Changes

4 commits squashed in PR #69 → a7ff5f2 cluster:

• e018465 feat(check-diagnosis-readiness): NEW helper script
• 7d8027b refactor(idd-all-chain): Step 0.4 invokes helper + chain-flow prose update
• 17b507b fix(idd-all-chain): round-2 verify FAIL fixes (P1 prose + 3 P3)
• fcf6fc8 fix(idd-all-chain): round-3 typo (invocation; ready spacing)
• Squash main: a7ff5f2 feat(check-diagnosis-readiness): extract Step 0.4 helper script (feature: implement check_diagnosis_readiness() helper function (extract from #47 inline bash) #51) (feat(check-diagnosis-readiness): extract Step 0.4 helper script (#51) #69)

Files Changed

 plugins/issue-driven-dev/references/chain-flow.md             | +2/-2
 plugins/issue-driven-dev/scripts/check-diagnosis-readiness.sh | +89 (NEW, executable)
 plugins/issue-driven-dev/skills/idd-all-chain/SKILL.md        | +21/-15
 3 files changed, 111 insertions(+), 16 deletions(-)

Plan tier — Decision Points (resolved)

• D1 Path B (separate script under scripts/) — matches manifest-append.sh precedent
• D2 Positional <github-repo> <issue-number>... variadic — no flag, simpler than --repo
• D3 JSON {"ready":[N],"not_ready":[N]} integer arrays
• D4 test("(?m)^## Diagnosis") regex — preserves fix: idd-all-chain Step 0.4 jq filter use anchored regex (avoid false-positive on quoted text) #53 line-anchor narrowing
• D5 Exit codes 0/1/2 per manifest-append.sh

Distribution Sync (Step 6.5 manual demo since deployed cache v2.56 lacks Step 6.5; source v2.57 has it)

infer_distribution_type ~/Developer/issue-driven-development → plugin
resolve_plugin_name → "issue-driven-dev"
CHAIN_DESC = "/plugin-tools:plugin-update issue-driven-dev"

User decision pending after this close.

Closing Follow-ups Filed (v2.45.0+ #527)

(none — #46 multi-root extension is parent target already filed;keyword "Future #46" + "ready for #46" in summary all cross-link to existing #46 tracking issue, no orphan mentions)

Distribution Sync (Step 6.5 manual demo — UPDATE)

• Detected: plugin (issue-driven-dev)
• PLUGIN_NAME: issue-driven-dev
• Choice: skip — current marketplace at v2.57.0 (just synced after feature: /idd-close should chain to plugin-update / mcp-update / cli-update for distribution-aware close #45 close), feature: implement check_diagnosis_readiness() helper function (extract from #47 inline bash) #51 changes will batch with future closes (feature: idd-verify orchestration playbook (subagent_type guidance + recovery protocol) #52, multi-finding mode: jsonl run log 被 repo .gitignore 阻擋(.claude/ 是常見 gitignore pattern,衝突 D2 commit 默認) #55) into single v2.57 → v2.58 bump
• At: 2026-05-10T14:59:55Z