diff --git a/.claude/.idd/attachments/issue-512/_manifest.json b/.claude/.idd/attachments/issue-512/_manifest.json new file mode 100644 index 00000000..dcf213aa --- /dev/null +++ b/.claude/.idd/attachments/issue-512/_manifest.json @@ -0,0 +1,6 @@ +{ + "issue": 512, + "fetched_at": "2026-11-12T06:00:58Z", + "fetched_by": "idd-diagnose", + "files": [] +} diff --git a/openspec/changes/archive/2026-11-12-idd-512-doc-sync-after-close/.openspec.yaml b/openspec/changes/archive/2026-11-12-idd-512-doc-sync-after-close/.openspec.yaml new file mode 100644 index 00000000..4f27ebf0 --- /dev/null +++ b/openspec/changes/archive/2026-11-12-idd-512-doc-sync-after-close/.openspec.yaml @@ -0,0 +1,6 @@ +schema: spec-driven +created: 2026-11-12 +created_by: che cheng +created_with: claude +archived_by: che cheng +archived_at: 2026-11-12 diff --git a/openspec/changes/archive/2026-11-12-idd-512-doc-sync-after-close/proposal.md b/openspec/changes/archive/2026-11-12-idd-512-doc-sync-after-close/proposal.md new file mode 100644 index 00000000..780ea82c --- /dev/null +++ b/openspec/changes/archive/2026-11-12-idd-512-doc-sync-after-close/proposal.md @@ -0,0 +1,49 @@ +**GitHub-side tracker**: #512 + +## Problem + +`idd-close` 的 Step 6.3(doc-sync 檢查)有一句「位置」,說這一步在結案摘要貼出之後、`gh issue close` 之前做。同一份 SKILL.md 的其他地方都是先關閉:Step 4 在同一個 bash 區塊裡貼摘要、接著關閉 issue;步驟的順序是 Step 4、Step 6、Step 6.3、Step 6.5;Step 0.5 的清單也是 `publish_and_close`、`auto_update_body`、`doc_sync_sweep`、`distribution_sync_chain_detection`。照步驟順序執行的人到 Step 6.3 時 issue 已經關了;照那一句執行的人要自己把 Step 4 的區塊拆開。兩種讀法做出來的順序不同。 + +## Root Cause + +Step 6.3 加進來的時候(#220),「位置」那一句寫的是當時的打算,這一步實際被放在 Step 4 與 Step 6 之後。沒有任何檢查比對這一句、步驟的順序與清單,也沒有規格寫明這一步在什麼時候做,所以矛盾一直留著。 + +## Proposed Solution + +- 維護者已決定(2026-11-11):doc-sync 檢查留在 issue 關閉之後,只改「位置」那一句,不把檢查移到貼出摘要之前。 +- 那一句改成說狀態:issue 已關閉、結案摘要已貼出之後,在 Step 6 body sync 之後、Step 6.5 distribution sync 之前。 +- 新增一條 requirement,寫明這個位置,以及 SKILL.md 講到它的三處要一致。 +- doc-sync-sweep 的測試加一個檢查程式:讀 SKILL.md,比對步驟的順序、清單的順序與「位置」那一句;並用七份改壞的副本確認每一項檢查都抓得到。 + +## Non-Goals + +- 把 doc-sync 檢查移到關閉之前,或讓它能擋下結案:維護者選了相反的做法。 +- 改 Step 4、Step 6、Step 6.5 或 Step 0.5 清單的內容:它們已經一致。 +- 寫明 `--retroactive` 模式跑不跑 Step 6.3:那張表沒有列這一步,是另一個問題,另開 issue。 +- 檢查執行者實際照什麼順序跑:步驟由照 SKILL.md 執行的模型做,這次只檢查它讀的文字。 +- ASSUMPTION: 不升版號,CHANGELOG 加在既有的 Unreleased 區塊。 + +## Success Criteria + +- doc-sync-sweep 新增的檢查在改 SKILL.md 之前失敗(現行的檔案不通過),改之後通過;七份改壞的副本各自被抓到,原因是它改壞的那一項。 +- doc-sync-sweep 原有的七個檢查照舊通過。 +- run-all-tests 的全部 suite 與 spectra-archive-post-ic 通過。 +- 連結檢查對新增的 requirement 回 ok。 + +## Capabilities + +### New Capabilities + +- `idd-close-doc-sync`: 寫明 `/idd-close` 的 doc-sync 檢查在什麼時候做(issue 關閉、結案摘要貼出之後),以及 SKILL.md 講到這個位置的幾處要一致。 + +### Modified Capabilities + +(none) + +## Impact + +- Affected specs: idd-close-doc-sync(新增,ADDED requirement「The doc-sync sweep runs after the issue is closed」) +- Affected code: + - Modified: plugins/issue-driven-dev/skills/idd-close/SKILL.md + - Modified: plugins/issue-driven-dev/scripts/tests/doc-sync-sweep/test.sh + - Modified: plugins/issue-driven-dev/CHANGELOG.md diff --git a/openspec/changes/archive/2026-11-12-idd-512-doc-sync-after-close/specs/idd-close-doc-sync/spec.md b/openspec/changes/archive/2026-11-12-idd-512-doc-sync-after-close/specs/idd-close-doc-sync/spec.md new file mode 100644 index 00000000..fcb19f8b --- /dev/null +++ b/openspec/changes/archive/2026-11-12-idd-512-doc-sync-after-close/specs/idd-close-doc-sync/spec.md @@ -0,0 +1,30 @@ +## Purpose + +Defines when `/idd-close` runs its doc-sync sweep, the check of README and CLAUDE.md files for content the closed issue made stale: after the issue is closed and its closing summary is posted. It exists so that the places in `skills/idd-close/SKILL.md` that state this position cannot drift apart again. + +## ADDED Requirements + +### Requirement: The doc-sync sweep runs after the issue is closed + +`/idd-close` SHALL run the doc-sync sweep (Step 6.3) only when the issue is closed and its closing summary is posted: after the step that posts the summary and closes the issue (Step 4), after the body sync (Step 6), and before the distribution sync (Step 6.5). `skills/idd-close/SKILL.md` states where the sweep sits in three places: the order of its step sections, the order of the stage task list of Step 0.5, and the sentence of Step 6.3 that states the position. The step sections and the task list SHALL both place the sweep after the close and the body sync and before the distribution sync. The sentence SHALL say that the issue is already closed and SHALL NOT say that the sweep comes before the issue is closed. + +No executable check: the steps are carried out by a model that follows SKILL.md, so the order in which a run actually takes them is not checked. The Example checks the text the model follows. + +#### Scenario: A close reaches the doc-sync sweep + +- **GIVEN** `/idd-close` has posted the closing summary and closed the issue +- **WHEN** it reaches Step 6.3 +- **THEN** the issue is already closed and its closing summary is already posted, so nothing the sweep finds holds the close back + +##### Example: where the doc-sync sweep sits in idd-close + +| `skills/idd-close/SKILL.md` | The check | +| --- | --- | +| as shipped | passes | +| the position sentence of Step 6.3 says the sweep comes before `gh issue close` | fails on the sentence | +| the position sentence of Step 6.3 does not say that the issue is closed | fails on the sentence | +| Step 6.3 has no position sentence | fails on the sentence | +| the Step 6.3 section is placed before Step 4 | fails on the step order | +| the Step 6.3 section is placed after Step 6.5 | fails on the step order | +| the task list names `doc_sync_sweep` before `publish_and_close` | fails on the task order | +| the task list names `doc_sync_sweep` after `distribution_sync_chain_detection` | fails on the task order | diff --git a/openspec/changes/archive/2026-11-12-idd-512-doc-sync-after-close/tasks.md b/openspec/changes/archive/2026-11-12-idd-512-doc-sync-after-close/tasks.md new file mode 100644 index 00000000..c54a6406 --- /dev/null +++ b/openspec/changes/archive/2026-11-12-idd-512-doc-sync-after-close/tasks.md @@ -0,0 +1,12 @@ +## 1. 測試先行 + +- [x] 1.1 doc-sync 檢查的位置有可執行的檢查:依 requirement「The doc-sync sweep runs after the issue is closed」的 Example「where the doc-sync sweep sits in idd-close」,doc-sync-sweep 加一個讀 idd-close SKILL.md 的檢查程式與 Example 八列各自的檢查,測試檔帶標記 spec-example: idd-close-doc-sync / where the doc-sync sweep sits in idd-close。現行的檔案要通過;七份改壞的副本(「位置」那一句說在關閉之前、那一句沒說 issue 已經關閉、沒有「位置」那一句、Step 6.3 移到 Step 4 之前、Step 6.3 移到 Step 6.5 之後、清單裡 doc_sync_sweep 排在 publish_and_close 之前、清單裡 doc_sync_sweep 排在 distribution_sync_chain_detection 之後)各自被抓到,而且抓到的原因是那一份改壞的地方。驗證:改 SKILL.md 之前,現行的檔案不通過,說在關閉之前的那份副本做不出來(與現行檔案相同),四份改順序的副本除了順序還帶著那一句的問題。 + +## 2. skill 文字 + +- [x] 2.1 改 idd-close Step 6.3 的「位置」那一句:寫成 issue 已關閉、closing summary 已貼出之後,在 Step 6 body sync 之後、Step 6.5 distribution sync 之前。步驟的順序與 Step 0.5 的清單不動。驗證:1.1 全部通過;doc-sync-sweep 原有的七個檢查照舊通過。 + +## 3. 收尾 + +- [x] 3.1 CHANGELOG 的 Unreleased 加 Fixed 條目(#512)。驗證:git diff 只有新增行,已發布版本的條目沒有改動。 +- [x] 3.2 跑 doc-sync-sweep 與整套測試(run-all-tests.sh 與 spectra-archive-post-ic)。驗證:結束碼都是 0。 diff --git a/openspec/specs/idd-close-doc-sync/spec.md b/openspec/specs/idd-close-doc-sync/spec.md new file mode 100644 index 00000000..63244d4b --- /dev/null +++ b/openspec/specs/idd-close-doc-sync/spec.md @@ -0,0 +1,32 @@ +# idd-close-doc-sync Specification + +## Purpose + +Defines when `/idd-close` runs its doc-sync sweep, the check of README and CLAUDE.md files for content the closed issue made stale: after the issue is closed and its closing summary is posted. It exists so that the places in `skills/idd-close/SKILL.md` that state this position cannot drift apart again. + +## Requirements + +### Requirement: The doc-sync sweep runs after the issue is closed + +`/idd-close` SHALL run the doc-sync sweep (Step 6.3) only when the issue is closed and its closing summary is posted: after the step that posts the summary and closes the issue (Step 4), after the body sync (Step 6), and before the distribution sync (Step 6.5). `skills/idd-close/SKILL.md` states where the sweep sits in three places: the order of its step sections, the order of the stage task list of Step 0.5, and the sentence of Step 6.3 that states the position. The step sections and the task list SHALL both place the sweep after the close and the body sync and before the distribution sync. The sentence SHALL say that the issue is already closed and SHALL NOT say that the sweep comes before the issue is closed. + +No executable check: the steps are carried out by a model that follows SKILL.md, so the order in which a run actually takes them is not checked. The Example checks the text the model follows. + +#### Scenario: A close reaches the doc-sync sweep + +- **GIVEN** `/idd-close` has posted the closing summary and closed the issue +- **WHEN** it reaches Step 6.3 +- **THEN** the issue is already closed and its closing summary is already posted, so nothing the sweep finds holds the close back + +##### Example: where the doc-sync sweep sits in idd-close + +| `skills/idd-close/SKILL.md` | The check | +| --- | --- | +| as shipped | passes | +| the position sentence of Step 6.3 says the sweep comes before `gh issue close` | fails on the sentence | +| the position sentence of Step 6.3 does not say that the issue is closed | fails on the sentence | +| Step 6.3 has no position sentence | fails on the sentence | +| the Step 6.3 section is placed before Step 4 | fails on the step order | +| the Step 6.3 section is placed after Step 6.5 | fails on the step order | +| the task list names `doc_sync_sweep` before `publish_and_close` | fails on the task order | +| the task list names `doc_sync_sweep` after `distribution_sync_chain_detection` | fails on the task order | diff --git a/plugins/issue-driven-dev/CHANGELOG.md b/plugins/issue-driven-dev/CHANGELOG.md index 82706fd4..37fa1b05 100644 --- a/plugins/issue-driven-dev/CHANGELOG.md +++ b/plugins/issue-driven-dev/CHANGELOG.md @@ -20,6 +20,13 @@ Version number left to the release. the job is cancelled. A longer limit buys little: at a load near 150 on the same machine, actionability-gate alone took 193 s, so at that load the full run already fails on another suite. No other suite got a file: apart from merge-completeness, none took more than 60 s in three full runs at ordinary load. +- **`idd-close` says in one way where its doc-sync sweep sits (#512).** The 「位置」 sentence of Step 6.3 said the + sweep runs before `gh issue close`, while the step order, the Step 0.5 task list and Step 4 (which posts the + summary and closes the issue in one block) all run it after the close. The sentence now says what the rest of + the skill does: the issue is closed and the closing summary is posted, then the body sync, then the sweep, then + the distribution sync. The order of the steps is unchanged. A new capability, `idd-close-doc-sync`, states the + position, and the doc-sync-sweep suite reads SKILL.md and compares the three places; it also runs the comparison + on copies broken on purpose, one for each thing it compares, so each part of the check is seen to fail. ## [4.0.1] - 2026-11-11 diff --git a/plugins/issue-driven-dev/scripts/tests/doc-sync-sweep/test.sh b/plugins/issue-driven-dev/scripts/tests/doc-sync-sweep/test.sh index 8dcf6bd4..c2439223 100755 --- a/plugins/issue-driven-dev/scripts/tests/doc-sync-sweep/test.sh +++ b/plugins/issue-driven-dev/scripts/tests/doc-sync-sweep/test.sh @@ -23,4 +23,183 @@ SKILL="$HERE/../../../skills/idd-close/SKILL.md" assert_grep "SKILL.md 含 Step 6.3 doc-sync sweep" "Step 6.3: Doc-sync sweep" "$(cat "$SKILL")" assert_grep "SKILL.md 含 task list 項 doc_sync_sweep" 'name="doc_sync_sweep"' "$(cat "$SKILL")" +# ── Where the sweep sits in idd-close (#512) ── +# spec-example: idd-close-doc-sync / where the doc-sync sweep sits in idd-close +# SKILL.md says where Step 6.3 sits in three places: the order of the step sections, the order of the +# Step 0.5 task list, and the 「位置」 sentence of Step 6.3. pos.py reads a SKILL.md and prints one line +# per disagreement, `: ` with kind = sentence | order | tasks, or `ok`. The step order and +# the task order were already right when the sentence was wrong, so each kind is also run against +# copies broken on purpose: a check that cannot fail shows nothing. The first eight checks are the +# rows of the Example; the four after them break one thing each that no row covers on its own. +cat > "$W/pos.py" <<'PY' +import re +import sys + +OLD_SENTENCE = "**位置**:closing summary 已 publish、`gh issue close` 之前(與 Step 6 body sync 同區、序在 6.5 distribution sync 前)。" +SILENT_SENTENCE = "**位置**:closing summary 已貼出之後、Step 6.5 distribution sync 之前。" +BOTH_SENTENCE = "**位置**:issue 已關閉之後才回報結果,檢查本身在 `gh issue close` 之前做。" +TASKS = ["publish_and_close", "auto_update_body", "doc_sync_sweep", "distribution_sync_chain_detection"] +# "before the close": a word for closing, then at most ten characters of the same clause, then 前. +BEFORE_CLOSE = re.compile( + r"(gh issue close|關閉|結案|\bclosed?\b)[^,。;、:(()後]{0,10}(之前|以前|前)" + r"|before[^,.;:()]{0,40}(gh issue close|\bclosed?\b|\bclosing the issue\b)", re.I) +SAYS_CLOSED = re.compile(r"已關閉|已經關閉|已經關了|關閉之後|關閉後|關閉以後|after[^,.;:()]{0,40}\bclosed\b", re.I) + + +def kinds(lines): + """text / code / fence per line; a fence closes only on a run of backticks at least as long.""" + out, infence, n = [], False, 0 + for line in lines: + s = line.lstrip() + m = re.match(r"`{3,}", s) + if m and not infence: + infence, n = True, len(m.group(0)); out.append("fence"); continue + if m and infence and len(m.group(0)) >= n and s[len(m.group(0)):].strip() == "": + infence = False; out.append("fence"); continue + out.append("code" if infence else "text") + return out + + +def headings(lines, kind, step): + return [i for i, l in enumerate(lines) if kind[i] == "text" and l.startswith("### Step %s:" % step)] + + +def section(lines, kind, start): + """[start, end): from a step heading to the next step heading or h2 outside a fence.""" + for i in range(start + 1, len(lines)): + if kind[i] == "text" and (lines[i].startswith("### Step ") or lines[i].startswith("## ")): + return start, i + return start, len(lines) + + +def check(lines): + kind = kinds(lines) + why = [] + at = {} + for step in ("0.5", "4", "6", "6.3", "6.5"): + found = headings(lines, kind, step) + if len(found) != 1: + why.append(("tasks" if step == "0.5" else "order", 'expected one "### Step %s:" heading, found %d' % (step, len(found)))) + else: + at[step] = found[0] + if all(k in at for k in ("4", "6", "6.3", "6.5")): + a, b = section(lines, kind, at["4"]) + closes = [i for i in range(a, b) if kind[i] == "code" and lines[i].startswith("gh issue close ")] + if not closes: + why.append(("order", "Step 4 has no `gh issue close` command line")) + if not at["4"] < at["6"] < at["6.3"] < at["6.5"]: + why.append(("order", "the sections are not in the order Step 4, Step 6, Step 6.3, Step 6.5")) + if "0.5" in at: + a, b = section(lines, kind, at["0.5"]) + names = [m.group(1) for i in range(a, b) for m in [re.match(r'TaskCreate\(name="([A-Za-z_]+)"', lines[i])] if m] + where = [] + for t in TASKS: + if names.count(t) != 1: + why.append(("tasks", "%s is listed %d times in the Step 0.5 task list" % (t, names.count(t)))) + else: + where.append(names.index(t)) + if len(where) == len(TASKS) and where != sorted(where): + why.append(("tasks", "the task list is not in the order " + ", ".join(TASKS))) + if "6.3" in at: + a, b = section(lines, kind, at["6.3"]) + sent = [lines[i] for i in range(a, b) if kind[i] == "text" and lines[i].startswith("**位置**")] + if len(sent) != 1: + why.append(("sentence", "Step 6.3 has %d position sentences, expected one" % len(sent))) + else: + if BEFORE_CLOSE.search(sent[0]): + why.append(("sentence", "the position sentence says the sweep comes before the issue is closed")) + if not SAYS_CLOSED.search(sent[0]): + why.append(("sentence", "the position sentence does not say the issue is already closed")) + return why + + +def move(lines, a, b, to): + """Move lines[a:b] so that they start where line `to` (an index outside [a, b)) was.""" + block, rest = lines[a:b], lines[:a] + lines[b:] + to = to - (b - a) if to >= b else to + return rest[:to] + block + rest[to:] + + +def mutate(what, lines): + kind = kinds(lines) + one = lambda step: headings(lines, kind, step)[0] + a, b = section(lines, kind, one("6.3")) + put = {"says-before": [OLD_SENTENCE], "silent-on-close": [SILENT_SENTENCE], "closed-but-before": [BOTH_SENTENCE], "no-sentence": []} + if what in put: + hits = [i for i in range(a, b) if kind[i] == "text" and lines[i].startswith("**位置**")] + i = hits[0] + return lines[:i] + put[what] + lines[i + 1:] + if what == "before-step-4": + return move(lines, a, b, one("4")) + if what == "after-step-6.5": + return move(lines, a, b, section(lines, kind, one("6.5"))[1]) + if what == "close-moved-after-sweep": + s4, e4 = section(lines, kind, one("4")) + c = [i for i in range(s4, e4) if kind[i] == "code" and lines[i].startswith("gh issue close ")][0] + return move(lines, c, c + 1, b) + if what == "heading-missing": + return lines[:a] + ["### Doc-sync sweep"] + lines[a + 1:] + task = lambda name: [i for i, l in enumerate(lines) if l.startswith('TaskCreate(name="%s"' % name)][0] + d = task("doc_sync_sweep") + if what == "task-before-publish": + return move(lines, d, d + 1, task("publish_and_close")) + if what == "task-after-distribution": + return move(lines, d, d + 1, task("distribution_sync_chain_detection") + 1) + if what == "task-missing": + return lines[:d] + lines[d + 1:] + raise SystemExit("unknown mutation: " + what) + + +def main(): + lines = open(sys.argv[2], encoding="utf-8").read().split("\n") + if sys.argv[1] == "check": + why = check(lines) + print("\n".join("%s: %s" % w for w in why) if why else "ok") + return 1 if why else 0 + new = mutate(sys.argv[3], lines) + if new == lines: + raise SystemExit("mutation %s left the file as it was" % sys.argv[3]) + open(sys.argv[4], "w", encoding="utf-8").write("\n".join(new)) + return 0 + + +if __name__ == "__main__": + try: + sys.exit(main()) + except (IndexError, OSError) as e: + print("error: %s" % e, file=sys.stderr) + sys.exit(2) +PY + +# position_verdict FILE → ok | the kinds of disagreement found, sorted and joined with + | error +position_verdict() { + local out rc + out=$(python3 "$W/pos.py" check "$1" 2>/dev/null); rc=$? + case "$rc" in + 0) [ "$out" = ok ] && echo ok || echo error ;; + 1) printf '%s\n' "$out" | cut -d: -f1 | sort -u | paste -sd+ - ;; + *) echo error ;; + esac +} +# broken_verdict WHAT → the verdict on a copy of the shipped SKILL.md broken in one way; not-built when +# the copy could not be made or is the same as the shipped file +broken_verdict() { + python3 "$W/pos.py" mutate "$SKILL" "$1" "$W/skill-$1.md" 2>/dev/null || { echo not-built; return; } + position_verdict "$W/skill-$1.md" +} + +assert_eq "現行的 SKILL.md:步驟順序、清單、「位置」那一句一致" "ok" "$(position_verdict "$SKILL")" +assert_eq "「位置」那一句說在 gh issue close 之前 → 抓到的是那一句" "sentence" "$(broken_verdict says-before)" +assert_eq "「位置」那一句沒說 issue 已經關閉 → 抓到的是那一句" "sentence" "$(broken_verdict silent-on-close)" +assert_eq "Step 6.3 沒有「位置」那一句 → 抓到的是那一句" "sentence" "$(broken_verdict no-sentence)" +assert_eq "Step 6.3 移到 Step 4 之前 → 抓到的是步驟順序" "order" "$(broken_verdict before-step-4)" +assert_eq "Step 6.3 移到 Step 6.5 之後 → 抓到的是步驟順序" "order" "$(broken_verdict after-step-6.5)" +assert_eq "清單裡 doc_sync_sweep 排在 publish_and_close 之前 → 抓到的是清單" "tasks" "$(broken_verdict task-before-publish)" +assert_eq "清單裡 doc_sync_sweep 排在 distribution_sync_chain_detection 之後 → 抓到的是清單" "tasks" "$(broken_verdict task-after-distribution)" +# One thing broken that no row above covers on its own. +assert_eq "同一句又說 issue 已關閉、又說在 gh issue close 之前 → 抓到的是那一句" "sentence" "$(broken_verdict closed-but-before)" +assert_eq "gh issue close 那一行搬到 Step 6.3 之後 → 抓到的是步驟順序" "order" "$(broken_verdict close-moved-after-sweep)" +assert_eq "Step 6.3 的標題不見了 → 抓到的是步驟順序" "order" "$(broken_verdict heading-missing)" +assert_eq "清單裡沒有 doc_sync_sweep → 抓到的是清單" "tasks" "$(broken_verdict task-missing)" + print_summary "doc-sync-sweep" diff --git a/plugins/issue-driven-dev/skills/idd-close/SKILL.md b/plugins/issue-driven-dev/skills/idd-close/SKILL.md index f1d8e79e..8e1b6bc1 100644 --- a/plugins/issue-driven-dev/skills/idd-close/SKILL.md +++ b/plugins/issue-driven-dev/skills/idd-close/SKILL.md @@ -952,7 +952,7 @@ Skill(skill="issue-driven-dev:idd-update", args="#NNN") > 使用者原話(#220):「idd-close 的時候更新所有 README 跟 CLAUDE.md 這可能是最後一步吧」— close 是「改動最終狀態確定」的唯一時點,本步把文件 drift 的攔截制度化(motivating incident:che-ical v1.14.0 三處 stale docs 全靠人工 review 才抓到,其中 `README_zh-TW.md` 整份被字面 glob 漏掉)。 -**位置**:closing summary 已 publish、`gh issue close` 之前(與 Step 6 body sync 同區、序在 6.5 distribution sync 前)。 +**位置**:issue 已關閉、closing summary 已貼出之後(Step 4 與 Step 6 body sync 之後),Step 6.5 distribution sync 之前。到這一步時 issue 已經關了,所以它不擋結案;發現過時的文件照 6.3.3 處置。 #### 6.3.1 機械枚舉(防 glob 漏 — incident 教訓)