universal-dev-standards 6.13.0-beta.1 → 6.13.0-beta.2

package/bundled/core/turn-completion-integrity.md

@@ -159,10 +159,18 @@ actually wired into that harness's own config. As of v1.4.0:
 
 Codex's R9 exemption is best-effort, not silent failure: Codex's Stop payload
 gives the assistant's final message directly but not the human's, so reading
-the human side requires parsing a transcript file whose exact schema was not
-confirmed against a real installation at the time this table was written. A
-failed parse leaves the human side empty — detection still runs on the
-assistant's message, only the R9 exemption for that one turn may be missed.
+the human side requires parsing a transcript file. Confirmed against a real
+codex-cli 0.156.1 installation (2026-09-26): a user message in
+`~/.codex/sessions/**/*.jsonl` is a `{"type":"response_item","payload":
+{"type":"message","role":"user","content":[{"type":"input_text","text":...}]}}`
+record — the message lives under `payload`, not at the top level of the
+line or under a `message` key, and a `role: "developer"` record on the same
+shape is not a human message. The 6.13.0-beta.1 adapter read neither of the
+two shapes it tried against this real one, so R9 never exempted a turn on
+Codex; fixed for 6.13.0-beta.2. A failed parse (or an unrecognized record
+shape) still leaves the human side empty rather than throwing — detection
+still runs on the assistant's message, only the R9 exemption for that one
+turn may be missed.
 
 Cursor was evaluated and is not supported: whether its stop hook can actually
 block a turn in the way this standard requires was unresolved as of this

package/bundled/hooks/check-turn-completion-codex.mjs

@@ -23,12 +23,14 @@
  *
  * R9 (exempt a human-directed stop) is best-effort here. Codex's Stop payload
  * gives the assistant's last message directly but not the human's; this
- * adapter tries transcript_path for it (rollout.jsonl), tolerantly, because
- * its exact schema was not confirmed against a real Codex install at
- * authoring time. If that read fails or the field is null, the user side is
- * treated as empty — which means R9 cannot exempt that turn, not that the
- * check goes silent (last_assistant_message still drives detection). This is
- * the documented gap in core/turn-completion-integrity.md's Codex section.
+ * adapter reads transcript_path for it (rollout.jsonl), tolerantly. The real
+ * record shape has been confirmed against a codex-cli 0.156.1 install
+ * (2026-09-26; see extractMessage() below) — 6.13.0-beta.1 tried two guessed
+ * shapes that never matched it, so R9 never actually exempted a Codex turn.
+ * If the read still fails, or an unrecognized record type is seen, the user
+ * side is treated as empty — which means R9 cannot exempt that turn, not
+ * that the check goes silent (last_assistant_message still drives
+ * detection). See core/turn-completion-integrity.md's Codex section.
  *
  * Judgement (packs, cooldown, rolling window, self-echo) lives in
  * turn-completion/engine.mjs and is shared with every other adapter; this
@@ -43,12 +45,40 @@
 import { readFileSync } from 'node:fs';
 import { decide, isSelfEcho, runSelfTest, printLanguages } from './turn-completion/engine.mjs';
 
+/**
+ * A user-message record's `{ role, content }` payload, whichever of the
+ * plausible JSONL shapes `ev` turns out to be.
+ *
+ * 🔴 2026-09-26: verified against a real codex-cli 0.156.1
+ * `~/.codex/sessions/**\/*.jsonl` transcript. The actual shape is
+ * `{"type":"response_item","payload":{"type":"message","role":"user",
+ * "content":[{"type":"input_text","text":"…"}]}}` — the message lives under
+ * `ev.payload`, not `ev.message` and not `ev` itself. The two fallback shapes
+ * below were this file's original best-effort guesses (Claude-Code-style
+ * nested `message`, and a flat record); neither matches what Codex actually
+ * writes, so `bestEffortLastUserMessage` always returned '' and R9 (exempting
+ * a human-directed stop) never fired on Codex. They stay as fallbacks in case
+ * a different Codex version or record type uses one of them, but `ev.payload`
+ * is tried first since it is the confirmed real shape.
+ *
+ * Other record types seen in a real rollout (`event_msg`, `token_usage_record`,
+ * `session_meta`, `world_state`, and `response_item` payloads of type
+ * `reasoning`/`custom_tool_call`/…) do not have `role: "user"` on the object
+ * this function returns, so they fall through untouched. A `role: "developer"`
+ * message is deliberately NOT treated as a user message — only
+ * `payload.type === "message" && payload.role === "user"` counts.
+ */
+function extractMessage(ev) {
+  if (ev && ev.payload && ev.payload.type === 'message') return ev.payload;
+  if (ev && ev.message && typeof ev.message === 'object') return ev.message;
+  return ev;
+}
+
 /**
  * Best-effort extraction of the human's last message from a Codex transcript.
- * Tolerant of several plausible JSONL shapes because the exact rollout.jsonl
- * schema was not confirmed against a real install; any failure returns '',
- * which is the same as "cannot tell" (R5) — it does not stop
- * last_assistant_message from still being checked.
+ * Tolerant of several plausible JSONL shapes; any failure returns '', which
+ * is the same as "cannot tell" (R5) — it does not stop last_assistant_message
+ * from still being checked.
  */
 function bestEffortLastUserMessage(transcriptPath) {
   if (typeof transcriptPath !== 'string' || !transcriptPath) return '';
@@ -58,16 +88,13 @@ function bestEffortLastUserMessage(transcriptPath) {
       if (!line.trim()) continue;
       let ev;
       try { ev = JSON.parse(line); } catch { continue; }
-      // Try a few plausible shapes rather than committing to one: a nested
-      // { message: { role, content } } (Claude-Code-style rollout entry), or
-      // a flat { role, content }.
-      const msg = (ev && ev.message) || ev;
+      const msg = extractMessage(ev);
       if (!msg || msg.role !== 'user') continue;
       const c = msg.content;
       const text = typeof c === 'string'
         ? c
         : Array.isArray(c)
-          ? c.filter((p) => p && (p.type === 'text' || typeof p.text === 'string')).map((p) => p.text || '').join('\n')
+          ? c.filter((p) => p && (p.type === 'text' || p.type === 'input_text' || typeof p.text === 'string')).map((p) => p.text || '').join('\n')
           : '';
       if (text && text.trim() && !isSelfEcho(text)) user = text;
     }

package/bundled/hooks/turn-completion/locales/en.mjs

@@ -115,9 +115,18 @@ export function isAsking(text) {
  * here disables the check for the rest of the session, which is worse than a
  * missed block. It must read as an instruction to stop, not a mention of
  * stopping.
+ *
+ * 🔴 2026-09-27: `\bI'?m (heading|going) (home|out)\b` was dead code — it can
+ * never match, because isStopRequest() always calls normalize() first, and
+ * normalize() rewrites "I'm" to "I am" before this pattern ever sees the
+ * text (`\bI'll\b` -> "I will" etc. have the same shape, but no other branch
+ * here depended on the contracted form surviving normalize()). Verified: a
+ * bare "I'm heading out." tested false pre-fix, true once the pattern
+ * accounts for the post-normalize "I am" form. Written to match either form
+ * defensively, in case normalize()'s rewrite list ever changes.
  */
 const STOP_REQUEST =
-  /(\blet's (stop|pause|pick this up later)\b|\b(pause|stop) (here|for now|there)\b|\bhold (on|off)\b|\bthat's (enough|it) for (now|today)\b|\b(done|enough) for (now|today)\b|\bwrap (it |this )?up\b|\bcontinue (this )?later\b|\bpick (this|it) up (tomorrow|later)\b|\btake a break\b|\bI'?m (heading|going) (home|out)\b|\bgood ?night\b)/i;
+  /(\blet's (stop|pause|pick this up later)\b|\b(pause|stop) (here|for now|there)\b|\bhold (on|off)\b|\bthat's (enough|it) for (now|today)\b|\b(done|enough) for (now|today)\b|\bwrap (it |this )?up\b|\bcontinue (this )?later\b|\bpick (this|it) up (tomorrow|later)\b|\btake a break\b|\bI(?:'m| am) (heading|going) (home|out)\b|\bgood ?night\b)/i;
 
 export function isStopRequest(text) {
   return STOP_REQUEST.test(normalize(text));
@@ -184,4 +193,15 @@ export const stopCorpus = [
   [false, 'mentions stopping but is not one', 'Explain why the hook stops the turn.'],
   [false, 'asks for work', 'Stop using the hardcoded list and walk the registry instead.'],
   [false, 'ordinary instruction', 'Fix the detector and push it.'],
+  // 🔴 the "I'm heading (home|out)" branch above was dead code before this
+  // fix — normalize() rewrites "I'm" to "I am" before the pattern is tested,
+  // and the pattern required the contracted form. This case exercises it
+  // directly (no "let's pause"/"hold on" alongside it, unlike the two cases
+  // above that already passed for a different reason).
+  [true, "bare 'heading out', no other stop phrase nearby", "I'm heading out."],
+  [false, 'a leaving verb alone is an instruction to finish something BEFORE leaving, not a stop request', 'Before I head out, please finish the migration.'],
 ];
+// Mutation check (verified by hand, then reverted — see commit/handback
+// notes): reverting STOP_REQUEST's `I(?:'m| am)` back to the dead-code
+// `I'?m`-only form turns the "bare 'heading out'" case above false, which
+// fails `--self-test`.

package/bundled/hooks/turn-completion/locales/zh-TW.mjs

@@ -93,15 +93,28 @@ export function isAsking(text) {
   return ASKING.test(text);
 }
 
+// 🔴 2026-09-25 實測缺口：「我要出門了，等我回來再繼續」與「暫停，我要出門」
+// 都沒有被下面任何一支既有樣式接住——前者當天真的誤擋了一次真實的 Claude
+// Code 回合。R10 說叫停樣式放寬是危險方向（錯誤豁免會讓整個 session 的檢查
+// 失效），所以這裡刻意寫窄：離開類詞必須跟「稍後再續」或裸的「暫停」同時
+// 出現在同一小段裡，單獨出現的離開詞不算——「出門前把這三件做完」只有離開
+// 詞、沒有稍後再續，仍必須判 false（見下方 stopCorpus 的反例）。
+const LEAVING = '(出門|離開一下|先走)';
+const RESUME_LATER = '(等我回來|回來再|明天再|晚點再|待會再|待会再)';
+const LEAVE_THEN_LATER = `${LEAVING}[^。！？\\n]{0,12}${RESUME_LATER}|${RESUME_LATER}[^。！？\\n]{0,12}${LEAVING}`;
+const LEAVE_WITH_PAUSE = `暫停[^。！？\\n]{0,12}${LEAVING}|${LEAVING}[^。！？\\n]{0,12}暫停`;
+
 /**
  * The human asking for the turn to end. Kept narrow on purpose: a false
  * positive disables the check for the rest of the session.
  */
-const STOP_REQUEST =
+const STOP_REQUEST = new RegExp(
   // 🔴 `先停` 曾寫成裸的，而語料當場抓到「先**停用**那份硬編碼清單」——
   // 一句要求做事的指令被讀成叫我停。這個方向的誤判會把守衛整場關掉，
   // 所以 `停` 後面接得出動詞的字一律排除。
-  /(先暫停|暫停一下|先停(?![用止掉住])|停一下|先不要(做|動)|不用繼續|今天(先)?到這|先這樣|收工|下班|我要回家|明天再(說|弄|做)|改天再|先擱著|睡了|晚安)/;
+  '(先暫停|暫停一下|先停(?![用止掉住])|停一下|先不要(做|動)|不用繼續|今天(先)?到這|先這樣|收工|下班|我要回家|明天再(說|弄|做)|改天再|先擱著|睡了|晚安' +
+  `|${LEAVE_THEN_LATER}|${LEAVE_WITH_PAUSE})`
+);
 
 export function isStopRequest(text) {
   return STOP_REQUEST.test(text);
@@ -191,4 +204,14 @@ export const stopCorpus = [
   [false, '提到停止但不是叫停', '解釋一下這支 hook 為什麼會擋下回合。'],
   [false, '要求做事而句中有停', '先停用那份硬編碼清單，改成走訪註冊表。'],
   [false, '一般指令', '把偵測器修好然後推上去。'],
+  // 🔴 2026-09-25 真實使用者原話——當時真的誤擋了一次回合，見上方 STOP_REQUEST 的註解。
+  [true, '離開＋稍後再續（真實原話）', '我要出門了，等我回來再繼續'],
+  [true, '暫停＋離開（真實原話）', '暫停，我要出門'],
+  // 窄性反例：單獨的離開詞、或單獨的「稍後」詞，都不算叫停——那是要求
+  // 「在離開前」把事情做完，不是要收掉這一輪。
+  [false, '離開詞單獨出現：這是要求離開前做完，不是叫停', '出門前把這三件做完'],
+  [false, '稍後詞單獨出現，沒有離開詞：一樣是要求先做完', '等我回來前先把測試跑完'],
 ];
+// 突變驗證（手動跑過、已還原——見 commit/交接紀錄）：把 STOP_REQUEST 的
+// `LEAVE_THEN_LATER`／`LEAVE_WITH_PAUSE` 兩個新分支拿掉，上面兩筆「真實原話」
+// 會變 false，`--self-test` 隨之變紅，證明這兩筆真的在測新加的規則。

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

@@ -1,8 +1,8 @@
 ---
 source: ../../CHANGELOG.md
-source_version: 6.13.0-beta.1
-translation_version: 6.13.0-beta.1
-last_synced: 2026-09-25
+source_version: 6.13.0-beta.2
+translation_version: 6.13.0-beta.2
+last_synced: 2026-09-26
 status: current
 ---
 
@@ -17,6 +17,16 @@ status: current
 
 ## [Unreleased]
 
+## [6.13.0-beta.2] - 2026-09-26
+
+> **测试版** — 以 `npm install -g universal-dev-standards@beta` 安装。要测什么、已知限制、如何退回正式版：见 [docs/PRE-RELEASE.md](../../docs/PRE-RELEASE.md)。
+
+### 修复
+
+- **`uds uninstall` 从未移除 `installHooks()`／`installCodexHooks()`／`installGeminiHooks()` 写入的关卡——不只是 Codex 与 Gemini CLI（6.13.0-beta.1 记载的已知限制），Claude Code 自己的 `.claude/settings.json` 也有一模一样的缺口，而且从未被记录过。** `hooks` 这个 uninstall 分类原本只处理 `.husky/pre-commit` 与 `.git/hooks/pre-commit`；三个安装函数实际写入的配置文件完全没有任何 uninstaller 在管，导致每一个关卡在 `uds uninstall` 之后仍持续运行。新增的 `uninstallClaudeCodeHooks`／`uninstallCodexHooks`／`uninstallGeminiHooks`（`src/uninstallers/hook-uninstaller.js`）现在会精准移除 `.claude/settings.json`、`.codex/hooks.json`、`.gemini/settings.json` 里 UDS 安装的条目——判断依据是命令路径**加上**一份 UDS 目前确实有发布的脚本文件名清单，不是只看路径，这样用户自己放进 UDS 同一个 `scripts/hooks/` 目录下的 hook 就不会被误删。移除后变空的事件数组会一并从配置里移除；配置文件若因此变成完全空的对象（代表整份都是 UDS 写入的）就直接删除文件，否则保留文件并写回其余内容。JSON 格式损坏时报告错误并保持原样，不会覆写。已接入 `uds uninstall` 既有的 `hooks` 分类、`--dry-run` 预览，以及交互菜单里该分类的说明文字。
+- **Codex 适配层的 R9 豁免（「用户叫停就放行」）在真实 Codex 安装上从未真正生效过——`scripts/hooks/check-turn-completion-codex.mjs` 的 `bestEffortLastUserMessage()` 试过的两种记录形状都读不到字段。** 已对真实 codex-cli 0.156.1 的 `~/.codex/sessions/**/*.jsonl` 对话记录坐实：一条用户消息记录长这样——`{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":...}]}}`——消息位于 `payload` 之下，不在该条记录最外层、也不在 `message` 键下，所以该字段一直被读成不存在，R9 从未真正豁免过任何一轮 Codex 对话。现在优先读取 `payload.type === "message"`（其余记录类型若刚好用到原来那两种形状仍保留为后备），同时支持 `input_text` 内容项（与既有的 `text` 形状并存），且不把 `role: "developer"` 的记录当成用户消息。`core/turn-completion-integrity.md`「支持的执行环境」一节与 `docs/PRE-RELEASE.md` 已从「未对照真实安装验证过」更新为已坐实的真实形状。
+- **R9 的 zh-TW 叫停检测漏掉了「要离开、稍后再继续」这一族——已实测：「我要出门了，等我回来再继续」在 2026-09-25 真的误挡了一次 Claude Code 的对话完成关卡。** 这句与「暂停，我要出门」都没有被既有的任何一个 `STOP_REQUEST` 模式接住。新增两个窄模式：离开类词（出门／离开一下／先走）必须跟「稍后再续」类词（等我回来／回来再／明天再／晚点再／待会再）或裸的「暂停」同时出现在同一小段里——单独的离开词（例如「出门前把这三件做完」，这是要求离开前做完，不是叫停）语料仍必须判 false。顺手查了 en 语料包有没有同样的缺口，发现 `\bI'?m (heading|going) (home|out)\b` 是永远打不中的死代码：`isStopRequest()` 一律先调用 `normalize()`，会把 "I'm" 改写成 "I am"，只认缩写形式的模式因此永远匹配不到；已改为 `I(?:'m| am) (heading|going) (home|out)`，坐实裸的 "I'm heading out." 修复前为 false、修复后为 true。
+
 ## [6.13.0-beta.1] - 2026-09-26
 
 > **测试版** — 以 `npm install -g universal-dev-standards@beta` 安装。要测什么、已知限制、如何退回正式版：见 [docs/PRE-RELEASE.md](../../docs/PRE-RELEASE.md)。已知限制：`uds uninstall` 尚不会移除 Codex／Gemini CLI 设置里的关卡。

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

@@ -15,7 +15,7 @@ status: current
 
 > **语言**: [English](../../README.md) | [繁體中文](../zh-TW/README.md) | 简体中文
 
-**版本**: 6.13.0-beta.1 (Pre-release) | **发布日期**: 2026-09-26 | **授权**: [双重授权](../../LICENSE) (CC BY 4.0 + MIT)
+**版本**: 6.13.0-beta.2 (Pre-release) | **发布日期**: 2026-09-26 | **授权**: [双重授权](../../LICENSE) (CC BY 4.0 + MIT)
 
 语言无关、框架无关的软件项目文档标准。通过 AI 原生工作流，确保不同技术栈之间的一致性、质量和可维护性。
 

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

@@ -13,7 +13,7 @@ status: current
 <!-- UDS_SUPPORTED_VERSIONS_START -->
 | 版本 | 支持状态 |
 |------|--------|
-| 6.13.0-beta.1 | ✅ 预发布版本 |
+| 6.13.0-beta.2 | ✅ 预发布版本 |
 | 6.12.0 | ✅ 最新正式版 |
 | < 6.0.0 | ❌ 已终止支持 |
 <!-- UDS_SUPPORTED_VERSIONS_END -->

package/bundled/locales/zh-CN/core/turn-completion-integrity.md

@@ -2,8 +2,8 @@
 source: ../../../core/turn-completion-integrity.md
 source_version: 1.4.0
 translation_version: 1.4.0
-last_synced: 2026-09-25
-source_hash: 8966d46d5f79
+last_synced: 2026-09-26
+source_hash: 401b74843abc
 status: current
 ---
 
@@ -154,9 +154,16 @@ agent 写下「我接着做 X」，然后结束回合，而 X 没有做。
 
 Codex 的 R9 豁免是尽力而为，不是静默失效：Codex 的 Stop payload 直接给出
 agent 的最后一条消息，却不给出用户的；要拿到用户那一侧必须解析一份
-对话记录文件，而它的确切格式在撰写本表时未对照真实安装验证过。解析失败时
-用户那一侧会变空——检测仍照样运行在 agent 消息上，只有那一轮的 R9 豁免
-可能漏掉。
+对话记录文件。已对真实 codex-cli 0.156.1 安装坐实（2026-09-26）：
+`~/.codex/sessions/**/*.jsonl` 里的一条用户消息长这样——
+`{"type":"response_item","payload":{"type":"message","role":"user",
+"content":[{"type":"input_text","text":...}]}}`——消息位于 `payload`
+之下，不在该行最外层、也不在 `message` 键下；同一种形状但
+`role: "developer"` 的记录不算用户消息。6.13.0-beta.1 的适配层尝试过的
+两种形状都不是这个真实形状，所以 R9 在 Codex 上从未真正豁免过任何一轮；
+6.13.0-beta.2 已修复。解析失败（或遇到无法识别的记录形状）时仍只是让
+用户那一侧变空、不会抛出异常——检测仍照样运行在 agent 消息上，只有那一轮
+的 R9 豁免可能漏掉。
 
 Cursor 已评估但不支持：截至撰写本文时，Cursor 的 stop hook 能不能真的
 拦下一个回合仍未确定，若对着一个没人验证过的契约交付一份适配层，

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

@@ -1,8 +1,8 @@
 ---
 source: ../../CHANGELOG.md
-source_version: 6.13.0-beta.1
-translation_version: 6.13.0-beta.1
-last_synced: 2026-09-25
+source_version: 6.13.0-beta.2
+translation_version: 6.13.0-beta.2
+last_synced: 2026-09-26
 status: current
 ---
 
@@ -17,6 +17,16 @@ status: current
 
 ## [Unreleased]
 
+## [6.13.0-beta.2] - 2026-09-26
+
+> **測試版** — 以 `npm install -g universal-dev-standards@beta` 安裝。要測什麼、已知限制、如何退回正式版：見 [docs/PRE-RELEASE.md](../../docs/PRE-RELEASE.md)。
+
+### 修正
+
+- **`uds uninstall` 從未移除 `installHooks()`／`installCodexHooks()`／`installGeminiHooks()` 寫入的關卡——不只是 Codex 與 Gemini CLI（6.13.0-beta.1 記載的已知限制），Claude Code 自己的 `.claude/settings.json` 也有一模一樣的缺口，而且從未被記錄過。** `hooks` 這個 uninstall 分類原本只處理 `.husky/pre-commit` 與 `.git/hooks/pre-commit`；三支安裝函式實際寫入的設定檔完全沒有任何 uninstaller 在管，導致每一個關卡在 `uds uninstall` 之後仍持續執行。新增的 `uninstallClaudeCodeHooks`／`uninstallCodexHooks`／`uninstallGeminiHooks`（`src/uninstallers/hook-uninstaller.js`）現在會精準移除 `.claude/settings.json`、`.codex/hooks.json`、`.gemini/settings.json` 裡 UDS 安裝的項目——辨識依據是指令路徑**加上**一份 UDS 目前確實有出貨的腳本檔名清單，不是只看路徑，這樣使用者自己放進 UDS 同一個 `scripts/hooks/` 目錄底下的 hook 就不會被誤刪。移除後變空的事件陣列會一併從設定裡移除；設定檔若因此變成完全空的物件（代表整份都是 UDS 寫入的）就直接刪除檔案，否則保留檔案並寫回其餘內容。JSON 格式損壞時回報錯誤並保持原樣，不會覆寫。已接入 `uds uninstall` 既有的 `hooks` 分類、`--dry-run` 預覽，以及互動選單裡該分類的說明文字。
+- **Codex 轉接層的 R9 豁免（「使用者叫停就放行」）在真實 Codex 安裝上從未真的生效過——`scripts/hooks/check-turn-completion-codex.mjs` 的 `bestEffortLastUserMessage()` 試過的兩種紀錄形狀都讀不到欄位。** 已對真實 codex-cli 0.156.1 的 `~/.codex/sessions/**/*.jsonl` 逐字稿坐實：一則使用者訊息紀錄長這樣——`{"type":"response_item","payload":{"type":"message","role":"user","content":[{"type":"input_text","text":...}]}}`——訊息住在 `payload` 底下，不在該筆紀錄最外層、也不在 `message` 鍵底下，所以那個欄位一直被讀成不存在，R9 從未真的豁免過任何一輪 Codex 回合。現在優先讀 `payload.type === "message"`（其餘紀錄型別若剛好用到原本那兩種形狀仍保留為後備），一併支援 `input_text` 內容項目（與既有的 `text` 形狀並存），且不把 `role: "developer"` 的紀錄當成使用者訊息。`core/turn-completion-integrity.md`「支援的執行環境」一節與 `docs/PRE-RELEASE.md` 已從「未對照真實安裝驗證過」更新為已坐實的真實形狀。
+- **R9 的 zh-TW 叫停偵測漏掉「要離開、稍後再續」這一族——已實測：「我要出門了，等我回來再繼續」在 2026-09-25 真的誤擋了一次 Claude Code 的回合完成關卡。** 這句與「暫停，我要出門」都沒有被既有的任何一支 `STOP_REQUEST` 樣式接住。新增兩支窄樣式：離開類詞（出門／離開一下／先走）必須跟「稍後再續」類詞（等我回來／回來再／明天再／晚點再／待會再）或裸的「暫停」同時出現在同一小段裡——單獨的離開詞（例如「出門前把這三件做完」，這是要求離開前做完，不是叫停）語料仍必須判 false。順手查了 en 語料包有沒有一樣的缺口，發現 `\bI'?m (heading|going) (home|out)\b` 是永遠打不中的死碼：`isStopRequest()` 一律先呼叫 `normalize()`，會把 "I'm" 改寫成 "I am"，只認縮寫形的樣式因此永遠配不到；已修成 `I(?:'m| am) (heading|going) (home|out)`，坐實裸的 "I'm heading out." 修前為 false、修後為 true。
+
 ## [6.13.0-beta.1] - 2026-09-26
 
 > **測試版** — 以 `npm install -g universal-dev-standards@beta` 安裝。要測什麼、已知限制、如何退回正式版：見 [docs/PRE-RELEASE.md](../../docs/PRE-RELEASE.md)。已知限制：`uds uninstall` 尚不會移除 Codex／Gemini CLI 設定裡的關卡。

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

@@ -15,7 +15,7 @@ status: current
 
 > **語言**: [English](../../README.md) | 繁體中文 | [简体中文](../zh-CN/README.md)
 
-**版本**: 6.13.0-beta.1 (Pre-release) | **發布日期**: 2026-09-26 | **授權**: [雙重授權](../../LICENSE) (CC BY 4.0 + MIT)
+**版本**: 6.13.0-beta.2 (Pre-release) | **發布日期**: 2026-09-26 | **授權**: [雙重授權](../../LICENSE) (CC BY 4.0 + MIT)
 
 語言無關、框架無關的軟體專案文件標準。透過 AI 原生工作流，確保不同技術堆疊之間的一致性、品質和可維護性。
 

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

@@ -13,7 +13,7 @@ status: current
 <!-- UDS_SUPPORTED_VERSIONS_START -->
 | 版本 | 支援狀態 |
 |------|--------|
-| 6.13.0-beta.1 | ✅ 預發布版本 |
+| 6.13.0-beta.2 | ✅ 預發布版本 |
 | 6.12.0 | ✅ 最新正式版 |
 | < 6.0.0 | ❌ 已終止支援 |
 <!-- UDS_SUPPORTED_VERSIONS_END -->

package/bundled/locales/zh-TW/core/turn-completion-integrity.md

@@ -2,8 +2,8 @@
 source: ../../../core/turn-completion-integrity.md
 source_version: 1.4.0
 translation_version: 1.4.0
-last_synced: 2026-09-25
-source_hash: 8966d46d5f79
+last_synced: 2026-09-26
+source_hash: 401b74843abc
 status: current
 ---
 
@@ -154,9 +154,16 @@ agent 寫下「我接著做 X」，然後結束回合，而 X 沒有做。
 
 Codex 的 R9 豁免是盡力而為，不是靜默失效：Codex 的 Stop payload 直接給
 agent 的最後一則訊息，卻不給使用者的；要拿到使用者那一側必須解析一份
-逐字稿檔案，而它的確切格式在撰寫本表時未對照真實安裝驗證過。解析失敗時
-使用者那一側會變空——偵測仍照樣跑在 agent 訊息上，只有那一輪的 R9 豁免
-可能漏掉。
+逐字稿檔案。已對真實 codex-cli 0.156.1 安裝坐實（2026-09-26）：
+`~/.codex/sessions/**/*.jsonl` 裡的一則使用者訊息長這樣——
+`{"type":"response_item","payload":{"type":"message","role":"user",
+"content":[{"type":"input_text","text":...}]}}`——訊息住在 `payload`
+底下，不在該行的最外層、也不在 `message` 鍵底下；同一種形狀但
+`role: "developer"` 的紀錄不算使用者訊息。6.13.0-beta.1 的轉接層試過的
+兩種形狀都不是這個真實形狀，所以 R9 在 Codex 上從未真的豁免過任何一輪；
+6.13.0-beta.2 已修正。解析失敗（或遇到辨識不出的紀錄形狀）時仍只是讓
+使用者那一側變空、不會拋出例外——偵測仍照樣跑在 agent 訊息上，只有那一輪
+的 R9 豁免可能漏掉。
 
 Cursor 已評估但不支援：截至撰寫本文時，Cursor 的 stop hook 能不能真的
 擋下一個回合仍未確定，若對著一個沒人驗證過的契約出一份轉接層，

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "universal-dev-standards",
-  "version": "6.13.0-beta.1",
+  "version": "6.13.0-beta.2",
   "description": "CLI tool for adopting Universal Development Standards",
   "keywords": [
     "documentation",

package/src/commands/uninstall.js

@@ -56,7 +56,7 @@ export async function uninstallCommand(options) {
     const categories = await checkbox({
       message: msg.selectCategories,
       choices: [
-        { name: `${msg.categoryHooks} (.husky/pre-commit)`, value: 'hooks', checked: true },
+        { name: `${msg.categoryHooks} (.husky/pre-commit, .claude/settings.json, .codex/hooks.json, .gemini/settings.json)`, value: 'hooks', checked: true },
         { name: `${msg.categorySkills} (skills, commands)`, value: 'skills', checked: true },
         { name: `${msg.categoryIntegrations} (CLAUDE.md, .cursorrules, ...)`, value: 'integrations', checked: true },
         { name: `${msg.categoryStandards} (.standards/)`, value: 'standards', checked: true }

package/src/installers/hooks-installer.js

@@ -231,8 +231,12 @@ export function installHooks(projectPath) {
  *
  * @see core/turn-completion-integrity.md
  */
-const CODEX_HOOK_SCRIPT = 'check-turn-completion-codex.mjs';
-const GEMINI_HOOK_SCRIPT = 'check-turn-completion-gemini.mjs';
+// Exported so the uninstaller (../uninstallers/hook-uninstaller.js) can
+// recognize exactly these two script names as UDS's own, rather than
+// guessing from the shared `scripts/hooks/` directory path alone — a path
+// an adopter's own hook could just as easily live under.
+export const CODEX_HOOK_SCRIPT = 'check-turn-completion-codex.mjs';
+export const GEMINI_HOOK_SCRIPT = 'check-turn-completion-gemini.mjs';
 
 /** Copy the shared hook scripts into the project, same as installHooks() does. */
 function copyHookScripts(hookDir, hooksDir) {

package/src/uninstallers/hook-uninstaller.js

@@ -1,8 +1,168 @@
 import { existsSync, readFileSync, writeFileSync, unlinkSync } from 'fs';
-import { join } from 'path';
+import { join, basename } from 'path';
+import {
+  collectHookConfigs, standardsSourceDir, hooksSourceDir,
+  CODEX_HOOK_SCRIPT, GEMINI_HOOK_SCRIPT,
+} from '../installers/hooks-installer.js';
 
 /**
- * Remove UDS-related lines from .husky/pre-commit
+ * Every UDS-installed hook entry — in .claude/settings.json, .codex/hooks.json
+ * and .gemini/settings.json alike — runs a command of the shape
+ * `node scripts/hooks/<script>` (see installHooks/installCodexHooks/
+ * installGeminiHooks in ../installers/hooks-installer.js). That path alone is
+ * NOT a safe signature, though: `scripts/hooks/` is a directory UDS itself
+ * scaffolds inside the adopter's project, so an adopter's own hook script can
+ * live at the exact same path and be indistinguishable by path alone
+ * (verified: an earlier version of this file matched on path only, and a
+ * test placing a user hook at `scripts/hooks/my-own-hook.mjs` lost it).
+ * The safe signature is path *and* a script basename UDS is actually known to
+ * ship right now — the same set collectHookConfigs() derives for install,
+ * plus the two fixed Codex/Gemini script names.
+ *
+ * 🔴 Until this file added the three functions below, uninstall only ever
+ * touched .husky/pre-commit and .git/hooks/pre-commit — the settings.json /
+ * hooks.json files installHooks() etc. actually write were never cleaned up,
+ * so `uds uninstall` silently left every enforcement hook running (Claude
+ * Code included, not just Codex/Gemini).
+ */
+const UDS_HOOK_COMMAND_PATTERN = /^node scripts\/hooks\//;
+
+/** The command string a hook entry runs, mirroring hooks-installer.js's own commandOf(). */
+function commandOf(entry) {
+  const h = entry && entry.hooks && entry.hooks[0];
+  if (typeof h === 'string') return h;
+  return h && typeof h.command === 'string' ? h.command : undefined;
+}
+
+/** Script basenames UDS currently ships and would install a hook entry for. */
+function knownUdsHookScripts() {
+  const { scripts } = collectHookConfigs(standardsSourceDir(), hooksSourceDir());
+  return new Set([...scripts.map((s) => basename(s)), CODEX_HOOK_SCRIPT, GEMINI_HOOK_SCRIPT]);
+}
+
+function isUdsHookEntry(entry, knownScripts) {
+  const cmd = commandOf(entry);
+  if (typeof cmd !== 'string' || !UDS_HOOK_COMMAND_PATTERN.test(cmd)) return false;
+  return knownScripts.has(basename(cmd));
+}
+
+/**
+ * Strip UDS-installed entries out of a `{ event: entry[] }` map, dropping any
+ * event key left with zero entries. An adopter's own hooks on the same event
+ * (or even the same array, or the same `scripts/hooks/` directory) are never
+ * touched — only entries whose command names a script UDS is known to ship
+ * are removed.
+ */
+function stripUdsEntries(hooksMap) {
+  const knownScripts = knownUdsHookScripts();
+  let removedCount = 0;
+  const nextMap = {};
+  for (const [event, entries] of Object.entries(hooksMap || {})) {
+    const kept = (entries || []).filter((entry) => {
+      if (isUdsHookEntry(entry, knownScripts)) {
+        removedCount += 1;
+        return false;
+      }
+      return true;
+    });
+    if (kept.length > 0) nextMap[event] = kept;
+  }
+  return { nextMap, removedCount };
+}
+
+/** Put a stripped hooks map back onto a config object, dropping the `hooks` key entirely if empty. */
+function applyHooksMap(config, nextMap) {
+  const updated = { ...config };
+  if (Object.keys(nextMap).length > 0) {
+    updated.hooks = nextMap;
+  } else {
+    delete updated.hooks;
+  }
+  return updated;
+}
+
+/**
+ * Shared machinery for the three "remove UDS entries from a hooks config
+ * file" functions below. Handles the missing-file, invalid-JSON, and
+ * nothing-to-remove cases identically for all three, so their only
+ * difference is which file and which key they look at.
+ */
+function uninstallHookConfigFile({ configPath, label, dryRun, deleteEmptyFile }) {
+  const result = { removed: [], skipped: [], errors: [] };
+  if (!existsSync(configPath)) return result; // nothing installed here — nothing to report
+
+  let config;
+  try {
+    config = JSON.parse(readFileSync(configPath, 'utf-8'));
+  } catch (error) {
+    result.errors.push(`${label} — could not parse (${error.message}); left untouched`);
+    return result;
+  }
+
+  const { nextMap, removedCount } = stripUdsEntries(config.hooks);
+  if (removedCount === 0) {
+    result.skipped.push(`${label} (no UDS hook entries found)`);
+    return result;
+  }
+
+  const entryLabel = `${label} (${removedCount} UDS hook ${removedCount === 1 ? 'entry' : 'entries'})`;
+  if (dryRun) {
+    result.removed.push(entryLabel);
+    return result;
+  }
+
+  const updatedConfig = applyHooksMap(config, nextMap);
+  const isNowEmpty = Object.keys(updatedConfig).length === 0;
+
+  try {
+    if (deleteEmptyFile && isNowEmpty) {
+      unlinkSync(configPath);
+      result.removed.push(`${entryLabel}, file removed — created by UDS, now empty`);
+    } else {
+      writeFileSync(configPath, JSON.stringify(updatedConfig, null, 2) + '\n');
+      result.removed.push(entryLabel);
+    }
+  } catch (error) {
+    result.errors.push(`${label} — ${error.message}`);
+  }
+
+  return result;
+}
+
+/** Remove UDS's Stop/PreToolUse/etc. entries from .claude/settings.json (installHooks()'s output). */
+export function uninstallClaudeCodeHooks(projectPath, options = {}) {
+  return uninstallHookConfigFile({
+    configPath: join(projectPath, '.claude', 'settings.json'),
+    label: '.claude/settings.json',
+    dryRun: options.dryRun || false,
+    deleteEmptyFile: true,
+  });
+}
+
+/** Remove UDS's Stop entry from .codex/hooks.json (installCodexHooks()'s output). */
+export function uninstallCodexHooks(projectPath, options = {}) {
+  return uninstallHookConfigFile({
+    configPath: join(projectPath, '.codex', 'hooks.json'),
+    label: '.codex/hooks.json',
+    dryRun: options.dryRun || false,
+    deleteEmptyFile: true,
+  });
+}
+
+/** Remove UDS's AfterAgent entry from .gemini/settings.json (installGeminiHooks()'s output). */
+export function uninstallGeminiHooks(projectPath, options = {}) {
+  return uninstallHookConfigFile({
+    configPath: join(projectPath, '.gemini', 'settings.json'),
+    label: '.gemini/settings.json',
+    dryRun: options.dryRun || false,
+    deleteEmptyFile: true,
+  });
+}
+
+/**
+ * Remove UDS-related lines from .husky/pre-commit, the native
+ * .git/hooks/pre-commit fallback, and the enforcement-hook entries UDS wrote
+ * into .claude/settings.json, .codex/hooks.json and .gemini/settings.json.
  * @param {string} projectPath - Project root path
  * @param {Object} options - { dryRun: boolean }
  * @returns {Object} { removed: string[], skipped: string[], errors: string[] }
@@ -14,29 +174,24 @@ export function uninstallHook(projectPath, options = {}) {
 
   if (!existsSync(hookPath)) {
     result.skipped.push('.husky/pre-commit (not found)');
-    return result;
-  }
-
-  try {
-    const content = readFileSync(hookPath, 'utf-8');
-    const lines = content.split('\n');
-    const udsPattern = /uds\s+check|checkin-standards/;
-    const filteredLines = lines.filter(line => !udsPattern.test(line));
-
-    if (filteredLines.length === lines.length) {
-      result.skipped.push('.husky/pre-commit (no UDS lines found)');
-      return result;
-    }
+  } else {
+    try {
+      const content = readFileSync(hookPath, 'utf-8');
+      const lines = content.split('\n');
+      const udsPattern = /uds\s+check|checkin-standards/;
+      const filteredLines = lines.filter(line => !udsPattern.test(line));
 
-    if (dryRun) {
-      result.removed.push('.husky/pre-commit (UDS check lines)');
-      return result;
+      if (filteredLines.length === lines.length) {
+        result.skipped.push('.husky/pre-commit (no UDS lines found)');
+      } else if (dryRun) {
+        result.removed.push('.husky/pre-commit (UDS check lines)');
+      } else {
+        writeFileSync(hookPath, filteredLines.join('\n'), 'utf-8');
+        result.removed.push('.husky/pre-commit (UDS check lines)');
+      }
+    } catch (error) {
+      result.errors.push(`.husky/pre-commit — ${error.message}`);
     }
-
-    writeFileSync(hookPath, filteredLines.join('\n'), 'utf-8');
-    result.removed.push('.husky/pre-commit (UDS check lines)');
-  } catch (error) {
-    result.errors.push(`.husky/pre-commit — ${error.message}`);
   }
 
   // Also handle native .git/hooks/pre-commit (installed by uds init for non-Node projects)
@@ -70,5 +225,17 @@ export function uninstallHook(projectPath, options = {}) {
     }
   }
 
+  // Enforcement hooks written by installHooks()/installCodexHooks()/installGeminiHooks()
+  // — the gap this function used to have entirely (see module doc comment above).
+  for (const sub of [
+    uninstallClaudeCodeHooks(projectPath, { dryRun }),
+    uninstallCodexHooks(projectPath, { dryRun }),
+    uninstallGeminiHooks(projectPath, { dryRun }),
+  ]) {
+    result.removed.push(...sub.removed);
+    result.skipped.push(...sub.skipped);
+    result.errors.push(...sub.errors);
+  }
+
   return result;
 }

package/standards-registry.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "version": "6.13.0-beta.1",
+  "version": "6.13.0-beta.2",
   "lastUpdated": "2026-05-13",
   "description": "Standards registry for universal-dev-standards with integrated skills and AI-optimized formats",
   "formats": {
@@ -58,14 +58,14 @@
     "standards": {
       "name": "universal-dev-standards",
       "url": "https://github.com/AsiaOstrich/universal-dev-standards",
-      "version": "6.13.0-beta.1"
+      "version": "6.13.0-beta.2"
     },
     "skills": {
       "name": "universal-dev-standards",
       "url": "https://github.com/AsiaOstrich/universal-dev-standards",
       "localPath": "skills",
       "rawUrl": "https://raw.githubusercontent.com/AsiaOstrich/universal-dev-standards/main/skills",
-      "version": "6.13.0-beta.1",
+      "version": "6.13.0-beta.2",
       "note": "Skills are now included in the main repository under skills/"
     }
   },
@@ -2295,7 +2295,7 @@
       "id": "license-compliance",
       "name": "License Compliance Standards",
       "nameZh": "授權合規標準",
-      "version": "6.13.0-beta.1",
+      "version": "6.13.0-beta.2",
       "source": {
         "human": "core/license-compliance.md",
         "ai": "ai/standards/license-compliance.ai.yaml"
@@ -2307,7 +2307,7 @@
       "id": "verification-oracle",
       "name": "Verification Oracle Standards",
       "nameZh": "驗證 Oracle 標準",
-      "version": "6.13.0-beta.1",
+      "version": "6.13.0-beta.2",
       "source": {
         "human": "core/verification-oracle.md",
         "ai": "ai/standards/verification-oracle.ai.yaml"
@@ -2319,7 +2319,7 @@
       "id": "model-provenance",
       "name": "Model Provenance Policy Standards",
       "nameZh": "模型來源政策標準",
-      "version": "6.13.0-beta.1",
+      "version": "6.13.0-beta.2",
       "source": {
         "human": "core/model-provenance.md",
         "ai": "ai/standards/model-provenance.ai.yaml"
@@ -2331,7 +2331,7 @@
       "id": "resource-cost-boundary",
       "name": "Resource / Cost Boundary Declaration Standards",
       "nameZh": "資源／成本邊界宣告標準",
-      "version": "6.13.0-beta.1",
+      "version": "6.13.0-beta.2",
       "source": {
         "human": "core/resource-cost-boundary.md",
         "ai": "ai/standards/resource-cost-boundary.ai.yaml"