[kiki830621]

Refs #502

Summary

• idd-comment Step 0.7 decides whether a call came from a spectra-discuss session; when it says yes, Step 7 writes a bookmark and prints a resume prompt. It said yes whenever the repository had any open Spectra change, whatever the comment was about (reported before as refactor: idd-comment Step 0.7 spectra-bridge over-triggers on unrelated in-flight spectra changes #126). That signal is removed, and the block no longer runs spectra. The other three signals are unchanged: --resume-spectra, a --source that contains spectra-discuss, and a bridge file whose active_spectra_session is true.
• rules/spectra-bridge.md and the two sentences in the plugin's CLAUDE.md and README that list the signals say the same; the two sentences used to say the bridge file only had to exist.
• New capability spectra-bridge-detection with one requirement and two Examples (spec change idd-502-open-change-not-a-bridge-signal, archived).
• New suite spectra-bridge-detect: it takes the block out of SKILL.md and runs it one signal at a time with a stand-in spectra that writes down every call (22 checks).
• Known consequence: a comment made in the middle of spectra-discuss gets the resume prompt only when the caller passes --resume-spectra. Whether to add an automatic path is a question in [enhancement] spectra bridge detection: LOW and INFO findings left by the verify of #502 (follow-up from #502) #525.
• Not in this PR: the bridge can turn on with an empty topic, and the rule lists idd-issue as implementing it ([bug] spectra bridge: it can turn on with an empty topic, and the rule lists idd-issue as implementing it (found during #502) #524); four LOW and INFO rows of the verify report ([enhancement] spectra bridge detection: LOW and INFO findings left by the verify of #502 (follow-up from #502) #525).

Verification

Verify gate clean — see the verify report on issue #502. /idd-all merges this PR next if CI and the close-stage guardrails pass.

Checklist

• Diagnose ✓
• Implement (2 commits)
• Verify — clean
• No auto-close trailer: /idd-close runs after the merge (idd-all's close stage, or by hand)

Related

#524, #525

---

🤖 Generated by /idd-all. Do NOT add a GitHub close trailer (Closes/Fixes/Resolves) — IDD discipline requires /idd-close (run by /idd-all's close stage, or by hand) to enforce the checklist gate + closing summary.