universal-dev-standards 5.1.0-beta.6 → 5.1.0

package/bundled/core/standard-lifecycle-management.md

@@ -0,0 +1,94 @@
+# Standard Lifecycle Management
+
+> **Source**: XSPEC-070 | **Driven by**: DEC-043 Wave 1 Governance Meta Pack | **Status**: Trial (2026-04-17 ~ 2026-10-17)
+
+## Overview
+
+UDS 標準生命週期狀態機。既有 66 個標準無明確狀態管理：新增標準沒有試驗期、過時標準無棄用路徑、廢棄標準仍被引用。本標準建立五狀態機（Proposed / Trial / Active / Deprecated / Archived）與合法轉移規則，並規範所有 `.ai.yaml` 標準必須在 frontmatter 標示 `status` / `since` / `expires` / `supersedes`。
+
+## Key Principles
+
+- **所有標準必有狀態**：frontmatter 必須包含 `status` 和 `since`
+- **Trial 必有期限**：`expires` 預設 since + 6 months
+- **Deprecated 必有替代**：`supersedes` 指向替代標準 id 或遷移文件
+- **禁止反向轉移**：Active → Proposed、Archived → Active 均無意義
+- **逾期自動 Archived**：Trial 到期未決則自動歸檔
+
+## States
+
+| State | Description | Skill-referenceable? |
+|-------|-------------|----------------------|
+| **Proposed** | 草案階段，未通過 admission | No |
+| **Trial** | 批准但試驗中（預設 6 個月）| Yes（標註 trial）|
+| **Active** | 全面採用，standard-of-truth | Yes |
+| **Deprecated** | 標記棄用，必須提供 `supersedes` | Yes（Skill 應警示）|
+| **Archived** | 已移除，僅保留歷史 | No |
+
+## Legal Transitions
+
+```
+Proposed ──(admission passed)──→ Trial
+Trial    ──(validated)──────────→ Active
+Trial    ──(expired/rejected)───→ Archived
+Active   ──(superseded)─────────→ Deprecated
+Deprecated ──(migration done)───→ Archived
+```
+
+**禁止的轉移**：
+
+- Active → Proposed（無意義）
+- Archived → Active（應重新申請 admission）
+- Deprecated → Active（應重新 Trial）
+- Proposed → Active（須先 Trial）
+
+## Frontmatter Required Fields
+
+### Always Required
+
+- `status`: proposed | trial | active | deprecated | archived
+- `since`: ISO-8601（進入當前狀態的日期）
+- `version`: semver 字串
+
+### Conditional
+
+| Field | When |
+|-------|------|
+| `expires` | `status = trial`（預設 since + 6 months）|
+| `supersedes` | `status = deprecated`（替代標準 id 或遷移文件路徑）|
+| `migration_guide` | `status = deprecated`（相對路徑，選填但強烈建議）|
+
+## Usage Examples
+
+- **Scenario 1 — Trial → Active**：`retry-standards` 處於 trial。2026-08-01 審視發現 DevAP Fix Loop 和 VibeOps Builder 均採用且無重大缺陷 → 轉 Active，`since=2026-08-01`，移除 `expires`
+- **Scenario 2 — Trial 逾期自動 Archived**：某標準 trial 期限 2026-10-17 到期未通過驗證 → 狀態轉 Archived，記錄原因
+- **Scenario 3 — Deprecated 帶遷移**：`legacy-retry-logic` 被 `retry-standards` 取代 → `status=deprecated, supersedes=retry-standards, migration_guide=docs/migrations/retry-v1-to-v2.md`；Skill 使用時顯示警告
+
+## Telemetry Event
+
+`standard_state_change`:
+
+```
+{
+  standard_id: string,
+  from_state: proposed|trial|active|deprecated|archived,
+  to_state:   proposed|trial|active|deprecated|archived,
+  reason: string,
+  timestamp: ISO-8601
+}
+```
+
+## Error Codes
+
+- `LIFECYCLE-001` — `MISSING_STATUS`
+- `LIFECYCLE-002` — `MISSING_EXPIRES`（trial 狀態）
+- `LIFECYCLE-003` — `MISSING_SUPERSEDES`（deprecated 狀態）
+- `LIFECYCLE-004` — `FORBIDDEN_TRANSITION`
+- `LIFECYCLE-005` — `TRIAL_EXPIRED`（期限已過但未決策）
+
+## References
+
+- AI-optimized: [ai/standards/standard-lifecycle-management.ai.yaml](../ai/standards/standard-lifecycle-management.ai.yaml)
+- XSPEC-070: DEC-043 Wave 1 Governance Meta Pack 跨專案規格
+- DEC-043: UDS 覆蓋完整性路線圖（驅動來源）
+- Related: `standard-admission-criteria`, `skill-standard-alignment-check`, `adr-standards`
+- Industry: IETF RFC lifecycle (Proposed → Draft → Internet Standard), Python PEP states, W3C Recommendation Track

package/bundled/core/timeout-standards.md

@@ -0,0 +1,63 @@
+# Timeout Standards
+
+> **Source**: XSPEC-067 | **Driven by**: DEC-043 Wave 1 Reliability Pack | **Status**: Trial (2026-04-17 ~ 2026-10-17)
+
+## Overview
+
+Timeout 標準 — 避免多層呼叫鏈中下層 timeout 大於上層（導致上層先 timeout 而下層仍在執行的資源浪費）。透過 cascading 預算規則（每層 ≤ 0.8× 上層）與 deadline propagation（傳 absolute timestamp）讓整條呼叫鏈精準 fail-fast。與 `circuit-breaker` 整合，timeout 計入 failure count。
+
+## Key Principles
+
+- **Cascading 預算**：多層呼叫的 timeout 必須逐層遞減，每下一層 ≤ `0.8 × 上層`（預留 20% buffer）
+- **Deadline Propagation**：跨服務呼叫必須傳遞 deadline（absolute timestamp），不得只傳 relative duration
+- **Fail-fast on Expired**：收到請求後若 `now > deadline`，立即 fail-fast，禁止發起下游呼叫
+- **Breaker 整合**：timeout 觸發計入對應 circuit-breaker 的 failure count
+- **禁止倒置**：下層 timeout 大於上層 timeout 等同沒設 timeout，配置違規
+
+## Cascading Budget Example
+
+```
+Client timeout         = 10000 ms
+Gateway timeout        =  8000 ms   (10000 × 0.8)
+Service A timeout      =  6400 ms   (8000  × 0.8)
+Downstream DB timeout  =  5120 ms   (6400  × 0.8)
+```
+
+0.8 為業界經驗值（gRPC / Envoy 常用 0.7~0.85），預留 20% buffer 給序列化、網路傳輸、重試開銷。
+
+## Deadline Propagation
+
+- Header: `X-Deadline`
+- Format: absolute ISO-8601 timestamp（不是 relative duration）
+- 發起呼叫前：`deadline = now + timeout`，寫入 header
+- 收到請求後：立即檢查 `now > deadline_header`，若是則回 `DEADLINE_EXCEEDED`
+- 向下游呼叫：`timeout = min(cascading_budget, deadline - now)`
+
+## Timeout Categories
+
+| Category | Default ms | Purpose |
+|----------|------------|---------|
+| `connect_timeout` | 5000 | 建立 TCP / TLS 連線 |
+| `request_timeout` | 30000 | 發送請求到收到完整回應 |
+| `idle_timeout` | 60000 | 連線閒置多久後關閉 |
+| `total_deadline` | 60000 | 含所有重試的整體上限 |
+
+## Usage Examples
+
+- **Scenario 1 — Cascading 預算**：Client 10s → Gateway 8s → Service A 6.4s → DB 5.12s，確保下層先 timeout，上層有機會 fallback
+- **Scenario 2 — Deadline 過期**：請求抵達 Service A 時 `X-Deadline` 已過期，立即回 `DEADLINE_EXCEEDED`，不呼叫 DB
+- **Scenario 3 — Timeout 觸發 breaker**：連續 3 次下游呼叫皆 timeout（failureThreshold=3），第 4 次 breaker 進入 OPEN
+
+## Error Codes
+
+- `TIMEOUT-001` — `REQUEST_TIMEOUT`（單次請求超時）
+- `TIMEOUT-002` — `DEADLINE_EXCEEDED`（整體 deadline 已過）
+- `TIMEOUT-003` — `CASCADING_BUDGET_VIOLATION`（下層 > 上層，配置錯誤）
+
+## References
+
+- AI-optimized: [ai/standards/timeout-standards.ai.yaml](../ai/standards/timeout-standards.ai.yaml)
+- XSPEC-067: DEC-043 Wave 1 Reliability Pack 跨專案規格
+- DEC-043: UDS 覆蓋完整性路線圖（驅動來源）
+- Related: `circuit-breaker`, `retry-standards`, `failure-source-taxonomy`
+- Industry: gRPC deadline propagation, Envoy timeout budgeting, Google SRE Book Ch.22

package/bundled/core/token-budget.md

@@ -0,0 +1,58 @@
+# Token Budget Zone Standard
+
+> **Source**: XSPEC-036 | **Borrowed from**: claude-code-book Ch.7
+
+## Overview
+
+The Token Budget Zone model divides token usage into four progressive zones, each triggering increasingly aggressive protection strategies. This prevents the "works fine until sudden crash" failure mode and gives systems time to gracefully degrade before hitting hard limits.
+
+## Zones
+
+| Zone | Range | Action | Log Level |
+|------|-------|--------|-----------|
+| **SAFE** | 0–84% | Normal operation | — |
+| **WARNING** | 85–89% | Emit event, notify coordinator | info |
+| **DANGER** | 90–94% | Trigger lightweight compression (Snip) | warn |
+| **BLOCKING** | 95–100% | Reject new requests, return error | error |
+
+## Constants
+
+```typescript
+const TOKEN_BUDGET_ZONE = {
+  WARNING_THRESHOLD: 0.85,
+  DANGER_THRESHOLD: 0.90,
+  BLOCKING_THRESHOLD: 0.95,
+} as const;
+
+type TokenBudgetZone = "safe" | "warning" | "danger" | "blocking";
+```
+
+## DANGER Zone Actions
+
+When entering DANGER zone (90–94%):
+1. **Tool Result Snip**: Truncate large tool outputs, keep summaries
+2. **Reduce maxToolRounds**: Cut by 20% for remaining agents
+3. **Persist to disk**: Move important outputs out of context
+
+## Post-Compact Budget
+
+Compression operations need output space to succeed. Reserve constants:
+
+| Constant | Value | Purpose |
+|----------|-------|---------|
+| `MAX_FILES_TO_RESTORE` | 5 | Max files to restore after compaction |
+| `TOTAL_TOKEN_BUDGET` | 50,000 | Total post-compact token budget |
+| `MAX_TOKENS_PER_FILE` | 5,000 | Per-file token limit |
+
+## Applicable Scenarios
+
+- DevAP task execution token monitoring
+- VibeOps 9-Agent pipeline cumulative context management
+- VibeOps PipelineMemory Snip trigger condition
+- Any environment with `maxTotalTokens` limit
+
+## References
+
+- AI-optimized: [ai/standards/token-budget.ai.yaml](../ai/standards/token-budget.ai.yaml)
+- XSPEC-036: Cross-project specification
+- Borrowed from: [claude-code-book](https://github.com/lintsinghua/claude-code-book) Ch.7 four-zone context management

package/bundled/core/translation-lifecycle-standards.md

@@ -0,0 +1,162 @@
+# Translation Lifecycle Standards
+
+> **Language**: English | [繁體中文](../locales/zh-TW/core/translation-lifecycle-standards.md)
+
+**Version**: 1.0.0
+**Last Updated**: 2026-04-20
+**Status**: Trial (expires 2026-10-20)
+**Applicability**: All projects with multi-language documentation
+**Scope**: universal
+**Source**: Derived from UDS BUG-A06 post-mortem (2026-04-20)
+**Parent Standard**: [documentation-lifecycle](documentation-lifecycle.md)
+
+---
+
+## Purpose
+
+Translation lifecycle standards: MISSING vs OUTDATED distinction, semver-aware severity classification, and automation integration (pre-commit hook, release gate).
+
+The `documentation-lifecycle` standard mentions translation sync as a release-gate check, but does not define how to classify or respond to different degrees of drift. This standard fills that gap: a translation that is absent is fundamentally different from one that is slightly stale, and a major-version gap is fundamentally different from a patch bump. Without this distinction, teams either over-block (failing on any staleness) or under-block (ignoring all staleness until it becomes a user-visible defect).
+
+**Evidence (BUG-A06 post-mortem)**:
+1. UDS accumulated 32 missing translations over 3 months of adding new standards without a MISSING gate — only discovered during a Q2 audit.
+2. `anti-hallucination.md` zh-CN was at 1.5.0 while the source shipped 1.5.1 — a new Agent Epistemic Calibration framework section was completely absent in the zh-CN edition, invisible to users.
+
+---
+
+## Core Rules
+
+- `MISSING` (translation file does not exist) is always a release blocker — `exit 1`
+- `MAJOR` version gap (source X vs translation x where X > x) is a release blocker — `exit 1`
+- `MINOR` version gap is advisory — warn prominently, do not block
+- `PATCH` version gap is advisory — warn softly, do not block
+- Severity is determined by semver comparison of `source_version` in translation frontmatter vs current source file version
+- Every translation file MUST have YAML frontmatter with `source`, `source_version`, `translation_version`, `last_synced`, `status`
+- When a source standard is modified, the translation's `source_version` becomes stale immediately — this drift is detectable at commit time via pre-commit hook
+
+---
+
+## Severity Classification
+
+| Level | Condition | Exit Code | Action |
+|-------|-----------|-----------|--------|
+| `MISSING` | Translation file does not exist | 1 | Create before release |
+| `MAJOR` | source MAJOR > translation MAJOR | 1 | Update before stable release |
+| `MINOR` | source MINOR > translation MINOR | 0 | Update before next release (advisory) |
+| `PATCH` | source PATCH > translation PATCH | 0 | Update when convenient (advisory) |
+| `CURRENT` | source_version == translation source_version | 0 | No action needed |
+
+### Semver Diff Formula
+
+```
+diff_level = compare(
+  strip_prerelease(current_source_version),
+  strip_prerelease(translation.source_version)
+)
+
+where: MAJOR if maj differs, MINOR if min differs, else PATCH
+```
+
+---
+
+## Trigger Conditions
+
+| Event | Required Action |
+|-------|----------------|
+| New standard added to `core/` | Create translation in all supported locales (MISSING check blocks release) |
+| Standard version bumped (PATCH) | Update translation's `source_version` + `last_synced` when convenient |
+| Standard version bumped (MINOR) | Update translation content + frontmatter before next release |
+| Standard version bumped (MAJOR) | Update translation content + frontmatter before current release (blocker) |
+| Translation file manually updated | Bump `translation_version` + `last_synced` in frontmatter |
+
+---
+
+## Translation Frontmatter Protocol
+
+Every translation file MUST begin with:
+
+```yaml
+---
+source: ../../../core/<filename>.md          # relative path to source
+source_version: <X.Y.Z>                      # source version at last sync
+translation_version: <X.Y.Z>                 # translation's own version
+last_synced: <YYYY-MM-DD>                    # date of last sync
+status: current | outdated | draft           # human-readable status
+---
+```
+
+When updating a translation after a source change:
+1. Translate the new/changed content
+2. Set `source_version` = new source version
+3. Set `translation_version` = same as `source_version` (or bump independently)
+4. Set `last_synced` = today's date
+5. Set `status: current`
+
+---
+
+## Automation Integration
+
+### Pre-Commit Hook
+
+When `core/*.md` files are staged, the pre-commit hook runs `check-translation-sync.sh` and shows OUTDATED warnings. The hook **never blocks** the commit (blocking at commit time is too disruptive) — it is a reminder only.
+
+Setup: `./scripts/install-hooks.sh` (one-time, after clone)
+
+### Release Gate (`check-translation-sync.sh`)
+
+Run before `npm publish` or as part of `pre-release-check.sh`:
+
+```bash
+bash scripts/check-translation-sync.sh
+# exit 1 if MISSING or MAJOR gap found
+# exit 0 if only MINOR/PATCH gaps (with advisory output)
+```
+
+### Version Bump Integration (`bump-version.sh`)
+
+`bump-version.sh` automatically runs `check-translation-sync.sh` after version files are updated, showing the translation health snapshot at the moment of bump — giving the author immediate feedback on what needs updating before publish.
+
+---
+
+## Scenarios
+
+**Scenario 1 — Standard patch bump (1.0.0 → 1.0.1)**
+- Translation `source_version: 1.0.0`, source now at `1.0.1`
+- Severity: `PATCH` — advisory, exit 0
+- Action: Update at next opportunity, no release block
+
+**Scenario 2 — Standard minor bump with new section (1.0.0 → 1.1.0)**
+- Translation `source_version: 1.0.0`, source now at `1.1.0`
+- Severity: `MINOR` — advisory, exit 0
+- Action: Update before next release; zh-CN users missing new content
+
+**Scenario 3 — Standard major rewrite (1.x.x → 2.0.0)**
+- Translation `source_version: 1.5.0`, source now at `2.0.0`
+- Severity: `MAJOR` — blocker, exit 1
+- Action: Must update before stable release
+
+**Scenario 4 — New standard, no translation file**
+- No `locales/zh-TW/core/new-standard.md` exists
+- Severity: `MISSING` — blocker, exit 1
+- Action: Create translation file before release
+
+---
+
+## Error Codes
+
+| Code | Description |
+|------|-------------|
+| `TRANS-001` | `MISSING_TRANSLATION` — Translation file does not exist for a source standard |
+| `TRANS-002` | `MAJOR_VERSION_GAP` — Translation source_version is MAJOR behind current source |
+| `TRANS-003` | `MISSING_FRONTMATTER` — Translation file lacks required YAML frontmatter |
+| `TRANS-004` | `STALE_SOURCE_REF` — `source` path in frontmatter points to non-existent file |
+
+---
+
+## References
+
+- [documentation-lifecycle.md](documentation-lifecycle.md) — Parent standard; trigger matrix and check pyramid
+- [standard-admission-criteria.md](standard-admission-criteria.md) — How new standards are admitted (triggers TRANS-001)
+- `scripts/check-translation-sync.sh` — Implementation of this standard's automation rules
+- `.githooks/pre-commit` — Pre-commit integration
+- `scripts/install-hooks.sh` — Hook installation

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

@@ -1,8 +1,8 @@
 ---
 source: ../../CHANGELOG.md
-source_version: 5.1.0-beta.6
-translation_version: 5.1.0-beta.6
-last_synced: 2026-04-13
+source_version: 5.1.0
+translation_version: 5.1.0
+last_synced: 2026-04-20
 status: current
 ---
 
@@ -17,6 +17,54 @@ status: current
 
 ## [Unreleased]
 
+## [5.1.0] - 2026-04-20
+
+> **正式版**：BUG-A06 i18n 完整性 — 新增 32 份缺失翻译、Semver 感知翻译闸门、新增 `translation-lifecycle-standards` UDS 标准。BUG-A07 Shell 测试覆盖 — 20+ 脚本的 bats smoke tests。BUG-A08 假通过测试审计 — 修正 22 个测试。Pre-release Batch 0：6 个标准从 Trial 升至 Adopt（DEC-021/025/031/035/038/040）。标准总数：106 个。
+
+### 新增
+- **`translation-lifecycle-standards`**（Trial，到期 2026-10-20）：新 UDS 标准，定义 MISSING 与 OUTDATED 的区别、Semver 严重度分级（MISSING/MAJOR = 发布阻塞器，MINOR/PATCH = advisory），以及自动化集成（pre-commit hook、release gate、bump-version 集成）。来源：BUG-A06 事后分析。
+- **`.githooks/pre-commit`** + **`scripts/install-hooks.sh`**：commit 时若暂存 `core/*.md` 文件则显示 OUTDATED 警告，永不阻塞 commit。通过 `./scripts/install-hooks.sh` 启用。
+- **32 份 zh-TW 与 zh-CN 翻译**（BUG-A06）：所有核心标准现已有完整 zh-TW 和 zh-CN 翻译，包含 `circuit-breaker`、`token-budget`、`dual-phase-output`、`failure-source-taxonomy`、`immutability-first`、`security-decision`、`capability-declaration`、`recovery-recipe-registry`、`retry-standards`、`health-check-standards`、`timeout-standards`、`skill-standard-alignment-check`、`standard-admission-criteria`、`standard-lifecycle-management`、`packaging-standards`、`frontend-design-standards`、`translation-lifecycle-standards` 等。
+- **bats smoke tests**（BUG-A07）：`tests/scripts/` — 20+ 个 Shell 脚本的 smoke tests，涵盖 `check-translation-sync.sh`、`check-version-sync.sh`、`bump-version.sh`、`install-hooks.sh` 等。
+
+### 变更
+- **`check-translation-sync.sh`**：Semver 感知严重度 — MAJOR 版本落差现在 exit 1（发布阻塞器）；MINOR/PATCH 落差 exit 0 附 advisory 警告。新增 `semver_diff()` 函数与 `[MAJOR]`/`[MINOR]`/`[PATCH]` 严重度标签。
+- **`bump-version.sh`**：更新版本文件后自动执行 `check-translation-sync.sh`，在升版时提供翻译健康状态快照。
+- **`scripts/pre-release-check.sh`**：更新为将 `check-translation-sync.sh` 作为硬闸门（MISSING + MAJOR = exit 1）。
+
+### 修正
+- **zh-CN `anti-hallucination.md`**（BUG-A06）：从 1.5.0 更新至 1.5.1 — 补上缺失的「Agent 认识论校准」章节（Answer/Ask/Abstain 框架，XSPEC-008）。该章节自 2026-04-13 起在 zh-CN 中完全缺失。
+- **22 个假通过测试**（BUG-A08）：修正未正确验证行为的测试，加入真实断言。
+
+### 升至 Adopt（Pre-release Batch 0）
+- `circuit-breaker`（DEC-021）：Trial 6 个月后升至 Adopt
+- `token-budget`（DEC-025）：Trial 6 个月后升至 Adopt
+- `dual-phase-output`（DEC-031）：Trial 6 个月后升至 Adopt
+- `security-decision`（DEC-035）：Trial 6 个月后升至 Adopt
+- `immutability-first`（DEC-038）：Trial 6 个月后升至 Adopt
+- `failure-source-taxonomy`（DEC-040）：Trial 6 个月后升至 Adopt
+
+[5.1.0]: https://github.com/AsiaOstrich/universal-dev-standards/compare/v5.1.0-beta.7...v5.1.0
+
+## [5.1.0-beta.7] - 2026-04-17
+
+> **Beta Release**：DEC-043 Wave 1 — 六个 Trial 状态标准，涵盖可靠性模式与治理 Meta 框架。
+
+### 新增
+- **Reliability 包（XSPEC-067）**：三个 Trial 状态的韧性模式标准。
+  - `retry-standards`：重试策略（指数退避、Jitter、幂等性保护）。
+  - `timeout-standards`：分层 timeout 预算（call / request / end-to-end）与传递规则。
+  - `health-check-standards`：Liveness / Readiness / Startup probe 语义。
+- **治理 Meta 包（XSPEC-070，Wave 1 前置）**：三个定义「标准如何被纳入、管理、与 Skill 对齐」的 Trial 标准。
+  - `standard-admission-criteria`：新标准提案的入场门槛。
+  - `standard-lifecycle-management`：Trial → Stable → Deprecated → Archived 状态流转。
+  - `skill-standard-alignment-check`：Skill 与其引用标准之间的对齐稽核。
+- 六份标准皆遵循 UDS 三方同步要求：`.ai.yaml`（机器）+ `.md`（人类）+ `cli/standards-registry.json` entry（+66 行）。
+
+### 背景
+- 由 **DEC-043**（UDS 覆盖完整性路线图）驱动。治理 Meta 包为 Wave 1 前置条件，解锁 Wave 2–4（八个主题标准包：SRE / CI-CD / IaC / 合规 / Reliability / 资料工程 / 产品 / 治理 — XSPEC-063~070）。
+- PR：#77
+
 ## [5.1.0-beta.6] - 2026-04-13
 
 > **Beta 版本**：修复 `uds init` 崩溃问题、E2E 测试隔离问题，以及 macOS 显示语言检测失效问题。

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

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

package/bundled/locales/zh-CN/core/anti-hallucination.md

@@ -1,8 +1,8 @@
 ---
 source: ../../../core/anti-hallucination.md
-source_version: 1.5.0
-translation_version: 1.5.0
-last_synced: 2026-02-10
+source_version: 1.5.1
+translation_version: 1.5.1
+last_synced: 2026-04-20
 status: current
 ---
 
@@ -742,6 +742,24 @@ Redis 是最佳选择。如果这是单实例应用程序且有
 
 ---
 
+## Agent 认识论校准（v1.4.0，XSPEC-008）
+
+Agent 必须使用 Answer / Ask / Abstain 框架声明其认识论状态：
+
+| 动作 | 使用时机 | 必填字段 |
+|------|---------|---------|
+| `answer` | 拥有足够信息 | 无（completeness/confidence 为选填）|
+| `ask` | 缺少关键信息 | `missing_variables` 列表 |
+| `abstain` | 真正超出能力范围 | `abstain_reason` |
+
+**Fail-closed Agent**（必须始终回答）：`evaluator`、`guardian`
+
+**向后兼容**：缺少 `epistemic` 字段时默认为 `action_type: "answer"`。
+
+参见：XSPEC-008、DEC-014（PassiveQA）
+
+---
+
 ## 相关标准
 
 - [测试标准](testing-standards.md) - 确保验证 AI 分析结果（或使用 `/testing-guide` 技能）
@@ -754,6 +772,7 @@ Redis 是最佳选择。如果这是单实例应用程序且有
 
 | 版本 | 日期 | 变更 |
 |------|------|------|
+| 1.5.1 | 2026-04-13 | 新增: Agent 认识论校准（Answer/Ask/Abstain）框架（XSPEC-008）|
 | 1.4.0 | 2026-01-19 | 新增: 副作用分析规则（第 7 条禁止行为）、工作流程步骤及检查清单项目 |
 | 1.3.1 | 2025-12-24 | 新增: 相关标准章节 |
 | 1.3.0 | 2025-12-22 | 增强: 禁止行为章节，新增详细对比范例 |