universal-dev-standards 6.7.5 → 6.8.0

package/bundled/locales/zh-TW/CHANGELOG.md

@@ -1,8 +1,8 @@
 ---
 source: ../../CHANGELOG.md
-source_version: 6.7.5
-translation_version: 6.7.5
-last_synced: 2026-08-18
+source_version: 6.8.0
+translation_version: 6.8.0
+last_synced: 2026-08-19
 status: current
 ---
 
@@ -17,6 +17,24 @@ status: current
 
 ## [Unreleased]
 
+## [6.8.0] - 2026-08-20
+
+### 新增
+
+- **一道去問「這條 `uds <cmd>` 指示真的跑得動嗎」的閘門（XSPEC-383 R4）。** 2026-08-19 查到三個頂層指令（`uds install`、`uds lint`、`uds sync`）與兩個旗標（`uds check --spec-size`、`uds spec create --boost`）出現在出貨的指引裡而**它們都不存在**——落點包括 `quickstart.js`（它的整個工作就是「快速找到對的指令」）與 `integration-generator.js`（它把指令**寫進每一個採用者的 `CLAUDE.md`／`AGENTS.md`**）。兩處早已修掉（`465335e4`），而**沒有任何東西在確認那個修正會維持**。`check-command-existence.mjs` 走訪 `core/`、`locales/`、`ai/standards/`、`cli/src/`、`skills/`、`docs/` 與 repo 根目錄的 `*.md`，抽出每一個 `uds <cmd>` 樣式，用 `uds <path> --definitely-not-a-real-flag` 對本次 commit 自己的 CLI 探測——**不是 `--help`**：commander 對**未知**指令會回答通用指令表而不是報錯，而那正是 `uds lint`／`uds sync` 在第一輪檢查中存活的原因。
+- **同一支探針對現況再跑一次，翻出第一次事故的修正從未碰到的漂移。** `uds workflow`（v6.0.0 移除）在 `docs/user/CHEATSHEET.md`、`docs/reference/FEATURE-REFERENCE.md`、`skills/workflows/README.md`（及 zh-TW／zh-CN 鏡像）**被當成現行指令展示了五個月**，而 `docs/MIGRATION-v6.md` 自己就給了能抓到它的那條 grep。`uds config --lang`／`--mode` 從未存在（root `README.md`、兩份 locale、`docs/reference/INTEGRATION-VERIFICATION.md`）。`uds agent install --all` 把位置參數寫成旗標。`uds reverse-tdd` 是為了一段 GitHub Actions 範例**虛構出來的 CLI**。`uds check --interactive` 不存在，因為互動模式本來就是預設。**29 個發現，29 個修好，0 個殘留。**
+- **一道去問「有沒有人到得了這段程式碼」的閘門（XSPEC-383 R3）。** 單元測試證明函式是對的，對「有沒有使用者叫得到」一個字都沒說。2026-04-07 有一次 commit 加了 `spec-linter.js`（172 行、14 個測試全過）與 `sync.js`（133 行）——**兩者都從未被註冊**，而同一天有下游產品把自己接上 `npx uds lint --json`，一個因此永遠不會存在的指令。四個半月，兩邊全綠，中間沒有一條通的路。`check-module-reachability.mjs` 從 package.json 的 `bin` 與 `main` 出發做 BFS，**手查找到 2 個，走訪找到 24 個**，含整個九模組的 `src/flow/` 子系統。
+- **`uds lint`（XSPEC-383 R5）。** 註冊那個 linter 自 2026-04-07 起就在等的指令，帶著兩項禁得起真實 spec 考驗的檢查：相依有效性與篇幅。
+
+### 變更
+
+- **雜湊前先正規化行尾（#155）。** `uds check` 比對的是磁碟上的原始 bytes，於是 Windows 在 `core.autocrlf=true` 下的 checkout 把每個 LF 換成 CRLF，**每一個雜湊都不再吻合**——而「N 個檔案已修改」這句話，無論是有人改了 N 個檔還是平台改寫了每一個換行，讀起來完全一樣。走訪另外找到兩套從不經過 `hasher.js` 的雜湊實作，四處全修。新增 21 個測試，含負向對照：真實內容差異與尾隨空白差異，在 CRLF checkout 上仍須偵測得到。`uds check --force` 的輸出前後逐位元組相同，既有 manifest 不需要重新蓋章。
+- **使用說明產生器改為問 CLI，而不是背誦一份清單。** `scanCliCommands` 把 `cli/bin/uds.js` 讀進一個變數然後忽略它，改用一份註記著「based on uds.js analysis」的手寫陣列。於是**每一次重新產生都把已移除的 `uds workflow` 寫回文件**，也從來不會加入 `uds lint`。現在它解析 `uds --help`——CLI 對自己有哪些指令的權威回答，涵蓋任何單檔解析看不到的註冊寫法（`mcp` 完全由另一個模組註冊）。涵蓋率從 19/24 變成 **23/23**。
+
+### 移除
+
+- **`uds sync` 與 AC 覆蓋檢查（XSPEC-383 R5，選項 E）。** `sync.js` 零消費者。AC 覆蓋檢查對 93 份真實 spec 量測，回報 98 條驗收條件中 0 條被覆蓋——**不是因為它們沒有測試**，而是因為它用**位置**生成 AC 識別字（`AC-1`、`AC-2`）而不是讀規格宣告的那些，再用寫死的 `@` 前綴去找。一個寫 `AC-045-001` 並且標註不帶 `@` 的專案，無論追溯做得多完整都會得到零覆蓋。**它報的不是「這個專案沒有追溯」，而是「我用我自己的慣例去找，找不到」，而這兩句話印出來一模一樣。** 它是移除而不是留著不接：它是一個正確實作了一個唯一已知消費者並不使用的慣例的東西，躺在樹上等著被人重新接上。跨 repo 的 AC 識別字慣例調解是協商，不是補丁，另案處理。
+
 ## [6.7.5] - 2026-08-18
 
 ### 變更

package/bundled/locales/zh-TW/README.md

@@ -2,8 +2,8 @@
 source: ../../README.md
 source_version: 6.0.0
 translation_version: 6.0.0
-last_synced: 2026-07-08
-source_hash: add024721b5a
+last_synced: 2026-08-19
+source_hash: d978c5775a25
 status: current
 ---
 
@@ -15,7 +15,7 @@ status: current
 
 > **語言**: [English](../../README.md) | 繁體中文 | [简体中文](../zh-CN/README.md)
 
-**版本**: 6.7.5 | **發布日期**: 2026-08-18 | **授權**: [雙重授權](../../LICENSE) (CC BY 4.0 + MIT)
+**版本**: 6.8.0 | **發布日期**: 2026-08-20 | **授權**: [雙重授權](../../LICENSE) (CC BY 4.0 + MIT)
 
 語言無關、框架無關的軟體專案文件標準。透過 AI 原生工作流，確保不同技術堆疊之間的一致性、品質和可維護性。
 
@@ -79,7 +79,7 @@ npx universal-dev-standards init
 | **核心標準** | 150 | 通用開發準則 |
 | **AI Skills** | 55 | 互動式技能 |
 | **斜線命令** | 51 | 快速操作 |
-| **CLI 指令** | 22 | 專案設定與維護 |
+| **CLI 指令** | 23 | 專案設定與維護 |
 <!-- UDS_STATS_TABLE_END -->
 
 > **5.0 新功能？** 請參閱[預發布說明](../../docs/PRE-RELEASE.md)了解新功能詳情。
@@ -198,9 +198,9 @@ uds uninstall   # 從專案移除標準
 
 | 參數 | 指令 | 說明 |
 | :--- | :--- | :--- |
-| **提交語言** | `uds config --lang zh-TW` | 設定 AI 提交訊息的偏好語言 |
+| **提交語言** | `uds config set output_language traditional-chinese` | 設定 AI 提交訊息的偏好語言 |
 | **標準** | `uds init` | 安裝所有可用標準 |
-| **工具模式** | `uds config --mode skills` | 在 Skills、Standards 或兩者之間切換 |
+| **工具模式** | `uds config --type content_mode` | 在 Skills、Standards 或兩者之間切換 |
 
 ---
 

package/bundled/locales/zh-TW/SECURITY.md

@@ -13,7 +13,7 @@ status: current
 <!-- UDS_SUPPORTED_VERSIONS_START -->
 | 版本 | 支援狀態 |
 |------|--------|
-| 6.7.5 | ✅ 最新正式版 |
+| 6.8.0 | ✅ 最新正式版 |
 | < 6.0.0 | ❌ 已終止支援 |
 <!-- UDS_SUPPORTED_VERSIONS_END -->
 

package/bundled/locales/zh-TW/core/ai-instruction-standards.md

@@ -1,8 +1,8 @@
 ---
 source: ../../../core/ai-instruction-standards.md
-source_version: 1.1.0
-translation_version: 1.1.0
-last_synced: 2026-05-28
+source_version: 1.1.1
+translation_version: 1.1.1
+last_synced: 2026-08-19
 status: current
 ---
 
@@ -215,7 +215,7 @@ translation_version: {本翻譯的版本}
 |------|------|--------|
 | **Canonical 擁有者** | `core/{name}.md`、`core/{name}.ai.yaml`、`skills/{name}/SKILL.md` | 維持 L1/L2/L3/L4 為英文；每次 breaking change 時 bump `source_version` |
 | **Locale 維護者** | `locales/{lang}/...` 檔 | `translation_version` 對齊 `source_version`；翻譯 L1（必）、L2（選）、L3（必）、L4（建議）|
-| **採用者（下游專案）** | 自己的 `.claude/skills/`、`CLAUDE.md` 等 | 用 `uds install --locale {lang}` 安裝；**絕不**手動修改 canonical 檔（要客製化請用 locale 變體或 overlay）|
+| **採用者（下游專案）** | 自己的 `.claude/skills/`、`CLAUDE.md` 等 | 用 `uds init --locale {lang}`（首次）或 `uds update --locale {lang}`（重新同步）安裝；**絕不**手動修改 canonical 檔（要客製化請用 locale 變體或 overlay）|
 
 ### Chimera 防範
 
@@ -237,7 +237,8 @@ Pre-commit / CI lint 強制 error 級規則；warn 級規則只在 dashboard 揭
 採用者透過 UDS CLI 安裝指令檔：
 
 ```bash
-uds install --locale zh-TW   # 以繁體中文安裝 skills 與 standards
+uds init --locale zh-tw     # 首次以繁體中文安裝 skills 與 standards
+uds update --locale zh-tw   # 對既有採用重新同步
 ```
 
 **Locale 解析優先順序**：
@@ -258,7 +259,7 @@ uds install --locale zh-TW   # 以繁體中文安裝 skills 與 standards
 若採用者已手動修改過專案中的 canonical 檔（例：在 `.claude/skills/` 翻譯了描述）：
 
 1. **辨識 chimera**：比對採用者檔案與 UDS canonical / canonical 的 locale 變體。
-2. **安裝正確變體**：執行 `uds install --locale {lang}` 替換 chimera 為 locale 變體。
+2. **安裝正確變體**：執行 `uds update --locale {lang}` 替換 chimera 為 locale 變體。
 3. **保留專案級客製**：若 chimera 含合理的專案級客製（非翻譯），抽出為 overlay 或記錄到客製化日誌（例：`UDS-CUSTOMIZATION.md`）。
 4. **丟棄純翻譯**：chimera 中純翻譯部分直接丟棄——locale 變體會取代它。
 
@@ -270,8 +271,9 @@ uds install --locale zh-TW   # 以繁體中文安裝 skills 與 standards
 | 更新 canonical | 改進英文 source | Bump `source_version`；通知 locale 維護者 |
 | 翻譯 / 同步 locale | 新增或更新 locale 內容 | Bump `translation_version`；參照當前 `source_version` |
 | 檢查覆蓋率 | 定期 review | 看自動產生的 `locales/COVERAGE.md` |
-| 帶 locale 安裝 | 採用者初設或重新同步 | `uds install --locale {lang}` |
-| 跑 i18n lint | Commit 前 / CI | `uds lint --i18n` |
+| 帶 locale 安裝 | 採用者初設 | `uds init --locale {lang}` |
+| 帶 locale 重新同步 | 既有採用 | `uds update --locale {lang}` |
+| 跑 i18n lint | Commit 前 / CI | `uds check --i18n` |
 
 ---
 

package/bundled/locales/zh-TW/docs/CHEATSHEET.md

@@ -1,6 +1,6 @@
 # UDS 速查表
 
-> Quick reference for all UDS features | Last updated: 2026-08-17
+> Quick reference for all UDS features | Last updated: 2026-08-19
 
 **Language**: [English](../../../docs/user/CHEATSHEET.md) | 繁體中文 | [简体中文](../../zh-CN/docs/CHEATSHEET.md)
 
@@ -12,13 +12,27 @@
 |---------|-------------|
 | `uds list` | List available standards |
 | `uds init` | Initialize standards in current project |
-| `uds configure` | Modify options for initialized project |
-| `uds check` | Check adoption status of current project |
+| `uds config` | Manage UDS configuration and project settings |
+| `uds hitl` | Human-in-the-Loop controls |
+| `uds configure` | Alias for "uds config" — Modify project settings |
+| `uds check` | Check file integrity and adoption status (quick validation). For deep health diagnosis, use "uds audit" |
+| `uds lint` | Check spec dependency validity and size against installed specs (specs/*.md) |
+| `uds simulate` | Simulate a standard check with input (Predictive Validation) |
+| `uds fix` | Auto-fix standard violations (Self-Healing) |
 | `uds update` | Update standards to latest version |
 | `uds skills` | List installed Claude Code skills |
-| `uds agent` | Manage UDS agents (list, install, info) |
-| `uds workflow` | Manage UDS workflows (list, install, info, execute, status) |
-| `uds ai-context` | Manage AI context configuration (init, validate, graph) |
+| `uds audit` | Deep health diagnosis with pattern detection and feedback (strategic). For quick file check, use "uds check" |
+| `uds deps` | Compare the versions you test against the versions your declared ranges resolve to |
+| `uds uninstall` | Remove UDS standards, integrations, skills, and hooks |
+| `uds compile` | Compile enforcement standards into hook configurations |
+| `uds report` | Analyze hook telemetry and show adoption report |
+| `uds release` | Manage release process (promote, deploy, manifest, verify) |
+| `uds spec` | Manage lightweight micro-specs for vibe coding. For full spec lifecycle with review, use "/sdd" |
+| `uds quickstart` | Interactive workflow guide — find the right commands quickly |
+| `uds agent` | Manage UDS agents for AI tools |
+| `uds ai-context` | Manage .ai-context.yaml configuration for AI-friendly architecture |
+| `uds mcp` | MCP server commands for AI tool integration |
+| `uds run` | Run a project command by intent (test/lint/build/security) via uds.project.yaml |
 
 ## 💬 斜線命令
 

package/bundled/locales/zh-TW/docs/FEATURE-REFERENCE.md

@@ -1,7 +1,7 @@
 # UDS 功能參考手冊
 
 > Universal Development Standards - 完整功能文件
-> Auto-generated | Last updated: 2026-08-17
+> Auto-generated | Last updated: 2026-08-19
 
 **Language**: [English](../../../docs/reference/FEATURE-REFERENCE.md) | 繁體中文 | [简体中文](../../zh-CN/docs/FEATURE-REFERENCE.md)
 
@@ -9,7 +9,7 @@
 
 ## 目錄
 
-1. [CLI 指令](#cli-commands) (9)
+1. [CLI 指令](#cli-commands) (23)
 2. [斜線命令](#slash-commands) (51)
 3. [技能](#skills) (55)
 4. [代理](#agents) (5)
@@ -17,7 +17,7 @@
 6. [核心規範](#core-standards) (150)
 7. [腳本](#scripts) (54)
 
-**Total Features: 329**
+**Total Features: 343**
 
 ---
 
@@ -58,9 +58,22 @@
 | `-E, --experimental` | Enable experimental features (methodology) |
 | `--force` | Bypass UDS source-repo self-adoption guard (DEC-044 / XSPEC-071) |
 
+### `uds config`
+
+**說明**: Manage UDS configuration and project settings
+
+### `uds hitl`
+
+**說明**: Human-in-the-Loop controls
+
+**選項**:
+| Option | 說明 |
+|--------|-------------|
+| `--op` | Operation description |
+
 ### `uds configure`
 
-**說明**: Modify options for initialized project
+**說明**: Alias for "uds config" — Modify project settings
 
 **選項**:
 | Option | 說明 |
@@ -73,7 +86,7 @@
 
 ### `uds check`
 
-**說明**: Check adoption status of current project
+**說明**: Check file integrity and adoption status (quick validation). For deep health diagnosis, use "uds audit"
 
 **選項**:
 | Option | 說明 |
@@ -91,6 +104,36 @@
 | `--force` | Bypass UDS source-repo self-adoption guard (DEC-044 / XSPEC-071) |
 | `--i18n` | Run i18n lint rules (XSPEC-239) across canonical + locale variants |
 
+### `uds lint`
+
+**說明**: Check spec dependency validity and size against installed specs (specs/*.md)
+
+**選項**:
+| Option | 說明 |
+|--------|-------------|
+| `--json` | Output result in JSON format |
+
+### `uds simulate`
+
+**說明**: Simulate a standard check with input (Predictive Validation)
+
+**選項**:
+| Option | 說明 |
+|--------|-------------|
+| `-s, --standard` | Standard to simulate against |
+| `-i, --input` | Input string to test |
+| `--json` | Output result in JSON format |
+
+### `uds fix`
+
+**說明**: Auto-fix standard violations (Self-Healing)
+
+**選項**:
+| Option | 說明 |
+|--------|-------------|
+| `-s, --standard` | Standard to fix |
+| `--json` | Output result in JSON format |
+
 ### `uds update`
 
 **說明**: Update standards to latest version
@@ -117,9 +160,100 @@
 
 **說明**: List installed Claude Code skills
 
+### `uds audit`
+
+**說明**: Deep health diagnosis with pattern detection and feedback (strategic). For quick file check, use "uds check"
+
+**選項**:
+| Option | 說明 |
+|--------|-------------|
+| `--health` | Health check only |
+| `--patterns` | Pattern detection only |
+| `--friction` | Friction detection only |
+| `--report` | Interactive feedback submission |
+| `--yes` | Submit all findings without interactive selection (CI / non-TTY) |
+| `--dry-run` | Preview report without submitting |
+| `--gh` | Force gh CLI for submission |
+| `--format` | Output format (json) |
+| `--quiet` | Summary only |
+| `--score` | Run multi-dimensional health score analysis |
+| `--self` | Self mode: analyze UDS repo itself (use with --score) |
+| `--save` | Save score snapshot for trend tracking (use with --score) |
+| `--trend` | Show historical score trend (use with --score) |
+| `--ci` | CI mode: output score only, exit 1 if below threshold (use with --score) |
+| `--threshold` | Score threshold for CI mode (default: 75) |
+
+### `uds deps`
+
+**說明**: Compare the versions you test against the versions your declared ranges resolve to
+
+**選項**:
+| Option | 說明 |
+|--------|-------------|
+| `--path` | Directory containing package.json (default: cwd) |
+| `--json` | Output raw JSON |
+| `--concurrency` | Parallel registry lookups (default: 8) |
+
+### `uds uninstall`
+
+**說明**: Remove UDS standards, integrations, skills, and hooks
+
+**選項**:
+| Option | 說明 |
+|--------|-------------|
+| `--all` | Remove everything including user-level installations |
+| `--standards-only` | Remove only .standards/ directory |
+| `--skills-only` | Remove only skills and commands |
+| `--integrations-only` | Remove only UDS blocks from integration files |
+| `--dry-run` | Preview mode, no files modified |
+| `-y, --yes` | Skip confirmation prompts |
+
+### `uds compile`
+
+**說明**: Compile enforcement standards into hook configurations
+
+**選項**:
+| Option | 說明 |
+|--------|-------------|
+| `--target` | Target platform (claude-code) |
+| `--dry-run` | Preview output without writing files |
+
+### `uds report`
+
+**說明**: Analyze hook telemetry and show adoption report
+
+### `uds release`
+
+**說明**: Manage release process (promote, deploy, manifest, verify)
+
+### `uds spec`
+
+**說明**: Manage lightweight micro-specs for vibe coding. For full spec lifecycle with review, use "/sdd"
+
+**選項**:
+| Option | 說明 |
+|--------|-------------|
+| `-s, --scope` | Scope (frontend, backend, fullstack) |
+| `-o, --output` | Output directory (default: specs/) |
+| `-y, --yes` | Auto-confirm without prompting |
+| `--status` | Filter by status (draft, confirmed, archived) |
+| `-o, --output` | Specs directory (default: specs/) |
+| `-o, --output` | Specs directory (default: specs/) |
+| `-o, --output` | Specs directory (default: specs/) |
+| `-o, --output` | Specs directory (default: specs/) |
+| `-y, --yes` | Skip confirmation |
+| `-o, --output` | Specs directory (default: specs/) |
+| `--archived` | Search only archived specs |
+| `-o, --output` | Specs directory |
+| `-o, --output` | Specs directory |
+
+### `uds quickstart`
+
+**說明**: Interactive workflow guide — find the right commands quickly
+
 ### `uds agent`
 
-**說明**: Manage UDS agents (list, install, info)
+**說明**: Manage UDS agents for AI tools
 
 **選項**:
 | Option | 說明 |
@@ -129,13 +263,17 @@
 | `-g, --global` | Install to user level instead of project level |
 | `-y, --yes` | Skip confirmation prompts |
 
-### `uds workflow`
+### `uds ai-context`
 
-**說明**: Manage UDS workflows (list, install, info, execute, status)
+**說明**: Manage .ai-context.yaml configuration for AI-friendly architecture
 
-### `uds ai-context`
+### `uds mcp`
+
+**說明**: MCP server commands for AI tool integration
+
+### `uds run`
 
-**說明**: Manage AI context configuration (init, validate, graph)
+**說明**: Run a project command by intent (test/lint/build/security) via uds.project.yaml
 
 ---
 
@@ -298,7 +436,7 @@
 | `ai-agreement-standards` | 1.0.0 | This standard formalizes the interaction between Human (Acquirer) and AI (Suppli |
 | `ai-command-behavior` | 1.0.0 | This standard defines a structure for specifying AI Agent runtime behavior in co |
 | `ai-friendly-architecture` | 1.0.0 | This standard defines architecture and documentation practices that maximize the |
-| `ai-instruction-standards` | 1.1.0 | This standard defines best practices for creating and maintaining AI instruction |
+| `ai-instruction-standards` | 1.1.1 | This standard defines best practices for creating and maintaining AI instruction |
 | `ai-response-navigation` | 1.3.0 | This standard defines navigation behavior for AI responses: every substantive AI |
 | `alerting-standards` | 1.0.0 |  |
 | `anti-hallucination` | 1.5.1 | This standard defines strict guidelines for AI assistants to prevent hallucinati |

package/bundled/locales/zh-TW/skills/agents/README.md

@@ -153,7 +153,7 @@ uds agent list
 uds agent install code-architect
 
 # 安裝所有代理
-uds agent install --all
+uds agent install all
 
 # 安裝到使用者目錄（全域）
 uds agent install code-architect --global

package/bundled/locales/zh-TW/skills/reverse-engineer/tdd-analysis.md

@@ -605,9 +605,19 @@ test.each([
 
 ## CI/CD 整合
 
-### GitHub Actions 範例
+### GitHub Actions —— 目前無法腳本化
+
+`uds reverse-tdd` 這個 CLI 指令不存在。覆蓋率缺口分析是以 **`reverse-tdd`
+AI agent**（`uds agent install reverse-tdd`）提供——由你的 AI 工具互動式執行，
+不是會吐出 `coverage.json` 的確定性腳本。本文件先前版本示範了一個呼叫不存在
+CLI 指令的 GitHub Actions 步驟（XSPEC-383 R4，2026-08-19）。
+
+下方僅為**示意**——展示若未來真的做出可腳本化的分析器，CI 整合可能長什麼樣，
+不是現在就能貼進 workflow 使用的東西：
 
 ```yaml
+# 示意用途——目前沒有可腳本化的等價物。
+# 現況：改用 reverse-tdd agent 從你的 AI 工具互動式執行。
 name: BDD Coverage Check
 
 on: [pull_request]
@@ -618,29 +628,9 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - name: Run BDD Coverage Analysis
-        run: |
-          uds reverse-tdd features/ --output coverage.json
-
-      - name: Check Coverage Threshold
+      - name: Run BDD Coverage Analysis (尚未實作)
         run: |
-          COVERAGE=$(jq '.summary.effectiveCoverage' coverage.json)
-          if (( $(echo "$COVERAGE < 0.80" | bc -l) )); then
-            echo "Coverage $COVERAGE below 80% threshold"
-            exit 1
-          fi
-
-      - name: Comment on PR
-        uses: actions/github-script@v6
-        with:
-          script: |
-            const coverage = require('./coverage.json');
-            github.rest.issues.createComment({
-              issue_number: context.issue.number,
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              body: `## BDD 覆蓋率報告\n\n覆蓋率: ${(coverage.summary.effectiveCoverage * 100).toFixed(1)}%`
-            });
+          echo "目前沒有 CLI 等價物——互動式用法請見 reverse-tdd agent"
 ```
 
 ---

package/bundled/locales/zh-TW/skills/workflows/README.md

@@ -164,18 +164,9 @@ steps:
 
 ## 用法
 
-### CLI 安裝
+### 取得 Workflows
 
-```bash
-# List available workflows
-uds workflow list
-
-# Install specific workflow
-uds workflow install integrated-flow
-
-# Install all workflows
-uds workflow install --all
-```
+`uds workflow` 已於 v6.0.0 移除（流程編排職責移至採用層——DEC-049；見 [MIGRATION-v6.md §3](../../../../docs/MIGRATION-v6.md#3-removed-4-deprecated-cli-commands)）。沒有 CLI 安裝步驟：workflow 定義直接存放在本 repo 的 `skills/workflows/*.workflow.yaml`（見上方表格），請直接引用路徑或複製到專案的 `.claude/workflows/`。
 
 ### 執行
 

package/bundled/skills/agents/README.md

@@ -241,7 +241,7 @@ uds agent list
 uds agent install code-architect
 
 # Install all agents
-uds agent install --all
+uds agent install all
 
 # Install to user directory (global)
 uds agent install code-architect --global

package/bundled/skills/reverse-engineer/tdd-analysis.md

@@ -597,9 +597,22 @@ Mark both scenarios as [Inferred] with shared test reference
 
 ## CI/CD Integration
 
-### GitHub Actions Example
+### GitHub Actions — not currently scriptable
+
+There is no `uds reverse-tdd` CLI command. Coverage-gap analysis is delivered
+as the **`reverse-tdd`** AI agent (`uds agent install reverse-tdd`) — an
+interactive, LLM-driven analysis run from your AI tool, not a deterministic
+script that emits a `coverage.json` file. A prior version of this doc showed
+a GitHub Actions step invoking a CLI command that never existed (XSPEC-383
+R4, 2026-08-19).
+
+The sketch below is **illustrative only** — it shows the shape a scriptable
+CI integration would need if one is built, not something you can paste into
+a workflow today:
 
 ```yaml
+# ASPIRATIONAL — no scriptable equivalent exists yet.
+# Today: run the reverse-tdd agent interactively from your AI tool instead.
 name: BDD Coverage Check
 
 on: [pull_request]
@@ -610,29 +623,9 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - name: Run BDD Coverage Analysis
-        run: |
-          uds reverse-tdd features/ --output coverage.json
-
-      - name: Check Coverage Threshold
+      - name: Run BDD Coverage Analysis (not yet implemented)
         run: |
-          COVERAGE=$(jq '.summary.effectiveCoverage' coverage.json)
-          if (( $(echo "$COVERAGE < 0.80" | bc -l) )); then
-            echo "Coverage $COVERAGE below 80% threshold"
-            exit 1
-          fi
-
-      - name: Comment on PR
-        uses: actions/github-script@v6
-        with:
-          script: |
-            const coverage = require('./coverage.json');
-            github.rest.issues.createComment({
-              issue_number: context.issue.number,
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              body: `## BDD Coverage Report\n\nCoverage: ${(coverage.summary.effectiveCoverage * 100).toFixed(1)}%`
-            });
+          echo "No CLI equivalent yet — see reverse-tdd agent for interactive use"
 ```
 
 ---

package/bundled/skills/workflows/README.md

@@ -157,18 +157,9 @@ steps:
 
 ## Usage
 
-### CLI Installation
+### Getting Workflows
 
-```bash
-# List available workflows
-uds workflow list
-
-# Install specific workflow
-uds workflow install integrated-flow
-
-# Install all workflows
-uds workflow install --all
-```
+`uds workflow` was removed in v6.0.0 (process orchestration moved to the adoption layer — DEC-049; see [MIGRATION-v6.md §3](../../docs/MIGRATION-v6.md#3-removed-4-deprecated-cli-commands)). There is no CLI install step: workflow definitions live directly under `skills/workflows/*.workflow.yaml` in this repo (see the table above), so reference them by path or copy them into your project's `.claude/workflows/`.
 
 ### Execution
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "universal-dev-standards",
-  "version": "6.7.5",
+  "version": "6.8.0",
   "description": "CLI tool for adopting Universal Development Standards",
   "keywords": [
     "documentation",
@@ -56,7 +56,9 @@
     "prepare": "node ../scripts/setup-husky.mjs",
     "test:upgrade": "node scripts/test-upgrade-path.mjs",
     "check:bundle-parity": "node scripts/check-bundle-parity.mjs",
-    "prepack": "node scripts/prepack.mjs"
+    "prepack": "node scripts/prepack.mjs",
+    "check:reachability": "node scripts/check-module-reachability.mjs",
+    "check:command-existence": "node scripts/check-command-existence.mjs"
   },
   "dependencies": {
     "@inquirer/prompts": "^8.4.2",