universal-dev-standards 5.17.0 → 6.1.0

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

@@ -1,8 +1,8 @@
 # UDS 速查表
 
-> Quick reference for all UDS features | Last updated: 2026-05-14
+> Quick reference for all UDS features | Last updated: 2026-07-09
 
-**Language**: [English](../../../docs/CHEATSHEET.md) | [繁體中文](../../zh-TW/docs/CHEATSHEET.md) | 简体中文
+**Language**: [English](../../../docs/user/CHEATSHEET.md) | [繁體中文](../../zh-TW/docs/CHEATSHEET.md) | 简体中文
 
 ---
 
@@ -17,7 +17,6 @@
 | `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) |
 
 ## 💬 斜线命令
@@ -34,6 +33,7 @@
 | `/check` | [UDS] Verify standards adoption status |
 | `/checkin` | "[UDS] Pre-commit quality gates verification" |
 | `/ci-cd` | "[UDS] Guide CI/CD pipeline design, configuration and optimization" |
+| `/code-review` | [UDS] Perform systematic code review with checklist |
 | `/commit` | [UDS] Generate commit messages following Conventional Commits standard |
 | `/config` | [UDS] Configure project development standards |
 | `/coverage` | [UDS] Analyze test coverage and provide recommendations |
@@ -52,6 +52,7 @@
 | `/guide` | [UDS] Access Universal Development Standards guides and references. |
 | `/incident` | "[UDS] Guide incident response, root cause analysis and post-mortem documentation" |
 | `/init` | [UDS] Initialize development standards in current project |
+| `/journey-test` | [UDS] Generate coherent user journey test plans (TESTPLAN) and E2E skeletons from a project description. |
 | `/methodology` | [UDS] Manage development methodology workflow |
 | `/metrics` | "[UDS] Track development metrics, code quality indicators and project health" |
 | `/migrate` | "[UDS] Guide code migration, framework upgrades and technology modernization" |
@@ -64,12 +65,12 @@
 | `/reverse-sdd` | [UDS] Reverse engineer code into SDD specification document |
 | `/reverse-tdd` | [UDS] Analyze BDD-TDD coverage gaps |
 | `/reverse` | [UDS] Reverse engineer code to Specs, BDD, or TDD coverage. |
-| `/review` | [UDS] Perform systematic code review with checklist |
 | `/runbook` | "[UDS] Guide runbook creation, maintenance, drills, and coverage reporting" |
 | `/scan` | "[UDS] Guide automated security scanning, dependency auditing and secret detection" |
 | `/sdd-retro` | [UDS] Create retroactive specs for untracked feat/fix commits |
 | `/sdd` | [UDS] Create or review specification documents for Spec-Driven Development |
 | `/security` | "[UDS] Guide security review and vulnerability assessment following OWASP standards" |
+| `/skill-builder` | [UDS] Identify repeated processes and build Skills with the right development depth. |
 | `/slo` | "[UDS] Guide SLI selection, SLO setting, and Error Budget management" |
 | `/tdd` | [UDS] Guide through Test-Driven Development workflow |
 | `/update` | [UDS] Update development standards to latest version |
@@ -85,7 +86,7 @@
 | `ai-instruction-standards` | Create and maintain AI instruction files (CLAUDE.md, AGENTS. |
 | `api-design-assistant` | Guide API design following REST, GraphQL, and gRPC best prac |
 | `atdd-assistant` | "[UDS] Guide through Acceptance Test-Driven Development work |
-| `audit-assistant` | "[UDS] UDS Health & Feedback System \| UDS 健康檢查與回饋系統" |
+| `audit-assistant` | "[UDS] UDS Health & Feedback System" |
 | `bdd-assistant` | "[UDS] Guide through Behavior-Driven Development workflow" |
 | `brainstorm-assistant` | "[UDS] Structured AI-assisted brainstorming before spec crea |
 | `changelog-guide` | "[UDS] Generate and maintain CHANGELOG.md entries" |
@@ -105,7 +106,8 @@
 | `error-code-guide` | Design consistent error codes following the PREFIX_CATEGORY_ |
 | `git-workflow-guide` | Guide Git branching strategies, branch naming, and merge ope |
 | `incident-response-assistant` | Guide incident response, root cause analysis, and post-morte |
-| `journey-test-assistant` | "[UDS] 從專案描述生成連貫使用者旅程測試計畫（TESTPLAN）與 E2E 骨架" |
+| `journey-test-assistant` | "[UDS] Generate coherent user journey test plans (TESTPLAN)  |
+| `knowledge-graph` | "[UDS] Trace spec/decision/code impact chains via a knowledg |
 | `logging-guide` | Implement structured logging with proper log levels and sens |
 | `metrics-dashboard-assistant` | "[UDS] Track development metrics, code quality indicators, a |
 | `migration-assistant` | "[UDS] Guide code migration, framework upgrades, and technol |
@@ -120,7 +122,7 @@
 | `release-standards` | "[UDS] Guide release process and changelogs" |
 | `requirement-assistant` | "[UDS] Write user stories and requirements following INVEST  |
 | `retrospective-assistant` | [UDS] Guide structured team retrospectives for Sprint and Re |
-| `reverse-engineer` | "[UDS] System archeology — reverse engineer code across Logi |
+| `reverse-engineer` | "[UDS] System archeology - reverse engineer code across Logi |
 | `runbook-assistant` | Guide runbook creation, maintenance, and drill exercises. |
 | `security-assistant` | Guide security review and vulnerability assessment following |
 | `security-scan-assistant` | Guide automated security scanning, dependency auditing, and  |
@@ -174,6 +176,7 @@
 | `anti-hallucination` | This standard defines strict guidelines for AI ass |
 | `anti-sycophancy-prompting` | This standard defines techniques and rules for des |
 | `api-design-standards` | This standard defines comprehensive guidelines for |
+| `audit-trail` | Audit Trail Standards |
 | `behavior-driven-development` | Behavior-Driven Development (BDD) Standards |
 | `behavior-snapshot` | Behavior Snapshot Standard |
 | `branch-completion` | Define a standardized workflow for completing deve |
@@ -188,13 +191,16 @@
 | `circuit-breaker` | Circuit Breaker Standard |
 | `code-review-checklist` | This standard provides a comprehensive checklist f |
 | `commit-message-guide` | Standardized commit messages improve code review e |
+| `container-image-standards` | Container Image Build and Security Standards |
 | `container-security` | 容器安全標準 |
 | `containerization-standards` | Containerization Standards |
 | `context-aware-loading` | This standard defines a protocol for AI tools to s |
 | `contract-testing-standards` | Contract testing verifies that a provider (API ser |
 | `cost-budget-test` | Cost Budget Test Standards |
 | `cross-flow-regression` | This standard defines cross-flow regression testin |
+| `data-contract` | Data Contract Standards |
 | `data-migration-testing` | Data Migration Testing |
+| `data-pipeline` | Data Pipeline Standards |
 | `database-standards` | This standard defines guidelines for database desi |
 | `deployment-standards` | This standard defines guidelines for safely deploy |
 | `deprecation-standards` | Deprecation & Sunset Standards |
@@ -210,6 +216,7 @@
 | `estimation-standards` | Estimation Standards |
 | `execution-history` | Execution History Repository Standards |
 | `failure-source-taxonomy` | Failure Source Taxonomy Standard |
+| `feature-discovery-standards` | Feature Discovery Standards |
 | `feature-flag-standards` | Feature Flag Management Standards |
 | `feature-manifest-standard` | Feature Manifest Standard |
 | `flaky-test-management` | Flaky Test Management Standards |
@@ -221,44 +228,60 @@
 | `git-worktree` | Define a lifecycle for using Git worktrees to isol |
 | `governance-layer` | A governance layer provides a shared anchor for al |
 | `health-check-standards` | Health Check Standards |
+| `iac-design-principles` | Infrastructure as Code Design Principles |
 | `immutability-first` | Immutability-First Architecture Standard |
+| `incident-response` | Incident Response Standards |
+| `knowledge-graph-memory` | This standard defines a **relationship schema** so |
 | `knowledge-transfer-standards` | Knowledge Transfer Standards |
+| `license-compliance` | License Compliance Standards |
 | `llm-output-validation` | LLM 輸出驗證標準 |
 | `logging-standards` | Logging Standards |
 | `mock-boundary` | This document defines rules for what can and canno |
+| `model-provenance` | Model Provenance Policy Standards |
 | `model-selection` | Define a cost-effective strategy for selecting AI  |
+| `multi-environment-e2e-testing` | Multi-Environment E2E Testing Standards |
 | `mutation-testing` | Mutation testing evaluates test suite effectivenes |
 | `no-cicd-deployment` | No-CI/CD Deployment Strategy |
 | `observability-standards` | Observability Standards |
 | `packaging-standards` | This standard defines a Recipe-based packaging fra |
 | `performance-standards` | This standard defines comprehensive guidelines for |
+| `pii-classification` | PII Classification and Handling Standards |
 | `pipeline-integration-standards` | Pipeline Integration Standards |
 | `pipeline-security-gates` | Pipeline Security Gates（CI Pipeline 安全檢查點） |
 | `policy-as-code-testing` | Policy as Code 測試標準 |
 | `postmortem-standards` | Postmortem Standards (Blameless Post-Incident Review) |
+| `prd-standards` | Product Requirements Document Standards |
 | `privacy-standards` | Privacy Standards |
+| `product-metrics-standards` | Product Metrics Framework Standards |
 | `project-context-memory` | This standard defines a structured system for capt |
 | `project-structure` | This standard defines conventions for project dire |
 | `prompt-regression` | Prompt Regression Standards |
 | `property-based-testing` | Property-Based Testing Standards |
+| `push-standards` | Git Push Safety Gates |
 | `recovery-recipe-registry` | Recovery Recipe Registry Standard |
 | `refactoring-standards` | This standard defines comprehensive guidelines for |
 | `release-quality-manifest` | Release Quality Manifest |
 | `release-readiness-gate` | This standard defines a **single, aggregated Relea |
 | `replay-test` | Replay Test Standards |
 | `requirement-engineering` | Requirement Engineering Standards |
+| `resource-cost-boundary` | Resource / Cost Boundary Declaration Standards |
 | `retrospective-standards` | Retrospectives are structured team reflections tha |
 | `retry-standards` | Retry Standards |
 | `reverse-engineering-standards` | This standard defines the principles, workflows, a |
 | `rollback-standards` | Rollback Standards（回滾標準） |
 | `runbook-standards` | Runbook Standards |
+| `runbook` | Runbook Writing Standards |
 | `sast-advanced` | This standard defines Advanced Static Application  |
+| `schema-evolution` | Schema Evolution Standards |
+| `secret-management-standards` | Secret Management and Credential Hygiene Standards |
 | `secure-op` | Secure-Op：AI Agent 安全操作標準 |
 | `security-decision` | Security Decision Standard |
 | `security-standards` | This standard defines comprehensive security guide |
 | `security-testing` | This document defines the security testing methodo |
+| `self-review-protocol` | This standard mandates a **self-review pass** on l |
 | `server-ops-security` | 伺服器操作安全標準 |
 | `skill-standard-alignment-check` | Skill-Standard Alignment Check |
+| `slo-sli` | SLO/SLI Definition Standards |
 | `slo-standards` | SLO Standards (Service Level Objectives) |
 | `smoke-test` | Smoke Test Standards |
 | `spec-driven-development` | Spec-Driven Development (SDD) Standards |
@@ -277,7 +300,10 @@
 | `timeout-standards` | Timeout Standards |
 | `token-budget` | Token Budget Zone Standard |
 | `translation-lifecycle-standards` | Translation lifecycle standards: MISSING vs OUTDAT |
+| `user-journey-testing` | User Journey Testing Standard |
+| `user-story-mapping` | User Story Mapping Standards |
 | `verification-evidence` | Establish an "Iron Law" that no task can be claime |
+| `verification-oracle` | Verification Oracle Standards |
 | `versioning` | This standard defines how to version software rele |
 | `virtual-organization-standards` | This standard treats the AI ecosystem as a "Virtua |
 | `workflow-enforcement` | Workflow Enforcement Standards |
@@ -328,10 +354,12 @@
 | `check-version-sync.ps1` | Check Version Sync |
 | `check-version-sync.sh` | Version Sync Checker |
 | `check-workflow-compliance.sh` | DEPRECATED: Use 'npx tsx scripts/check-workflow-co |
+| `commitlint-bilingual-rule.mjs` | commitlint-bilingual-rule.mjs — custom commitlint  |
 | `convert-md-to-yaml.mjs` | Markdown to AI-YAML Conversion Script |
 | `fix-manifest-paths.ps1` | Fix Manifest Paths |
 | `fix-manifest-paths.sh` | Manifest Path Fixer |
 | `generate-docs.mjs` | Generate Docs |
+| `generate-locale-coverage.mjs` | Locale Coverage Generator |
 | `generate-version-manifest.mjs` | Generate Version Manifest (SPEC-SELFDIAG-001 REQ-9 |
 | `install-hooks.mjs` | Install Hooks |
 | `install-hooks.sh` | DEPRECATED: Use 'node scripts/install-hooks.mjs' i |
@@ -340,6 +368,7 @@
 | `pre-release-check.sh` | Pre-release Check Script |
 | `pre-release.ps1` | Pre-Release Preparation Script for Universal Devel |
 | `pre-release.sh` | Pre-Release Preparation Script |
+| `setup-hooks.sh` | setup-hooks.sh — Install git hooks for UDS repo |
 | `setup-husky.mjs` | Cross-platform Husky Setup Script |
 | `sync-manifest.mjs` | Sync Manifest |
 

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

@@ -1,23 +1,23 @@
 # UDS 功能参考手册
 
 > Universal Development Standards - 完整功能文档
-> Auto-generated | Last updated: 2026-05-14
+> Auto-generated | Last updated: 2026-07-09
 
-**Language**: [English](../../../docs/FEATURE-REFERENCE.md) | [繁體中文](../../zh-TW/docs/FEATURE-REFERENCE.md) | 简体中文
+**Language**: [English](../../../docs/reference/FEATURE-REFERENCE.md) | [繁體中文](../../zh-TW/docs/FEATURE-REFERENCE.md) | 简体中文
 
 ---
 
 ## 目录
 
 1. [CLI 指令](#cli-commands) (9)
-2. [斜线命令](#slash-commands) (49)
-3. [技能](#skills) (54)
+2. [斜线命令](#slash-commands) (51)
+3. [技能](#skills) (55)
 4. [代理](#agents) (5)
 5. [工作流程](#workflows) (5)
-6. [核心规范](#core-standards) (125)
-7. [脚本](#scripts) (55)
+6. [核心规范](#core-standards) (149)
+7. [脚本](#scripts) (58)
 
-**Total Features: 302**
+**Total Features: 332**
 
 ---
 
@@ -89,6 +89,7 @@
 | `--migrate` | Migrate legacy manifest to hash-based tracking |
 | `--offline` | Skip npm registry check for CLI updates |
 | `--force` | Bypass UDS source-repo self-adoption guard (DEC-044 / XSPEC-071) |
+| `--i18n` | Run i18n lint rules (XSPEC-239) across canonical + locale variants |
 
 ### `uds update`
 
@@ -109,6 +110,7 @@
 | `--plan` | Show reconciliation plan without executing (like terraform plan) |
 | `--force` | Force update all files, ignoring hash comparison |
 | `--rollback` | Rollback to the most recent backup |
+| `--locale` | Override locale for skills install (zh-tw, zh-cn, en); also reads .uds/install.yaml + UDS_LOCALE env |
 
 ### `uds skills`
 
@@ -130,20 +132,6 @@
 
 **说明**: Manage UDS workflows (list, install, info, execute, status)
 
-**选项**:
-| Option | 说明 |
-|--------|-------------|
-| `--installed` | Show installation status for all AI tools |
-| `-t, --tool` | Target AI tool (default: claude-code) |
-| `-g, --global` | Install to user level instead of project level |
-| `-y, --yes` | Skip confirmation prompts |
-| `-t, --tool` | Target AI tool (default: claude-code) |
-| `--resume` | Resume from saved state |
-| `--restart` | Restart from beginning (discard saved state) |
-| `-v, --verbose` | Show detailed output |
-| `--dry-run` | Show steps without executing |
-| `-y, --yes` | Skip confirmation prompts |
-
 ### `uds ai-context`
 
 **说明**: Manage AI context configuration (init, validate, graph)
@@ -164,6 +152,7 @@
 | `/check` | [UDS] Verify standards adoption status |
 | `/checkin` | "[UDS] Pre-commit quality gates verification" |
 | `/ci-cd` | "[UDS] Guide CI/CD pipeline design, configuration and optimization" |
+| `/code-review` | [UDS] Perform systematic code review with checklist |
 | `/commit` | [UDS] Generate commit messages following Conventional Commits standard |
 | `/config` | [UDS] Configure project development standards |
 | `/coverage` | [UDS] Analyze test coverage and provide recommendations |
@@ -182,6 +171,7 @@
 | `/guide` | [UDS] Access Universal Development Standards guides and references. |
 | `/incident` | "[UDS] Guide incident response, root cause analysis and post-mortem documentation" |
 | `/init` | [UDS] Initialize development standards in current project |
+| `/journey-test` | [UDS] Generate coherent user journey test plans (TESTPLAN) and E2E skeletons from a project description. |
 | `/methodology` | [UDS] Manage development methodology workflow |
 | `/metrics` | "[UDS] Track development metrics, code quality indicators and project health" |
 | `/migrate` | "[UDS] Guide code migration, framework upgrades and technology modernization" |
@@ -194,12 +184,12 @@
 | `/reverse-sdd` | [UDS] Reverse engineer code into SDD specification document |
 | `/reverse-tdd` | [UDS] Analyze BDD-TDD coverage gaps |
 | `/reverse` | [UDS] Reverse engineer code to Specs, BDD, or TDD coverage. |
-| `/review` | [UDS] Perform systematic code review with checklist |
 | `/runbook` | "[UDS] Guide runbook creation, maintenance, drills, and coverage reporting" |
 | `/scan` | "[UDS] Guide automated security scanning, dependency auditing and secret detection" |
 | `/sdd-retro` | [UDS] Create retroactive specs for untracked feat/fix commits |
 | `/sdd` | [UDS] Create or review specification documents for Spec-Driven Development |
 | `/security` | "[UDS] Guide security review and vulnerability assessment following OWASP standards" |
+| `/skill-builder` | [UDS] Identify repeated processes and build Skills with the right development depth. |
 | `/slo` | "[UDS] Guide SLI selection, SLO setting, and Error Budget management" |
 | `/tdd` | [UDS] Guide through Test-Driven Development workflow |
 | `/update` | [UDS] Update development standards to latest version |
@@ -217,7 +207,7 @@
 | `ai-instruction-standards` | Create and maintain AI instruction files (CLAUDE.md, AGENTS.md, .cursor/rules/, etc.) with proper structure. |
 | `api-design-assistant` | Guide API design following REST, GraphQL, and gRPC best practices. |
 | `atdd-assistant` | "[UDS] Guide through Acceptance Test-Driven Development workflow" |
-| `audit-assistant` | "[UDS] UDS Health & Feedback System \| UDS 健康檢查與回饋系統" |
+| `audit-assistant` | "[UDS] UDS Health & Feedback System" |
 | `bdd-assistant` | "[UDS] Guide through Behavior-Driven Development workflow" |
 | `brainstorm-assistant` | "[UDS] Structured AI-assisted brainstorming before spec creation" |
 | `changelog-guide` | "[UDS] Generate and maintain CHANGELOG.md entries" |
@@ -237,7 +227,8 @@
 | `error-code-guide` | Design consistent error codes following the PREFIX_CATEGORY_NUMBER format. |
 | `git-workflow-guide` | Guide Git branching strategies, branch naming, and merge operations. |
 | `incident-response-assistant` | Guide incident response, root cause analysis, and post-mortem documentation. |
-| `journey-test-assistant` | "[UDS] 從專案描述生成連貫使用者旅程測試計畫（TESTPLAN）與 E2E 骨架" |
+| `journey-test-assistant` | "[UDS] Generate coherent user journey test plans (TESTPLAN) and E2E skeletons from project description." |
+| `knowledge-graph` | "[UDS] Trace spec/decision/code impact chains via a knowledge graph (engine or Markdown fallback)" |
 | `logging-guide` | Implement structured logging with proper log levels and sensitive data handling. |
 | `metrics-dashboard-assistant` | "[UDS] Track development metrics, code quality indicators, and project health" |
 | `migration-assistant` | "[UDS] Guide code migration, framework upgrades, and technology modernization" |
@@ -252,7 +243,7 @@
 | `release-standards` | "[UDS] Guide release process and changelogs" |
 | `requirement-assistant` | "[UDS] Write user stories and requirements following INVEST criteria" |
 | `retrospective-assistant` | [UDS] Guide structured team retrospectives for Sprint and Release cycles. |
-| `reverse-engineer` | "[UDS] System archeology — reverse engineer code across Logic, Data, and Runtime dimensions" |
+| `reverse-engineer` | "[UDS] System archeology - reverse engineer code across Logic, Data, and Runtime dimensions" |
 | `runbook-assistant` | Guide runbook creation, maintenance, and drill exercises. |
 | `security-assistant` | Guide security review and vulnerability assessment following OWASP standards. |
 | `security-scan-assistant` | Guide automated security scanning, dependency auditing, and secret detection. |
@@ -295,9 +286,9 @@
 
 | Standard | 版本 | 说明 |
 |----------|---------|-------------|
-| `acceptance-criteria-traceability` | - |  |
+| `acceptance-criteria-traceability` | 1.1.0 |  |
 | `acceptance-test-driven-development` | 1.1.0 |  |
-| `accessibility-standards` | 1.0.0 | This standard defines comprehensive guidelines for creating accessible software  |
+| `accessibility-standards` | 1.1.0 | This standard defines comprehensive guidelines for creating accessible software  |
 | `adr-standards` | 1.0.0 | Architecture Decision Records capture the context, options, and rationale behind |
 | `adversarial-test` | - |  |
 | `agent-behavior-discipline` | 1.0.0 | This standard defines four behavioral disciplines for AI agents that elevate per |
@@ -306,100 +297,121 @@
 | `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.0.0 | This standard defines best practices for creating and maintaining AI instruction |
-| `ai-response-navigation` | 1.0.0 | This standard defines navigation behavior for AI responses: every substantive AI |
+| `ai-instruction-standards` | 1.1.0 | This standard defines best practices for creating and maintaining AI instruction |
+| `ai-response-navigation` | 1.1.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 |
 | `anti-sycophancy-prompting` | 1.0.0 | This standard defines techniques and rules for designing prompts that elicit gen |
-| `api-design-standards` | 1.0.0 | This standard defines comprehensive guidelines for designing, building, and main |
+| `api-design-standards` | 1.1.0 | This standard defines comprehensive guidelines for designing, building, and main |
+| `audit-trail` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
 | `behavior-driven-development` | 1.1.0 |  |
 | `behavior-snapshot` | - |  |
 | `branch-completion` | 1.0.0 | Define a standardized workflow for completing development branches, including pr |
-| `browser-compatibility-standards` | 1.0.0 | This standard defines supported browser and device matrices, testing automation  |
+| `browser-compatibility-standards` | 1.0.2 | This standard defines supported browser and device matrices, testing automation  |
 | `capability-declaration` | - |  |
 | `cd-deployment-strategies` | - |  |
 | `change-batching-standards` | - |  |
 | `changelog-standards` | 1.0.2 | This standard defines how to write and maintain a CHANGELOG.md file to communica |
 | `chaos-engineering-standards` | 1.0.0 |  |
 | `chaos-injection-tests` | - |  |
-| `checkin-standards` | 1.6.0 | This standard defines quality gates that MUST be passed before committing code t |
+| `checkin-standards` | 1.7.0 | This standard defines quality gates that MUST be passed before committing code t |
 | `circuit-breaker` | - |  |
-| `code-review-checklist` | 1.3.0 | This standard provides a comprehensive checklist for reviewing code changes, ens |
+| `code-review-checklist` | 1.4.0 | This standard provides a comprehensive checklist for reviewing code changes, ens |
 | `commit-message-guide` | 1.3.0 | Standardized commit messages improve code review efficiency, facilitate automate |
+| `container-image-standards` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
 | `container-security` | - |  |
 | `containerization-standards` | 1.0.0 |  |
 | `context-aware-loading` | 1.0.0 | This standard defines a protocol for AI tools to selectively load development st |
 | `contract-testing-standards` | 1.0.0 | Contract testing verifies that a provider (API server) and its consumers (client |
 | `cost-budget-test` | - |  |
-| `cross-flow-regression` | 1.0.0 | This standard defines cross-flow regression testing — verifying that changes to  |
+| `cross-flow-regression` | 1.0.1 | This standard defines cross-flow regression testing — verifying that changes to  |
+| `data-contract` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
 | `data-migration-testing` | - |  |
+| `data-pipeline` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
 | `database-standards` | 1.0.0 | This standard defines guidelines for database design, querying, migration, and o |
-| `deployment-standards` | 1.0.0 | This standard defines guidelines for safely deploying software to production, co |
-| `deprecation-standards` | 1.0.0 |  |
+| `deployment-standards` | 1.1.0 | This standard defines guidelines for safely deploying software to production, co |
+| `deprecation-standards` | 1.1.0 |  |
 | `design-document-standards` | 1.0.0 |  |
-| `developer-memory` | 1.0.0 | This standard defines a structured system for capturing, retrieving, and surfaci |
+| `developer-memory` | 1.1.1 | This standard defines a structured system for capturing, retrieving, and surfaci |
 | `disaster-recovery-drill` | - |  |
 | `documentation-lifecycle` | 1.0.0 | This standard defines **when** to update documentation, **when** to check it, an |
 | `documentation-structure` | 1.5.0 | This standard defines a consistent documentation structure for software projects |
 | `documentation-writing-standards` | 1.2.0 | This standard defines documentation requirements based on project types and prov |
 | `dual-phase-output` | - |  |
 | `environment-standards` | 1.0.0 |  |
-| `error-code-standards` | 1.2.0 |  |
+| `error-code-standards` | 1.2.1 |  |
 | `estimation-standards` | 1.0.0 |  |
 | `execution-history` | 1.0.0 |  |
 | `failure-source-taxonomy` | - |  |
+| `feature-discovery-standards` | 1.0.0 | **Status**: Active | **Updated**: 2026-05-13 |  |
 | `feature-flag-standards` | 1.0.0 |  |
 | `feature-manifest-standard` | - |  |
 | `flaky-test-management` | - |  |
-| `flow-based-testing` | 1.3.0 | This document defines a systematic methodology for testing multi-step processes. |
-| `forward-derivation-standards` | 1.2.0 | This standard defines the principles and workflows for Forward Derivation—automa |
+| `flow-based-testing` | 1.3.1 | This document defines a systematic methodology for testing multi-step processes. |
+| `forward-derivation-standards` | 1.3.0 | This standard defines the principles and workflows for Forward Derivation—automa |
 | `frontend-design-standards` | 1.0.0 | This standard defines a machine-readable frontend design specification format (D |
 | `full-coverage-testing` | - |  |
 | `git-workflow` | 1.4.0 | This standard defines Git branching strategies and workflows to ensure consisten |
-| `git-worktree` | 1.0.0 | Define a lifecycle for using Git worktrees to isolate development work, ensuring |
+| `git-worktree` | 1.1.0 | Define a lifecycle for using Git worktrees to isolate development work, ensuring |
 | `governance-layer` | 1.0.0 | A governance layer provides a shared anchor for all agents and roles in a projec |
 | `health-check-standards` | - |  |
+| `iac-design-principles` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
 | `immutability-first` | - |  |
+| `incident-response` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
+| `knowledge-graph-memory` | 1.0.0 | This standard defines a **relationship schema** so that specifications, decision |
 | `knowledge-transfer-standards` | 1.0.0 |  |
+| `license-compliance` | 2.1.0 | **Status**: Active | **Updated**: 2026-05-16 |  |
 | `llm-output-validation` | - |  |
-| `logging-standards` | 1.2.0 |  |
-| `mock-boundary` | 1.0.0 | This document defines rules for what can and cannot be mocked in tests. Its goal |
-| `model-selection` | 1.0.0 | Define a cost-effective strategy for selecting AI model tiers based on task comp |
+| `logging-standards` | 1.4.0 |  |
+| `mock-boundary` | 1.1.0 | This document defines rules for what can and cannot be mocked in tests. Its goal |
+| `model-provenance` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
+| `model-selection` | 1.0.1 | Define a cost-effective strategy for selecting AI model tiers based on task comp |
+| `multi-environment-e2e-testing` | 1.0.0 | **Status**: Active | **Updated**: 2026-05-13 |  |
 | `mutation-testing` | 1.0.0 | Mutation testing evaluates test suite effectiveness by injecting artificial bugs |
 | `no-cicd-deployment` | - |  |
 | `observability-standards` | 1.0.0 |  |
-| `packaging-standards` | 1.0.0 | This standard defines a Recipe-based packaging framework that enables user proje |
-| `performance-standards` | 1.1.0 | This standard defines comprehensive guidelines for software performance engineer |
+| `packaging-standards` | 1.1.0 | This standard defines a Recipe-based packaging framework that enables user proje |
+| `performance-standards` | 1.2.0 | This standard defines comprehensive guidelines for software performance engineer |
+| `pii-classification` | 1.1.0 | **Status**: Active | **Updated**: 2026-06-19 |  |
 | `pipeline-integration-standards` | - |  |
 | `pipeline-security-gates` | - |  |
 | `policy-as-code-testing` | - |  |
 | `postmortem-standards` | 1.0.0 |  |
-| `privacy-standards` | 1.0.0 |  |
-| `project-context-memory` | 1.1.0 | This standard defines a structured system for capturing, retrieving, and enforci |
+| `prd-standards` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
+| `privacy-standards` | 1.1.0 |  |
+| `product-metrics-standards` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
+| `project-context-memory` | 1.2.0 | This standard defines a structured system for capturing, retrieving, and enforci |
 | `project-structure` | 1.2.0 | This standard defines conventions for project directory structure beyond documen |
 | `prompt-regression` | - |  |
 | `property-based-testing` | - |  |
+| `push-standards` | 1.0.0 | **Status**: Active | **Updated**: 2026-04-23 |  |
 | `recovery-recipe-registry` | - |  |
-| `refactoring-standards` | 2.1.0 | This standard defines comprehensive guidelines for code refactoring, covering ev |
+| `refactoring-standards` | 2.2.0 | This standard defines comprehensive guidelines for code refactoring, covering ev |
 | `release-quality-manifest` | - |  |
 | `release-readiness-gate` | 1.0.0 | This standard defines a **single, aggregated Release Readiness Gate** that unifi |
 | `replay-test` | - |  |
 | `requirement-engineering` | 1.0.0 |  |
+| `resource-cost-boundary` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
 | `retrospective-standards` | 1.0.0 | Retrospectives are structured team reflections that identify what worked well, w |
 | `retry-standards` | - |  |
-| `reverse-engineering-standards` | 1.0.0 | This standard defines the principles, workflows, and best practices for reverse  |
+| `reverse-engineering-standards` | 1.2.0 | This standard defines the principles, workflows, and best practices for reverse  |
 | `rollback-standards` | - |  |
 | `runbook-standards` | 1.0.0 |  |
+| `runbook` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
 | `sast-advanced` | 1.0.0 | This standard defines Advanced Static Application Security Testing (SAST) practi |
+| `schema-evolution` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
+| `secret-management-standards` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
 | `secure-op` | - |  |
 | `security-decision` | - |  |
 | `security-standards` | 1.1.0 | This standard defines comprehensive security guidelines for software development |
-| `security-testing` | 1.0.0 | This document defines the security testing methodology for software projects. It |
+| `security-testing` | 1.1.0 | This document defines the security testing methodology for software projects. It |
+| `self-review-protocol` | 1.1.0 | This standard mandates a **self-review pass** on large markdown edits before com |
 | `server-ops-security` | - |  |
 | `skill-standard-alignment-check` | - |  |
+| `slo-sli` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
 | `slo-standards` | 1.0.0 |  |
 | `smoke-test` | - |  |
-| `spec-driven-development` | 2.2.0 |  |
+| `spec-driven-development` | 2.3.0 |  |
 | `standard-admission-criteria` | - |  |
 | `standard-lifecycle-management` | - |  |
 | `structured-task-definition` | 1.0.0 |  |
@@ -415,8 +427,11 @@
 | `timeout-standards` | - |  |
 | `token-budget` | - |  |
 | `translation-lifecycle-standards` | 1.0.0 | Translation lifecycle standards: MISSING vs OUTDATED distinction, semver-aware s |
+| `user-journey-testing` | - |  |
+| `user-story-mapping` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
 | `verification-evidence` | 1.0.0 | Establish an "Iron Law" that no task can be claimed as complete without verifica |
-| `versioning` | 1.2.0 | This standard defines how to version software releases using Semantic Versioning |
+| `verification-oracle` | 1.0.0 | **Status**: Active | **Updated**: 2026-06-17 |  |
+| `versioning` | 1.5.0 | This standard defines how to version software releases using Semantic Versioning |
 | `virtual-organization-standards` | 1.0.0 | This standard treats the AI ecosystem as a "Virtual Organization." It defines ho |
 | `workflow-enforcement` | - |  |
 | `workflow-state-protocol` | 1.0.0 |  |
@@ -468,10 +483,12 @@
 | `check-version-sync.ps1` | Check Version Sync |
 | `check-version-sync.sh` | Version Sync Checker |
 | `check-workflow-compliance.sh` | DEPRECATED: Use 'npx tsx scripts/check-workflow-compliance.ts' instead (cross-platform). |
+| `commitlint-bilingual-rule.mjs` | commitlint-bilingual-rule.mjs — custom commitlint rules enforcing the |
 | `convert-md-to-yaml.mjs` | Markdown to AI-YAML Conversion Script |
 | `fix-manifest-paths.ps1` | Fix Manifest Paths |
 | `fix-manifest-paths.sh` | Manifest Path Fixer |
 | `generate-docs.mjs` | Generate Docs |
+| `generate-locale-coverage.mjs` | Locale Coverage Generator |
 | `generate-version-manifest.mjs` | Generate Version Manifest (SPEC-SELFDIAG-001 REQ-9, AC-14) |
 | `install-hooks.mjs` | Install Hooks |
 | `install-hooks.sh` | DEPRECATED: Use 'node scripts/install-hooks.mjs' instead (cross-platform). |
@@ -480,6 +497,7 @@
 | `pre-release-check.sh` | Pre-release Check Script |
 | `pre-release.ps1` | Pre-Release Preparation Script for Universal Development Standards |
 | `pre-release.sh` | Pre-Release Preparation Script |
+| `setup-hooks.sh` | setup-hooks.sh — Install git hooks for UDS repo |
 | `setup-husky.mjs` | Cross-platform Husky Setup Script |
 | `sync-manifest.mjs` | Sync Manifest |
 

package/bundled/locales/zh-CN/docs/MIGRATION-v6.md

@@ -0,0 +1,88 @@
+# UDS 6.0.0 迁移指南
+
+> **语言**: [English](../../../docs/MIGRATION-v6.md) | [繁體中文](../../zh-TW/docs/MIGRATION-v6.md) | 简体中文
+
+UDS 6.0.0 是 **major** 版本：包含一项 breaking 更名、移除 8 个已弃用的机器可读标准与 4 个已弃用的 CLI 命令——以上皆自 5.4.0 起带有「6.0.0 移除」预告。本指南涵盖所有需要调整的事项。
+
+**TL;DR 检查清单：**
+
+- [ ] 把所有 `/review` 呼叫改为 `/code-review`
+- [ ] 若脚本用到 `uds start` / `uds mission*` / `uds workflow*` / `uds flow*` / `uds sweep`，依 §3 迁移
+- [ ] 若采用层曾载入 8 个被移除的 `.ai.yaml` stub，改用自家 runtime 等效实作（§2）
+- [ ] 升级：`npm install -g universal-dev-standards@6`，然后在各专案跑 `uds update`
+
+---
+
+## 1. Breaking 更名：`/review` → `/code-review`
+
+`review` 命令/skill 更名为 `code-review`，使 skill frontmatter 名称与其目录（`code-review-assistant`）对齐。
+
+| 更名前 | 更名后 |
+|--------|--------|
+| `/review` | `/code-review` |
+| `skills/commands/review.md` | `skills/commands/code-review.md` |
+| `.gemini/commands/review.toml` | `.gemini/commands/code-review.toml` |
+| `flows/review.flow.yaml`（flow-id `review-flow`）| `flows/code-review.flow.yaml`（flow-id `code-review-flow`）|
+
+**你需要做的：**
+
+- 把自家 prompt、文件、CI 脚本、AI 指令档（`CLAUDE.md`、`AGENTS.md`、`.cursor/rules/` 等）中的 `/review` 改为 `/code-review`。
+- 若你的 flow 引用了 flow-id `review-flow`（如 `workflow-prerequisites`），改为 `code-review-flow`。
+- 重跑 `uds update` 让重生成的命令索引落进专案。
+
+**不受影响**：指涉外部工具内建 review 命令（如 Codex）的 `/review` 字样与 UDS 无关，刻意保留原样。
+
+## 2. 移除：8 个已弃用的机器可读标准（`.ai.yaml`）
+
+这 8 个标准的 runtime 已于 5.4.0 移交采用层（XSPEC-086/095；UDS 定义活动、采用层编排流程——DEC-049），其 `.ai.yaml` stub 如期移除：
+
+| 移除的 `.ai.yaml` | 保留的人类可读文件 |
+|---|---|
+| `agent-communication-protocol` | `core/agent-communication-protocol.md` |
+| `agent-dispatch` | `core/agent-dispatch.md` |
+| `branch-completion` | `core/branch-completion.md` |
+| `change-batching-standards` | `core/change-batching-standards.md` |
+| `execution-history` | `core/execution-history.md` |
+| `pipeline-integration-standards` | `core/pipeline-integration-standards.md` |
+| `workflow-enforcement` | `core/workflow-enforcement.md` |
+| `workflow-state-protocol` | `core/workflow-state-protocol.md` |
+
+**你需要做的：**
+
+- 若从未直接载入这些 `.ai.yaml`：不需动作——人类可读概念仍留在 `core/` 作为参考文件。
+- 若采用层（agent runtime、orchestrator、CI）曾载入这些 stub：在自家工具链实作等效机制。这些 stub 自 5.4.0 起本身就是指向此方向的弃用告示。
+- 这些标准不再由 `uds init` / `uds update` 发布。专案 `.standards/` 中既有副本不会被自动删除——想要干净树的话请手动移除。
+
+## 3. 移除：4 个已弃用的 CLI 命令
+
+四者皆于 5.4.0 标记 `@deprecated`（XSPEC-095）并预告 6.0.0 移除。流程编排属采用层职责（DEC-049）。
+
+| 移除的命令 | 迁移路径 |
+|---|---|
+| `uds start`、`uds mission:*`（status/pause/resume/cancel/list）| 用采用层的 mission runtime（如 VibeOps orchestrator）|
+| `uds workflow:*`（list/install/info/execute/status）| workflow 定义在 `flows/`；执行归采用层 |
+| `uds flow:*`（create/list/validate/diff/export/import）| 直接撰写 flow YAML；验证/执行在采用层 |
+| `uds sweep` | 用 `/sweep` skill（同能力、skill 形式）|
+
+保留的命令：`init`、`update`、`check`、`audit`、`config`、`skills`、`release`、`hitl`、`run` 及其余非编排类 CLI。
+
+## 4. 已弃用但 6.0.0「未」移除
+
+- **6 个 workflow skills** 标记为 `reference` 级并带明显弃用告示（XSPEC-291 §4）。它们仍随版发布；可按自己的节奏迁移。
+- 其他已弃用 runtime 命令带结构化 `@superseded-by` 指标。
+
+## 5. 升级步骤
+
+```bash
+# 1. 升级 CLI
+npm install -g universal-dev-standards@6
+
+# 2. 在各消费专案
+uds update
+
+# 3. 扫自家设定的残留引用
+grep -rn "/review\b" . --include="*.md" --include="*.toml" | grep -v code-review
+grep -rn "uds start\|uds workflow\|uds flow\|uds sweep" . --exclude-dir=node_modules
+```
+
+`uds check` 通过且上述 grep 干净，即完成迁移。

package/bundled/locales/zh-CN/docs/USAGE-MODES-COMPARISON.md

@@ -103,7 +103,7 @@ status: current
 | 学习曲线 | 低 | 高 | 低 |
 
 **说明**：
-- Skills 提供 `/commit`、`/tdd`、`/review` 等命令进行互动引導
+- Skills 提供 `/commit`、`/tdd`、`/code-review` 等命令进行互动引導
 - 规范文件需要开发者主动阅读并应用
 - Skills 可自动偵测上下文（如 git status、项目语言）
 
@@ -177,7 +177,7 @@ status: current
 - Token 消耗最低
 - 互动体驗最佳
 - 無需管理額外文件
-- `/commit`、`/tdd`、`/review` 命令足夠日常使用
+- `/commit`、`/tdd`、`/code-review` 命令足夠日常使用
 
 **配置方式**：
 ```bash