feat: actionability gate round 2 — prefix tier + deferral vocabulary, wired into all four consumers (#316)

.claude-plugin/marketplace.json

@@ -15,8 +15,8 @@
   "plugins": [
     {
       "name": "issue-driven-dev",
-      "version": "3.0.0",
-      "description": "v3.0.0 (BREAKING): the closing-summary helper may VETO and may never PERMIT. After twelve verify rounds failing in one direction — a real summary the recogniser could not follow classified `missing`, and `missing` being the sole authorisation for `/idd-close --retroactive` to post a duplicate — the power was split along the direction that is sound. \"A marker IS here\" is an observation; \"a marker is NOT here\" is an inference from a failure to recognise, and no matcher over source bytes can answer a question about rendered output in the negative. Gate exit codes are now 1 (recognised) / 2 (undeterminable) / 10 (nothing recognised — NOT permission); there is no exit 0 in gate mode, deliberately, so a caller still reading `rc == 0 means go` breaks loudly. Gate class `missing` → `unrecognised`, every reply carries authorises:false, and a fifth class `mentioned` names the state the tool can actually observe. `--retroactive` loses its unattended path: the skill must read the comment set itself and obtain human confirmation that cannot be disabled. Classification now asks who wrote the comment, so a commenter can no longer move an issue between classes. Also: three more exit-0 parser paths, markup counted as content three layers deep, a quotation reaching `compliant`, the mention gate passing on zero iterations by three routes, untrusted prose reaching a shell command line, and #317 criterion (c) answered correctly for the first time in five attempts. Ten guards were mutation-proven vacuous and rebuilt.",
+      "version": "3.1.0",
+      "description": "v3.1.0: the actionability gate, rounds 2 to 7. Round 1 read `### Complexity` against a closed value domain that the repository's own 159 diagnoses refuted (66 real values wrongly refused) and shipped a three-signal gate no consumer called. Now the tier is the leading whole word (rationale, decoration and ` via` suffixes are legal), the whole line is scanned for a small deferral vocabulary (exit 5, reason `complexity-deferral-marker` — a parked state, not a defect), and `### Blocking` is read per bullet by a shared helper with a leading-token placeholder rule frozen against the repo's 55 real rows — 54 sections under CommonMark (54/55 agree with hand review; round 2 had withheld 30 of the 48 empty ones, #316 itself among them). idd-list / idd-all / idd-implement / idd-plan call the verdict with all three signals before any branch or comment, print it as a machine line plus a delimited raw block, and repeat the gate byte for byte where a later step routes on it (pinned by test). Fences follow CommonMark's two visibility rules; the reader's known divergences from CommonMark are listed with their direction and pinned, not claimed exhaustive. The placeholder rule does not depend on the locale or on a shell function named grep; the matchers that still follow the environment are listed with their measured directions (#336). Changes to the reader are gated: vocabulary rules move only toward withholding unless a named corpus row requires the change; structural rules (headings, fences, bullets, trimming, and the locale of their matchers) are frozen until a requirement names the oracle they converge on (#336). idd-list gains Parked and Needs-diagnosis groups; the #84 blocked surface is preserved verbatim.",
       "author": {
         "name": "Che Cheng"
       },

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

@@ -0,0 +1,6 @@
+{
+  "issue": 316,
+  "fetched_at": "2026-08-15T10:08:39Z",
+  "fetched_by": "idd-diagnose",
+  "files": []
+}

openspec/changes/add-actionability-gate/.openspec.yaml

@@ -0,0 +1,4 @@
+schema: spec-driven
+created: 2026-08-14
+created_by: che cheng <kiki830621@gmail.com>
+created_with: claude

openspec/changes/add-actionability-gate/proposal.md

@@ -0,0 +1,62 @@
+## Why
+
+> **第 2 輪 re-baseline（2026-08-15）**：`/idd-verify --pr 318` FAIL（2 CRITICAL / 21 HIGH）。CRITICAL-2 以 90 筆真實語料證偽第 1 輪的封閉值域前提；`/idd-reorganize #316` 完成裁定；`/idd-diagnose #316` 第 2 輪以 **159 筆完整 corpus** 重新定出值域規則（159/159，0 false positive）。本 proposal 的 What Changes / Impact 已依該結論重寫；design D1/D3/D5 與 spec R1/R3/R7 同步重寫，其餘決策經裁定為 still-valid 而保留。
+>
+> **Re-scope note（2026-08-14）**：本 change 於 #298 仍 open 時提出。走完 discuss → propose、進入 apply 時發現 **#298 已由 PR #309 / #306 修掉並 close** —— 但修正**只落在 `idd-list`**，另三個 consumer（`idd-all` / `idd-implement` / `idd-plan`）未動，且 `idd-list` 自身 Step 5 仍文載會截斷的 regex，與新增的 Step 3.7 直接矛盾。本 change 遂 re-scope 為**承接剩餘缺口**，追蹤於 **#316**；已完成的共用 helper、canonical 契約與回歸測試（全新檔、與已 merge 內容零衝突）原樣保留。Migration 相關 task 因目標 issue 全數 close 而 moot。
+
+
+2026-08-10 對本 repo 真實的 22-issue backlog 跑 `/idd-list`，routing 把 **8 個 parked/deferred/blocked issue 判成「Actionable now」**（11 個 diagnosed 裡只有 1 個判對）。其中 #131 與 #200 帶有使用者 2026-07-07 親自下的 defer 裁決 —— 照 routing 執行等於自動推翻已記錄的人為決策。失敗是**靜默的**：輸出的表格語法正確、格式正常、沒有任何 warning。
+
+`/idd-diagnose #298` 的 root cause：**`### Complexity` 的值域從未被定義為封閉列舉，也沒有「unparseable → 保守 + surface」契約** —— 而結構相同的姊妹欄位 `### Conflict Class` 兩者都有（見 openspec/specs/parallel-orchestration/spec.md）。producer 寫出 `Simple when triggered` 並未違反任何明文規則，於是三個 consumer 各自發明了互不相容的窄化方式：`idd-list` 靜默截斷成 `Simple`；`idd-all` 與 `idd-implement` 得到非法字串，既不匹配任何 dispatch row 也不是 `UNKNOWN`，落入未定義行為（既有的 `UNKNOWN` 安全網只在 regex 完全沒 match 時觸發，結構上接不住此案例）。
+
+更深一層：**把會變的狀態存進不可變的 artifact**。`### Complexity` 活在 append-only 的 Diagnosis comment 裡，但 parked 是會變的狀態（trigger 一成立就該 unpark）。#136 的 comment 寫 bare `Spectra`、body 寫 `Spectra when triggered (parking lot)`，正是狀態被凍住後自己漂移出去的自然實驗。IDD 其實已經知道正確做法 —— `### Blocking` 正因為會變才放在 body 由 `idd-update` 維護。
+
+## What Changes
+
+- **`### Complexity` 的 tier 以 prefix 抽取，容許同行理由** —— 剝裝飾 → 值須**以** `Simple` / `Plan` / `Spectra` / `SDD-warranted` 之一**開頭**（最長匹配優先、整詞匹配），該開頭即為 tier。tier 之後的理由、括號說明、provenance 後綴**皆為合法**，不影響抽取。
+- **延期以語彙偵測，並有獨立 reason** —— 對**整個值**掃 `when triggered` / `parking lot` / `deferred` / `暫緩`，命中則不路由，reason 為 `complexity-deferral-marker`（與 `complexity-unparseable` 分離 —— 前者是正常狀態、後者是資料錯誤，人的處置不同）。
+- **`parking-lot` label 是 parked 的主要訊號**，延期語彙是次要安全網。語彙清單取高精度、容忍低召回。
+- **新增 actionability gate** —— 三訊號 OR 判定（Complexity 不可路由、`parking-lot` label、`### Blocking` 非空），放行需三者皆不成立，**且四個 consumer 必須實際呼叫它**。
+- **三個 consumer 的 Complexity 解析統一** —— `idd-list`、`idd-all`、`idd-implement`（含 `idd-plan` 的 tier 確認）改用共用 helper，消除各自窄化。
+- **`### Blocking` 抽取重構為 gate 的 input** —— 共用 helper 逐 bullet 讀、placeholder 看開頭 token，對 55 筆凍結語料與人工標註 54/55 一致（#1 為明文接受的 FP；第 2 輪的整行比對誤判 31 筆、含 #316 自己；語料 54/55 為 CLOSED，見 design 第 4 輪）。#84 既有的 Blocked 分組輸出行為不得退化；未診斷的 issue 另成 `undiagnosed` 組並保留 `/idd-diagnose` 命令。
+- **`idd-diagnose` producer 端明訂延期意圖走 label** —— 不再宣告封閉值域；改為「tier 寫清楚、延期貼 label、不要把延期寫進本欄」。
+- **零 migration** —— 新規則對既有 159 筆語料 159/159 全對（149 路由、9 擋下、1 缺區段），不需回填 label、不需改寫任何 Diagnosis comment。**零 migration 指「既有 diagnosis 不需改寫」，不是「backlog 可動性分佈不變」** —— 225 筆裡 66 筆從未 diagnose，全部 exit 4，顯示層以 `undiagnosed` 組承接（第 3 輪）。
+- **`references/ic-r011-checkpoint.md` 的 parking 慣例收斂** —— `blocker:infeasible` / `blocker:waiting` 目前 0 個 issue 在用，實際在用的是 `parking-lot`。
+
+## Capabilities
+
+### New Capabilities
+
+- `actionability-gate`: 定義 `### Complexity` 的 tier 抽取規則（以 tier 開頭、其後理由合法）與延期語彙偵測、parked 狀態的歸屬（label 而非 comment）、三訊號 actionability gate 的判定規則，以及不可路由時的保守處置與強制 surface。
+
+### Modified Capabilities
+
+- `idd-ic-r011-checkpoint`：skip path 的 (b)/(c) 分類改以 `parking-lot` label 立案（原 `blocker:infeasible` / `blocker:waiting` 從未建立過；`parking-lot` 自 3.1.0 起是 gate 的一級訊號）。delta 見 `specs/idd-ic-r011-checkpoint/spec.md`。
+
+其餘既有 spec 為何不需修改：硬閘與 Layer V 這兩份既有 spec 所產出的帶後綴 verdict（形如 tier 後接 " via " 再接來源）在新抽取規則下**仍為合法值**（tier 開頭、` via ` 後綴不參與 tier 判定），其 requirement 不需修改；conflict-class 規範對 Complexity 欄位的正交性敘述同樣維持成立。
+
+## Impact
+
+- Affected specs: 新增 `actionability-gate`；修改 `idd-ic-r011-checkpoint`（(b)/(c) 立案 label → `parking-lot`）
+- Affected code:
+  - New:
+    - `plugins/issue-driven-dev/references/actionability-gate.md`
+    - `plugins/issue-driven-dev/scripts/lib/actionability.sh`
+    - `plugins/issue-driven-dev/scripts/tests/actionability-gate/test.sh`
+    - `plugins/issue-driven-dev/scripts/tests/actionability-gate/fixtures/parked-routing.json`
+    - `plugins/issue-driven-dev/scripts/tests/actionability-gate/fixtures/corpus-complexity.json`（159 筆凍結 Complexity 語料）
+    - `plugins/issue-driven-dev/scripts/tests/actionability-gate/fixtures/corpus-blocking.json`（55 筆凍結 Blocking 語料，第 3 輪）
+  - Modified:
+    - `plugins/issue-driven-dev/skills/idd-list/SKILL.md`
+    - `plugins/issue-driven-dev/skills/idd-all/SKILL.md`
+    - `plugins/issue-driven-dev/skills/idd-implement/SKILL.md`
+    - `plugins/issue-driven-dev/skills/idd-plan/SKILL.md`
+    - `plugins/issue-driven-dev/skills/idd-diagnose/SKILL.md`
+    - `plugins/issue-driven-dev/references/ic-r011-checkpoint.md`
+    - `plugins/issue-driven-dev/skills/idd-issue/SKILL.md`（`blocker:*` → `parking-lot`，第 3 輪）
+    - `plugins/issue-driven-dev/rules/sdd-integration.md`（移除平行的 Complexity 解析敘述，第 3 輪）
+    - `plugins/issue-driven-dev/CHANGELOG.md`、`.claude-plugin/plugin.json`、`.claude-plugin/marketplace.json`（3.1.0）
+  - Removed: (none)
+- 同檔衝突：#299（`--limit` 先於排序生效）同樣修改 `plugins/issue-driven-dev/skills/idd-list/SKILL.md`，兩者需序列化或合併處理。
+- 追蹤 issue 由 #298 改為 **#316**（#298 已由 PR #309 / #306 修掉並 close，只涵蓋 `idd-list`）。
+- 配套 issue：#310（parked issue 無回訪機制）—— 本變更把 parked 藏得更乾淨，會放大該問題，但不在本次範圍內。