[META] consider /goal substitution for some /ralph-loop refs in IDD plugin docs

[kiki830621]

Problem

User feedback(2026-05-22 LINE/Claude Code session,inline 「順便改」note):

「有些 /ralph-loop 可以改成用 /goal」

IDD plugin 目前有 7 處 ralph-loop reference。Maintainer 需評估哪些可改用 /goal slash command(user 既有的 goal-tracking skill)。

7 處 ref 分類

概念級(3 處,描述「驅動機制」)— 可能可換 /goal

File	Line	Context
plugins/issue-driven-dev/MANIFESTO.md	135	自動化 caller /loop / ralph-loop / 外部 CI — ralph-loop 作為例子列出
plugins/issue-driven-dev/README.md	215, 223, 224, 228	install 指引 + Required for specific modes matrix
plugins/issue-driven-dev/references/usecase-routing.md	51	ralph-loop 自動驗-修迴圈 機制概念描述

Literal binary detect(4 處)— 不換,改了會破 detect 邏輯

File	Line	Context
plugins/issue-driven-dev/scripts/check-ralph-loop.sh	full	wrapper for backward-compat,argv literal ralph-loop
plugins/issue-driven-dev/scripts/check-plugin-presence.sh	8, 13, 48	usage example + comment reference
plugins/issue-driven-dev/skills/idd-verify/SKILL.md	80, 965-977	Step 0a fail-fast gate check-ralph-loop.sh
plugins/issue-driven-dev/skills/idd-all/SKILL.md	376-403	Step 0.6 graceful degrade gate check-ralph-loop.sh

Open questions for maintainer

• /goal 的 contract 是什麼?跟 ralph-loop 重疊到什麼程度?
• 是否 /goal 也能扮演 (PR, unattended) verify-fix loop driver?(若是 → idd-all Phase 0.6 應提 /goal 為 alternative)
• 或 /goal 是 higher-level 而 ralph-loop 是 inner driver?(關係互補,不是 substitution)
• 應該:(a) 概念級 3 處加 /goal 為 also-available alternative;(b) 全部 7 處 deprecate ralph-loop binary detect 改 /goal;(c) 不改,維持 ralph-loop 為唯一 canonical driver?

Type

enhancement / docs(plugin reference cleanup)

Priority

P3 — 影響文件 clarity 不影響 runtime behavior;等 #135 v3 implementation land 後一併評估 unattended-mode 驅動機制全景

Out of scope

本 issue 不 fold 進 #135 spectra change(terminology trust gap)— 兩條 axis 正交,避免 scope creep。

Refs #135 sister concern session