Merge pull request #231 from PsychQuant/idd/199-bridge-state-path-migration

fix: idd-comment bridge state onto .claude/.idd/state/bridge.json (namespace migration completion)

Author: kiki830621

.claude/.idd/attachments/issue-199/_manifest.json

@@ -0,0 +1,6 @@
+{
+  "issue": 199,
+  "fetched_at": "2026-07-05T15:19:46Z",
+  "fetched_by": "idd-diagnose",
+  "files": []
+}

plugins/issue-driven-dev/README.md

@@ -89,8 +89,8 @@ GitHub mentions are an irreversible side effect; the rule is mandatory not advis
 
 When `spectra-discuss` is interrupted mid-flow to invoke an IDD skill (e.g. "let me capture this finding to the issue"), the bridge protocol preserves and resumes context:
 
-- **Step 0.7 Detect** — `--resume-spectra="<topic>"` flag, `--source` contains `spectra-discuss`, `spectra list --json` shows in-flight changes, or `.claude/state/idd-bridge.json` exists → `SPECTRA_BRIDGE_ACTIVE=1`
-- **Step N-1 Bookmark** — `.claude/state/idd-bridge.json` written with verbatim `spectra_topic` + `issue_url` + `open_questions[]` + `idd_action_url` + `next_step_hint`
+- **Step 0.7 Detect** — `--resume-spectra="<topic>"` flag, `--source` contains `spectra-discuss`, `spectra list --json` shows in-flight changes, or `.claude/.idd/state/bridge.json` exists (legacy fallback: `.claude/state/idd-bridge.json`) → `SPECTRA_BRIDGE_ACTIVE=1`
+- **Step N-1 Bookmark** — `.claude/.idd/state/bridge.json` written with verbatim `spectra_topic` + `issue_url` + `open_questions[]` + `idd_action_url` + `next_step_hint`
 - **Step N Resume Prompt** — final output prints a clearly-delimited `↩ Resume spectra-discuss` block with a copy-pasteable `/spectra-discuss <topic>...` prompt
 
 Hard rules: never auto-invoke `/spectra-discuss` (user controls pacing); never paraphrase `spectra_topic`; resume prompt is the actual recovery — bookmark file is convenience.

plugins/issue-driven-dev/scripts/tests/bridge-path/test.sh

@@ -0,0 +1,24 @@
+#!/usr/bin/env bash
+# test.sh — drift lock for spectra-bridge state path (#199)
+# idd-comment must READ new-path-first (legacy fallback allowed) and WRITE the
+# new path ONLY. rules/spectra-bridge.md L116 is the contract.
+set -u
+HERE="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+SKILL="$HERE/../../../skills/idd-comment/SKILL.md"
+PASS=0; FAIL=0
+ok(){ echo "  ✓ $1"; PASS=$((PASS+1)); }
+no(){ echo "  ✗ $1"; FAIL=$((FAIL+1)); }
+
+# 1. write path: mkdir/cat must target .claude/.idd/state/, never .claude/state/
+if grep -qE 'cat > \.claude/state/idd-bridge\.json|mkdir -p \.claude/state' "$SKILL"; then
+  no "no legacy-path WRITE in idd-comment SKILL.md"
+else ok "no legacy-path WRITE in idd-comment SKILL.md"; fi
+# 2. new path present as primary read + write
+grep -q '\.claude/\.idd/state/bridge\.json' "$SKILL" && ok "new path referenced" || no "new path referenced"
+# 3. legacy path may appear ONLY as documented fallback (with the word fallback/legacy nearby)
+LEGACY_LINES=$(grep -n '\.claude/state/idd-bridge\.json' "$SKILL" | grep -viE 'fallback|legacy' | wc -l | tr -d ' ')
+[ "$LEGACY_LINES" = "0" ] && ok "legacy path only in fallback context" || no "legacy path only in fallback context ($LEGACY_LINES bare refs)"
+
+echo "================================"
+echo "Results: $PASS passed, $FAIL failed"
+[ "$FAIL" -eq 0 ]

plugins/issue-driven-dev/skills/idd-comment/SKILL.md

@@ -74,15 +74,15 @@ idd-issue source.docx       # auto-trigger when source contains ≥2 findings
 
 ```
 TaskCreate(name="parse_args", description="Parse #NNN + --type + --body / --quote / --source / --target / --target-comment / --deadline / --mention / --resume-spectra 等 options")
-TaskCreate(name="detect_spectra_context", description="Step 0.7: 偵測是否從 spectra-discuss 中斷進來（--resume-spectra flag / --source 含 spectra / spectra list 有 in-flight / .claude/state/idd-bridge.json）— 詳見 rules/spectra-bridge.md")
+TaskCreate(name="detect_spectra_context", description="Step 0.7: 偵測是否從 spectra-discuss 中斷進來（--resume-spectra flag / --source 含 spectra / spectra list 有 in-flight / .claude/.idd/state/bridge.json（legacy fallback: .claude/state/idd-bridge.json）— 詳見 rules/spectra-bridge.md")
 TaskCreate(name="validate_type_requirements", description="依 type 檢查必填欄位（decision 要 quote、note 要 source、link 要 target、errata 要 target-comment）")
 TaskCreate(name="resolve_mentions", description="Step 1.5: 若有 --mention 或 body 含 @xxx，強制走 rules/tagging-collaborators.md 協定（gh api 取 collaborators → fuzzy match → AskUserQuestion fallback → 用 @login 不用 display name）")
 TaskCreate(name="build_comment_body", description="按 type 對應 template 組 markdown（emoji header + blockquote + body + metadata marker），插入已驗證的 @login mentions")
 TaskCreate(name="verify_mentions", description="post 前 grep body 的 @\\w+ 全部 cross-check 已驗證的 collaborator set；未驗證 token 直接 abort")
 TaskCreate(name="post_comment", description="gh issue comment #NNN 用 --body-file 避免 escape 問題；errata type 額外 auto-call idd-edit")
 TaskCreate(name="report_result", description="輸出 ✓ Comment posted + URL；errata type 加報 idd-edit 結果")
 TaskCreate(name="auto_update_body", description="跑 /idd-update #NNN 同步 issue body Current Status（強制，常被漏；同 idd-close Step 6 模式）")
-TaskCreate(name="spectra_bridge_resume", description="Step 7: 若 SPECTRA_BRIDGE_ACTIVE，寫 .claude/state/idd-bridge.json bookmark + 輸出 ↩ Resume spectra-discuss 區塊（rules/spectra-bridge.md）")
+TaskCreate(name="spectra_bridge_resume", description="Step 7: 若 SPECTRA_BRIDGE_ACTIVE，寫 .claude/.idd/state/bridge.json bookmark + 輸出 ↩ Resume spectra-discuss 區塊（rules/spectra-bridge.md）")
 ```
 
 完成每一步立即 `TaskUpdate → completed`。**靜默完成 = 違規**。**TaskCreate 清單 = 真實的步驟清單；任何寫在 skill 裡但沒列進 TaskCreate 的步驟，都視為 skill 的 bug，必須補進 Task 清單。**
@@ -120,9 +120,16 @@ if command -v spectra >/dev/null 2>&1; then
   fi
 fi
 
-# Signal 4: bookmark 已存在
-if [ -f ".claude/state/idd-bridge.json" ]; then
-  ACTIVE=$(jq -r '.active_spectra_session // false' .claude/state/idd-bridge.json 2>/dev/null)
+# Signal 4: bookmark 已存在 — new path first, legacy fallback（#199; rule L116 契約）
+BRIDGE_FILE=""
+if [ -f ".claude/.idd/state/bridge.json" ]; then
+  BRIDGE_FILE=".claude/.idd/state/bridge.json"
+elif [ -f ".claude/state/idd-bridge.json" ]; then   # legacy fallback (#199)
+  BRIDGE_FILE=".claude/state/idd-bridge.json"   # legacy fallback
+  echo "ℹ Found legacy bridge at .claude/state/idd-bridge.json. Move to .claude/.idd/state/bridge.json."
+fi
+if [ -n "$BRIDGE_FILE" ]; then
+  ACTIVE=$(jq -r '.active_spectra_session // false' "$BRIDGE_FILE" 2>/dev/null)
   [ "$ACTIVE" = "true" ] && SPECTRA_BRIDGE_ACTIVE=1
 fi
 ```
@@ -365,8 +372,8 @@ Skill(skill="issue-driven-dev:idd-update", args="#NNN")
 #### 7.1 寫 bookmark 檔
 
 ```bash
-mkdir -p .claude/state
-cat > .claude/state/idd-bridge.json <<EOF
+mkdir -p .claude/.idd/state
+cat > .claude/.idd/state/bridge.json <<EOF
 {
   "version": 1,
   "created_at": "$(date -u +%Y-%m-%dT%H:%M:%S%z)",
@@ -397,7 +404,7 @@ to continue with full context preserved:
   待解問題:
   ${OPEN_QUESTIONS_BULLETS}
 
-State saved to: .claude/state/idd-bridge.json
+State saved to: .claude/.idd/state/bridge.json
 ═══════════════════════════════════════════════════════════
 ```
 
@@ -467,7 +474,7 @@ HTML comment 在 GitHub 不渲染，但可 parse：
   --body="..."
 ```
 
-→ Step 0.7 detect 命中 → Step 7 寫 `.claude/state/idd-bridge.json` + 印 `↩ Resume spectra-discuss` 區塊讓使用者貼回 spectra session。
+→ Step 0.7 detect 命中 → Step 7 寫 `.claude/.idd/state/bridge.json` + 印 `↩ Resume spectra-discuss` 區塊讓使用者貼回 spectra session。
 
 ## 鐵律