universal-dev-standards 5.3.2 → 5.4.0

package/bundled/ai/standards/agent-communication-protocol.ai.yaml

@@ -1,177 +1,43 @@
-# Agent Communication Protocol - AI Optimized
-# Source: core/agent-communication-protocol.md
-# Spec: docs/specs/SPEC-AGENT-COMM-001-agent-communication-protocol.md
+# Agent Communication Protocol - DEPRECATED STUB
+# This file has been migrated to DevAP per DEC-049 (UDS/DevAP responsibility split).
+# Canonical location: dev-autopilot/standards/orchestration/agent-communication-protocol.ai.yaml
+# Migration: XSPEC-086 Phase 2 (2026-04-27)
+#
+# Human-readable standard: core/agent-communication-protocol.md (remains in UDS)
+# Deprecation schedule: UDS 5.4.0 deprecated → UDS 6.0.0 removed
 
 standard:
   id: agent-communication
-  name: Agent Communication Protocol
-  description: 跨專案 Agent 統一通訊協定
-
   meta:
-    version: "1.0.0"
-    updated: "2026-03-30"
+    version: "1.0.1"
+    updated: "2026-04-27"
+    deprecated: true
+    deprecated_since: "5.4.0"
+    removal_version: "6.0.0"
+    canonical_owner: devap
+    canonical_path: "dev-autopilot/standards/orchestration/agent-communication-protocol.ai.yaml"
     source: core/agent-communication-protocol.md
-    description: 統一狀態碼、訊息信封、結構化交接與協定版本管理
-    scope: universal
-
-  guidelines:
-    - "Agent 間通訊必須使用 Envelope 格式，禁止 prompt injection"
-    - "狀態碼必須使用統一 8 碼超集：success / success_partial / failed / blocked / needs_context / skipped / timeout / unknown"
-    - "上下文傳遞必須使用 Handoff 物件，引用 artifact_id 而非嵌入完整內容"
-    - "未知狀態碼映射為 unknown，記錄警告，不中斷執行"
-    - "同 MAJOR 版本保證向後相容，不同 MAJOR 回報 VERSION_INCOMPATIBLE"
-
-  status_protocol:
-    - unified: success
-      uds: DONE
-      devap: success
-      vibeops: success
-    - unified: success_partial
-      uds: DONE_WITH_CONCERNS
-      devap: done_with_concerns
-      vibeops: partial
-    - unified: failed
-      uds: null
-      devap: failed
-      vibeops: failure
-    - unified: blocked
-      uds: BLOCKED
-      devap: blocked
-      vibeops: null
-    - unified: needs_context
-      uds: NEEDS_CONTEXT
-      devap: needs_context
-      vibeops: null
-    - unified: skipped
-      uds: null
-      devap: skipped
-      vibeops: null
-    - unified: timeout
-      uds: null
-      devap: timeout
-      vibeops: null
-    - unified: unknown
-      uds: null
-      devap: null
-      vibeops: null
-
-  envelope:
-    version: "1.0"
-    required_fields:
-      - field: envelope_version
-        type: string
-        description: "協定版本（MAJOR.MINOR）"
-      - field: message_id
-        type: uuid
-        description: "訊息唯一 ID"
-      - field: source
-        type: object
-        description: "發送者 { agent_id, agent_type, project }"
-      - field: target
-        type: object
-        description: "接收者 { agent_id?, agent_type }（broadcast 時可省略）"
-      - field: status
-        type: string
-        description: "統一狀態碼"
-      - field: timestamp
-        type: iso8601
-        description: "訊息建立時間"
-      - field: payload.artifact_type
-        type: string
-        enum: [spec, code, test, review, plan, design]
-      - field: payload.artifact_id
-        type: string
-        description: "Artifact 唯一 ID"
-    optional_fields:
-      - field: correlation_id
-        description: "關聯 ID（同一任務鏈）"
-      - field: parent_message_id
-        description: "父訊息 ID（回應時填寫）"
-      - field: metadata
-        description: "擴展元資料（model_tier, token_usage, duration_ms）"
-      - field: concerns
-        description: "success_partial 時的疑慮列表"
-
-  handoff:
-    required_fields:
-      - field: from
-        description: "發送者 { agent_id, agent_type, message_id }"
-      - field: to
-        description: "接收者 { agent_type }"
-      - field: artifacts
-        description: "Artifact 引用陣列 [{ artifact_id, artifact_type, summary }]"
-    optional_fields:
-      - field: decision_log
-        description: "決策記錄 [{ decision, reason, agent_id, timestamp }]"
-      - field: pending_items
-        description: "待處理事項 [{ item, priority, context? }]"
-      - field: constraints
-        description: "約束條件 [string]"
-
-  hook_exit_codes:
     description: >
-      Hook 退出碼三分類（借鑑 lintsinghua/claude-code-book Ch.7 Hooks 協議）。
-      適用於所有 DevAP/VibeOps 生成的 Claude Code hook shell 腳本。
-    codes:
-      - code: 0
-        name: pass
-        description: "Hook 通過，工具/Agent 執行繼續"
-        blocking: false
-        stdout_handling: "忽略"
-        stderr_handling: "忽略"
-      - code: 2
-        name: block
-        description: "阻止執行；stderr 輸出作為回饋文字直接注入 AI 上下文"
-        blocking: true
-        stdout_handling: "忽略"
-        stderr_handling: "作為 AI feedback 注入（支援 JSON 格式 decision:block/reason）"
-        note: "PreToolUse exit 2 → 阻止工具呼叫；Stop exit 2 → 中止 session"
-      - code: other
-        name: warn
-        description: "非阻擋性警告；記錄日誌但執行繼續（exit 1 為常用警告代碼）"
-        blocking: false
-        stdout_handling: "記錄到系統日誌"
-        stderr_handling: "顯示為 warning，不注入 AI 上下文"
-    rules:
-      - "MUST: 阻擋行為只能用 exit 2，不得用 exit 1 或其他非零代碼"
-      - "MUST: exit 2 時 stderr 必須是人類可讀的原因（推薦 JSON: {reason: string}）"
-      - "SHOULD: 軟性警告（deprecated pattern、style 違反）使用 exit 1"
-      - "MAY: exit 0 時可輸出 JSON 到 stdout（Stop hook 用 decision:block 要求 AI 繼續）"
+      DEPRECATED: This standard has moved to DevAP (orchestration layer).
+      Install DevAP and load standards/orchestration/agent-communication-protocol.ai.yaml instead.
 
   rules:
+    - id: deprecation-notice
+      trigger: any agent communication operation
+      instruction: >
+        This standard (agent-communication-protocol.ai.yaml) has been migrated to DevAP.
+        For the canonical executable definition, load:
+          dev-autopilot/standards/orchestration/agent-communication-protocol.ai.yaml
+
+        The human-readable standard remains at:
+          universal-dev-standards/core/agent-communication-protocol.md
+      priority: required
+
     - id: ACP-001
       trigger: "訊息缺少必要欄位"
-      action: "拒絕並回報 INVALID_ENVELOPE，指出缺少的欄位"
-      priority: critical
-    - id: ACP-002
-      trigger: "收到未知狀態碼"
-      action: "映射為 unknown，記錄警告，繼續執行"
-      priority: high
-    - id: ACP-003
-      trigger: "收到不同 MAJOR 版本的訊息"
-      action: "回報 VERSION_INCOMPATIBLE，附帶支援的版本範圍"
-      priority: high
-    - id: ACP-004
-      trigger: "收到同 MAJOR 更高 MINOR 版本的訊息"
-      action: "解析已知欄位，忽略未知欄位，不報錯"
-      priority: medium
-    - id: ACP-005
-      trigger: "建立 Handoff"
-      action: "引用 artifact_id，不嵌入完整內容"
-      priority: medium
-    - id: ACP-006
-      trigger: "生成 hook 腳本"
-      action: "依照 hook_exit_codes 三分類：0=pass, 2=block+feedback, 其他=warn"
-      priority: high
+      instruction: >
+        DEPRECATED — load dev-autopilot/standards/orchestration/agent-communication-protocol.ai.yaml
+        for the current executable communication protocol.
 
-physical_spec:
-  type: checklist
-  validator:
-    type: ai_review
-    rule: "檢查 Agent 通訊是否遵循 Envelope 格式、統一狀態碼、Handoff 結構"
-  checks:
-    - "訊息是否使用 Envelope 格式（非 prompt injection）"
-    - "狀態碼是否為 8 碼超集之一"
-    - "Handoff 是否引用 artifact_id 而非嵌入內容"
-    - "decision_log 每筆是否包含 decision, reason, agent_id, timestamp"
-    - "版本不相容時是否回報 VERSION_INCOMPATIBLE"
+        Minimal fallback: Reject messages missing required Envelope fields and report INVALID_ENVELOPE.
+      priority: critical

package/bundled/ai/standards/agent-dispatch.ai.yaml

@@ -1,69 +1,43 @@
-# Agent Dispatch & Parallel Coordination - AI Optimized
-# Source: core/agent-dispatch.md
-# Inspired by Superpowers dispatching-parallel-agents + subagent-driven-development (MIT)
+# Agent Dispatch & Parallel Coordination - DEPRECATED STUB
+# This file has been migrated to DevAP per DEC-049 (UDS/DevAP responsibility split).
+# Canonical location: dev-autopilot/standards/orchestration/agent-dispatch.ai.yaml
+# Migration: XSPEC-086 Phase 2 (2026-04-27)
+#
+# Human-readable standard: core/agent-dispatch.md (remains in UDS)
+# Deprecation schedule: UDS 5.4.0 deprecated → UDS 6.0.0 removed
 
 standard:
   id: agent-dispatch
-  name: Agent Dispatch & Parallel Coordination
-  description: 子代理派遣與並行協調標準
-
   meta:
-    version: "1.0.0"
-    updated: "2026-03-20"
+    version: "1.0.1"
+    updated: "2026-04-27"
+    deprecated: true
+    deprecated_since: "5.4.0"
+    removal_version: "6.0.0"
+    canonical_owner: devap
+    canonical_path: "dev-autopilot/standards/orchestration/agent-dispatch.ai.yaml"
     source: core/agent-dispatch.md
-    description: 子代理派遣、並行協調與狀態回報標準
-    inspired_by: superpowers/subagent-driven-development
-
-  guidelines:
-    - "派遣前必須識別獨立域（無共享狀態 → 可並行）"
-    - "每個代理的 prompt 必須 Focused（單一問題域）、Self-contained（完整上下文）、Specific output（明確回報格式）"
-    - "代理必須回報明確狀態：DONE / DONE_WITH_CONCERNS / NEEDS_CONTEXT / BLOCKED"
-    - "並行代理返回後必須檢查檔案衝突"
-    - "所有代理完成後必須跑完整測試套件驗證整合"
+    description: >
+      DEPRECATED: This standard has moved to DevAP (orchestration layer).
+      Install DevAP and load standards/orchestration/agent-dispatch.ai.yaml instead.
 
-  status_protocol:
-    - status: DONE
-      description: "任務完成，無問題"
-      orchestrator_action: "繼續後續任務"
-    - status: DONE_WITH_CONCERNS
-      description: "任務完成，但有疑慮需記錄"
-      orchestrator_action: "記錄 concerns 到報告，繼續後續任務"
-    - status: NEEDS_CONTEXT
-      description: "需要更多上下文才能完成"
-      orchestrator_action: "注入額外 context，重新派遣（不計為 retry）"
-    - status: BLOCKED
-      description: "無法完成，需要人工介入或升級處理"
-      orchestrator_action: "嘗試升級模型或拆分任務"
+  rules:
+    - id: deprecation-notice
+      trigger: any agent dispatch operation
+      instruction: >
+        This standard (agent-dispatch.ai.yaml) has been migrated to DevAP.
+        For the canonical executable definition, load:
+          dev-autopilot/standards/orchestration/agent-dispatch.ai.yaml
 
-  prompt_structure:
-    - principle: Focused
-      description: "每個代理只處理單一問題域"
-    - principle: Self-contained
-      description: "prompt 包含完整執行所需的上下文"
-    - principle: Specific_output
-      description: "明確定義期望的回報格式"
+        The human-readable standard remains at:
+          universal-dev-standards/core/agent-dispatch.md
+      priority: required
 
-  rules:
-    - id: AD-001
-      trigger: "多個代理編輯相同檔案"
-      action: "標記衝突，需要人工或自動合併"
-      priority: critical
-    - id: AD-002
-      trigger: "代理回報 BLOCKED"
-      action: "嘗試升級模型等級再試一次"
-      priority: high
     - id: AD-003
       trigger: "所有並行代理完成"
-      action: "跑完整測試套件驗證整合"
-      priority: high
+      instruction: >
+        DEPRECATED — load dev-autopilot/standards/orchestration/agent-dispatch.ai.yaml
+        for the current executable dispatch protocol.
 
-physical_spec:
-  type: checklist
-  validator:
-    type: ai_review
-    rule: "檢查代理派遣是否遵循獨立域識別、prompt 三原則、狀態協定"
-  checks:
-    - "並行代理是否在獨立域上工作（無共享檔案）"
-    - "代理 prompt 是否包含完整上下文"
-    - "代理是否回報標準化狀態碼"
-    - "並行完成後是否執行整合測試"
+        Minimal fallback: Run full test suite after all parallel agents complete.
+      priority: high

package/bundled/ai/standards/branch-completion.ai.yaml

@@ -1,82 +1,46 @@
-# Branch Completion Workflow - AI Optimized
-# Source: core/branch-completion.md
-# Inspired by Superpowers finishing-a-development-branch (MIT)
+# Branch Completion Workflow - DEPRECATED STUB
+# This file has been migrated to DevAP per DEC-049 (UDS/DevAP responsibility split).
+# Canonical location: dev-autopilot/standards/flow/branch-completion.ai.yaml
+# Migration: XSPEC-086 Phase 2 (2026-04-27)
+#
+# Human-readable standard: core/branch-completion.md (remains in UDS)
+# Deprecation schedule: UDS 5.4.0 deprecated → UDS 6.0.0 removed
 
 standard:
   id: branch-completion
-  name: Branch Completion Workflow
-  description: 分支完成工作流標準
-
   meta:
-    version: "1.0.0"
-    updated: "2026-03-20"
+    version: "1.0.1"
+    updated: "2026-04-27"
+    deprecated: true
+    deprecated_since: "5.4.0"
+    removal_version: "6.0.0"
+    canonical_owner: devap
+    canonical_path: "dev-autopilot/standards/flow/branch-completion.ai.yaml"
     source: core/branch-completion.md
-    description: 分支完成決策與清理標準
-    inspired_by: superpowers/finishing-a-development-branch
+    description: >
+      DEPRECATED: This standard has moved to DevAP (flow orchestration layer).
+      Install DevAP and load standards/flow/branch-completion.ai.yaml instead.
 
-  guidelines:
-    - "測試全過才能談完成"
-    - "提供 4 個完成選項讓使用者選擇"
-    - "Discard 需要明確確認，防止誤刪"
-    - "Worktree 對應分支完成後必須清理"
+  rules:
+    - id: deprecation-notice
+      trigger: any branch completion operation
+      instruction: >
+        This standard (branch-completion.ai.yaml) has been migrated to DevAP.
+        For the canonical executable definition, load:
+          dev-autopilot/standards/flow/branch-completion.ai.yaml
 
-  prerequisites:
-    - "所有測試通過"
-    - "lint 通過"
-    - "type check 通過"
-    - "無未提交的變更"
+        The human-readable standard remains at:
+          universal-dev-standards/core/branch-completion.md
 
-  options:
-    - id: merge_locally
-      description: "合併到目標分支"
-      steps:
-        - "git checkout <target>"
-        - "git merge --no-ff <branch>"
-        - "刪除分支"
-        - "清理 worktree（若有）"
-    - id: create_pr
-      description: "建立 Pull Request"
-      steps:
-        - "推送分支到 remote"
-        - "建立 PR（含描述與測試計畫）"
-        - "等待審查"
-    - id: keep_as_is
-      description: "保持現狀不動"
-      steps:
-        - "記錄分支狀態"
-        - "提醒使用者稍後處理"
-    - id: discard
-      description: "丟棄所有變更"
-      steps:
-        - "要求使用者明確確認（輸入分支名稱）"
-        - "刪除分支（git branch -D）"
-        - "清理 worktree（若有）"
+        To install DevAP: npm install -g @devap/cli
+      priority: required
 
-  rules:
-    - id: BC-001
-      trigger: "使用者選擇 discard"
-      action: "要求輸入分支名稱確認，防止誤刪"
-      priority: critical
-    - id: BC-002
-      trigger: "分支有 worktree"
-      action: "完成後自動清理 worktree"
-      priority: high
     - id: BC-003
       trigger: "前置條件未滿足"
-      action: "阻止完成，顯示失敗的檢查項目"
-      priority: high
-    - id: BC-004
-      trigger: "分支閒置超過 14 天"
-      action: "通知使用者完成或丟棄"
-      priority: medium
+      instruction: >
+        DEPRECATED — load dev-autopilot/standards/flow/branch-completion.ai.yaml
+        for the current executable branch completion flow.
 
-physical_spec:
-  type: checklist
-  validator:
-    type: ai_review
-    rule: "檢查分支完成是否遵循前置條件檢查和四選項流程"
-  checks:
-    - "完成前是否通過所有前置條件（測試、lint、type check）"
-    - "是否提供完成選項供使用者選擇"
-    - "Discard 操作是否要求明確確認"
-    - "關聯的 worktree 是否被清理"
+        Minimal fallback: Block branch completion when prerequisites (tests, lint,
+        type check, no uncommitted changes) are not met.
+      priority: high

package/bundled/ai/standards/change-batching-standards.ai.yaml

@@ -1,195 +1,46 @@
-# Change Batching Standards - AI Optimized
-# Source: core/change-batching-standards.md
+# Change Batching Standards - DEPRECATED STUB
+# This file has been migrated to DevAP per DEC-049 (UDS/DevAP responsibility split).
+# Canonical location: dev-autopilot/standards/flow/change-batching-standards.ai.yaml
+# Migration: XSPEC-086 Phase 2 (2026-04-27)
+#
+# Human-readable standard: core/change-batching-standards.md (remains in UDS)
+# Deprecation schedule: UDS 5.4.0 deprecated → UDS 6.0.0 removed
 
 standard:
   id: change-batching-standards
-  name: Change Batching Standards
-  description: Pending changes state machine, threshold strategies, and atomicity guarantees for batch commits
-
   meta:
-    version: "1.0.0"
-    updated: "2026-03-18"
+    version: "1.0.1"
+    updated: "2026-04-27"
+    deprecated: true
+    deprecated_since: "5.4.0"
+    removal_version: "6.0.0"
+    canonical_owner: devap
+    canonical_path: "dev-autopilot/standards/flow/change-batching-standards.ai.yaml"
     source: core/change-batching-standards.md
-    references:
-      - "SWEBOK v4.0 Chapter 6 (Software Configuration Management)"
-      - "ISO/IEC 12207 (Configuration Management Process)"
-      - "Continuous Delivery (Jez Humble) — Small batch sizes"
-      - "Lean Software Development — Batch size optimization"
-
-  state_machine:
-    description: Pending changes lifecycle
-    states:
-      - state: PENDING
-        description: Change recorded, waiting for threshold
-      - state: READY
-        description: Threshold met, batch prepared for merge
-      - state: MERGED
-        description: Batch successfully committed
-      - state: FAILED
-        description: Merge attempt failed
-      - state: ARCHIVED
-        description: Post-commit record for audit
-
-    transitions:
-      - from: PENDING
-        to: PENDING
-        trigger: New change added
-        action: Increment counters, re-evaluate thresholds
-      - from: PENDING
-        to: READY
-        trigger: Threshold met
-        action: Prepare merge batch, run pre-merge validation
-      - from: READY
-        to: MERGED
-        trigger: Merge succeeds
-        action: Create commit, clear batch, archive
-      - from: READY
-        to: FAILED
-        trigger: Merge fails
-        action: Log failure, preserve changes
-      - from: FAILED
-        to: PENDING
-        trigger: Reset
-        action: Re-queue changes, clear failure state
-      - from: MERGED
-        to: ARCHIVED
-        trigger: Post-commit
-        action: Record batch metadata for audit
-
-  threshold_strategies:
-    strategies:
-      - name: count
-        parameter: maxChanges
-        default: 5
-        description: Merge after N individual changes accumulated
-
-      - name: score
-        parameter: maxScore
-        default: 10
-        description: Merge when cumulative change score >= M
-
-      - name: time
-        parameter: maxAge
-        default: "30m"
-        description: Merge when oldest pending change exceeds TTL
-
-      - name: manual
-        parameter: null
-        default: null
-        description: Merge only on explicit user request
-
-    change_scoring:
-      - type: trivial
-        score: 1
-        example: Typo fix, whitespace, comment update
-      - type: minor
-        score: 2
-        example: Single function change, variable rename
-      - type: standard
-        score: 3
-        example: New function, modified logic flow
-      - type: complex
-        score: 5
-        example: Multi-file change, API modification
-      - type: critical
-        score: 8
-        example: Schema change, breaking change
-
-    composite_rule: "Multiple thresholds combine with OR logic (first met triggers merge)"
-
-  merge_rules:
-    priority_order:
-      - Same-spec affinity — changes referencing same SPEC-ID merge first
-      - Same-file grouping — changes to same files merge together
-      - Dependency order — changes with dependencies merge in order
-      - Chronological — within same priority, merge by creation time
-
-    conflict_resolution:
-      - type: Same line, same file
-        strategy: Latest change wins
-        fallback: Manual resolution
-      - type: Overlapping functions
-        strategy: Semantic merge if possible
-        fallback: Manual resolution
-      - type: Dependency conflict
-        strategy: Resolve dependency first
-        fallback: Reject batch, split
-
-    pre_merge_validation:
-      - check: All tests pass
-        required: true
-      - check: No lint errors
-        required: true
-      - check: No conflicts
-        required: true
-      - check: AC coverage maintained
-        required: false
-        note: Recommended
-
-  atomicity:
-    principle: All-or-nothing
-    rules:
-      - Single commit — each merged batch produces exactly one commit
-      - No partial merge — any change failure rejects entire batch
-      - Rollback support — failed merges restore all changes to PENDING
-      - Isolation — batch merge does not affect changes outside batch
-
-  rollback:
-    on_failure:
-      - Log failure with batch details
-      - Return all changes to PENDING state
-      - Diagnose failing change(s)
-      - Options — fix and retry, remove failing change, split batch
-
-    triggers:
-      - trigger: Test failure
-        action: Reject entire batch
-        automatic: true
-      - trigger: Lint error
-        action: Reject entire batch
-        automatic: true
-      - trigger: Merge conflict
-        action: Reject and notify
-        automatic: true
-      - trigger: Build failure
-        action: Reject entire batch
-        automatic: true
-      - trigger: Manual rejection
-        action: Return to PENDING
-        automatic: false
+    description: >
+      DEPRECATED: This standard has moved to DevAP (flow orchestration layer).
+      Install DevAP and load standards/flow/change-batching-standards.ai.yaml instead.
 
   rules:
-    - id: set-thresholds
-      trigger: configuring batch pipeline
-      instruction: Set explicit thresholds; do not accumulate changes indefinitely
-      priority: required
+    - id: deprecation-notice
+      trigger: any batch change operation
+      instruction: >
+        This standard (change-batching-standards.ai.yaml) has been migrated to DevAP.
+        For the canonical executable definition, load:
+          dev-autopilot/standards/flow/change-batching-standards.ai.yaml
 
-    - id: group-by-spec
-      trigger: batching changes
-      instruction: Group changes by specification or feature for cohesive commits
-      priority: recommended
+        The human-readable standard remains at:
+          universal-dev-standards/core/change-batching-standards.md
 
-    - id: validate-before-merge
-      trigger: batch reaches READY state
-      instruction: Run full validation (tests, lint, conflicts) before merging
+        To install DevAP: npm install -g @devap/cli
       priority: required
 
     - id: atomic-commits
       trigger: merging a batch
-      instruction: Enforce all-or-nothing — either all changes commit or none do
-      priority: required
+      instruction: >
+        DEPRECATED — load dev-autopilot/standards/flow/change-batching-standards.ai.yaml
+        for the current executable batch orchestration rules.
 
-    - id: preserve-on-failure
-      trigger: batch merge fails
-      instruction: Return all changes to PENDING state; never lose changes
+        Minimal fallback: Enforce all-or-nothing batch merging — either all changes
+        commit or none do.
       priority: required
-
-    - id: log-batch-decisions
-      trigger: any batch state transition
-      instruction: Log batch decisions (threshold met, merge result) for auditability
-      priority: recommended
-
-related_standards:
-  - checkin-standards.md
-  - pipeline-integration-standards.md
-  - commit-message-guide.md