universal-dev-standards 5.5.0 → 5.7.0

package/bundled/ai/options/testing/integration-testing.ai.yaml

@@ -17,7 +17,7 @@ characteristics:
   scope: Multiple components working together
   speed: "<1 second per test"
   isolation: Partial (may use real dependencies)
-  pyramid_percentage: 20%
+  coverage_policy: "Behavior-completeness ratchet (XSPEC-178) — no fixed % floor. See full-coverage-testing.ai.yaml."
 
 rules:
   - id: test-integration-points
@@ -86,4 +86,4 @@ tools:
     - MockServer
     - nock (Node.js)
 
-coverage_target: "Critical paths and integration points"
+coverage_target: "All critical paths AND integration points — not just happy path. Ratchet CI enforced. (XSPEC-178)"

package/bundled/ai/options/testing/unit-testing.ai.yaml

@@ -11,7 +11,7 @@ characteristics:
   scope: Single function or method
   speed: "<100ms per test"
   isolation: Complete (no external dependencies)
-  pyramid_percentage: 70%
+  coverage_policy: "Behavior-completeness ratchet (XSPEC-178) — no fixed % floor. See full-coverage-testing.ai.yaml."
 
 rules:
   - id: test-one-thing
@@ -71,7 +71,7 @@ when_not_to_write:
   - Testing trivial getters/setters
   - Testing third-party libraries
 
-coverage_target: "80% of business logic"
+coverage_target: "Behavior-completeness: happy/edge/error path per public function. Ratchet CI — coverage can only increase. (XSPEC-178 — deprecated fixed 80% threshold)"
 
 tools:
   javascript: [Jest, Vitest, Mocha]

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

@@ -1,6 +1,6 @@
 # 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
+# Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+# Adoption layer must implement an equivalent runtime; UDS retains only the human-readable concept under core/.
 # Migration: XSPEC-086 Phase 2 (2026-04-27)
 #
 # Human-readable standard: core/agent-communication-protocol.md (remains in UDS)
@@ -14,20 +14,19 @@ standard:
     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"
+    canonical_owner: adoption-layer
+    canonical_path: "" # adoption-layer responsibility
     source: core/agent-communication-protocol.md
     description: >
-      DEPRECATED: This standard has moved to DevAP (orchestration layer).
-      Install DevAP and load standards/orchestration/agent-communication-protocol.ai.yaml instead.
+      DEPRECATED: Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+      Adoption layer must implement an equivalent runtime.
 
   rules:
     - id: deprecation-notice
       trigger: any agent communication operation
       instruction: >
-        This standard (agent-communication-protocol.ai.yaml) has been migrated to DevAP.
+        Runtime details for this standard are now adoption-layer responsibility (runtime moved to adoption layer 2026-04-28).
         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
@@ -36,7 +35,7 @@ standard:
     - id: ACP-001
       trigger: "訊息缺少必要欄位"
       instruction: >
-        DEPRECATED — load dev-autopilot/standards/orchestration/agent-communication-protocol.ai.yaml
+        DEPRECATED — see universal-dev-standards/core/ for human-readable concept; runtime is adoption-layer responsibility
         for the current executable communication protocol.
 
         Minimal fallback: Reject messages missing required Envelope fields and report INVALID_ENVELOPE.

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

@@ -1,6 +1,6 @@
 # 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
+# Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+# Adoption layer must implement an equivalent runtime; UDS retains only the human-readable concept under core/.
 # Migration: XSPEC-086 Phase 2 (2026-04-27)
 #
 # Human-readable standard: core/agent-dispatch.md (remains in UDS)
@@ -14,20 +14,19 @@ standard:
     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"
+    canonical_owner: adoption-layer
+    canonical_path: "" # adoption-layer responsibility
     source: core/agent-dispatch.md
     description: >
-      DEPRECATED: This standard has moved to DevAP (orchestration layer).
-      Install DevAP and load standards/orchestration/agent-dispatch.ai.yaml instead.
+      DEPRECATED: Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+      Adoption layer must implement an equivalent runtime.
 
   rules:
     - id: deprecation-notice
       trigger: any agent dispatch operation
       instruction: >
-        This standard (agent-dispatch.ai.yaml) has been migrated to DevAP.
+        Runtime details for this standard are now adoption-layer responsibility (runtime moved to adoption layer 2026-04-28).
         For the canonical executable definition, load:
-          dev-autopilot/standards/orchestration/agent-dispatch.ai.yaml
 
         The human-readable standard remains at:
           universal-dev-standards/core/agent-dispatch.md
@@ -36,7 +35,7 @@ standard:
     - id: AD-003
       trigger: "所有並行代理完成"
       instruction: >
-        DEPRECATED — load dev-autopilot/standards/orchestration/agent-dispatch.ai.yaml
+        DEPRECATED — see universal-dev-standards/core/ for human-readable concept; runtime is adoption-layer responsibility
         for the current executable dispatch protocol.
 
         Minimal fallback: Run full test suite after all parallel agents complete.

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

@@ -1,6 +1,6 @@
 # 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
+# Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+# Adoption layer must implement an equivalent runtime; UDS retains only the human-readable concept under core/.
 # Migration: XSPEC-086 Phase 2 (2026-04-27)
 #
 # Human-readable standard: core/branch-completion.md (remains in UDS)
@@ -14,31 +14,29 @@ standard:
     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"
+    canonical_owner: adoption-layer
+    canonical_path: "" # adoption-layer responsibility
     source: core/branch-completion.md
     description: >
-      DEPRECATED: This standard has moved to DevAP (flow orchestration layer).
-      Install DevAP and load standards/flow/branch-completion.ai.yaml instead.
+      DEPRECATED: Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+      Adoption layer must implement an equivalent runtime.
 
   rules:
     - id: deprecation-notice
       trigger: any branch completion operation
       instruction: >
-        This standard (branch-completion.ai.yaml) has been migrated to DevAP.
+        Runtime details for this standard are now adoption-layer responsibility (runtime moved to adoption layer 2026-04-28).
         For the canonical executable definition, load:
-          dev-autopilot/standards/flow/branch-completion.ai.yaml
 
         The human-readable standard remains at:
           universal-dev-standards/core/branch-completion.md
 
-        To install DevAP: npm install -g @devap/cli
       priority: required
 
     - id: BC-003
       trigger: "前置條件未滿足"
       instruction: >
-        DEPRECATED — load dev-autopilot/standards/flow/branch-completion.ai.yaml
+        DEPRECATED — see universal-dev-standards/core/ for human-readable concept; runtime is adoption-layer responsibility
         for the current executable branch completion flow.
 
         Minimal fallback: Block branch completion when prerequisites (tests, lint,

package/bundled/ai/standards/browser-compatibility-standards.ai.yaml

@@ -0,0 +1,63 @@
+# Browser Compatibility Standards - AI Optimized
+# Source: core/browser-compatibility-standards.md
+
+id: browser-compatibility-standards
+meta:
+  version: "1.0.0"
+  updated: "2026-05-05"
+  source: core/browser-compatibility-standards.md
+  description: Browser/device support matrix, Playwright automation, and release gate for frontend projects; N/A for CLI/backend
+
+requirements:
+  REQ-1:
+    id: REQ-BC-001
+    title: Explicit Support Matrix
+    rule: >
+      Frontend projects MUST declare an explicit browser support matrix in
+      .browserslistrc and in Playwright project config. At minimum define Tier-1
+      (full support, release blocking) and Tier-2 (partial, WARN) browsers.
+      Tier-1 default: Chrome/Firefox/Safari/Edge latest + latest-1; iOS Safari
+      latest + latest-1; Android Chrome latest.
+    rationale: >
+      Implicit "supports all browsers" is untestable; an explicit matrix defines
+      scope for both engineering and QA.
+
+  REQ-2:
+    id: REQ-BC-002
+    title: Viewport Coverage
+    rule: >
+      Automated tests MUST cover at minimum three viewport widths: 360px (mobile),
+      768px (tablet), 1280px (desktop). No critical flow must be broken at any
+      Tier-1 browser × viewport combination.
+    rationale: >
+      Missing mobile viewport tests produce broken UX for the majority of
+      mobile users who represent 50%+ of web traffic globally.
+
+  REQ-3:
+    id: REQ-BC-003
+    title: Real iOS Device Testing
+    rule: >
+      For release candidates, Safari must be tested on real iOS devices (not
+      simulators only). WebKit on iOS Simulator diverges from real device WebKit
+      in rendering and API behaviour.
+    rationale: >
+      Simulator-only iOS testing misses a significant class of WebKit rendering
+      bugs that only manifest on real hardware.
+
+  REQ-4:
+    id: REQ-BC-004
+    title: Release Gate
+    rule: >
+      Tier-1 browser matrix pass rate MUST be 100% (no test failure = release block).
+      Tier-2 must be ≥ 95% (WARN if below). This is Dimension 9 (Tier-3) in
+      release-readiness-gate.md. Mark N/A for CLI, backend API, and mobile native projects.
+    rationale: >
+      100% Tier-1 requirement is appropriate because unsupported behavior in
+      a declared Tier-1 browser is a support commitment violation.
+
+quick_reference:
+  tier1_default: "Chrome, Firefox, Safari, Edge (latest + latest-1); iOS Safari; Android Chrome latest"
+  viewport_minimum: "360px, 768px, 1280px"
+  automation: "Playwright matrix config; BrowserStack/Sauce/LambdaTest for cross-OS"
+  na_when: "CLI-only, backend API, mobile native (non-web)"
+  release_readiness_dimension: "Dim 9, Tier-3"

package/bundled/ai/standards/capability-declaration.ai.yaml

@@ -100,10 +100,10 @@ standard:
       consequence: "記錄 CAPABILITY_MISMATCH 事件，降級至 FAIL_CLOSED_DEFAULTS"
 
   applicable_components:
-    - "DevAP AgentAdapter（ClaudeAdapter / OpenCodeAdapter / CliAdapter）"
-    - "DevAP Tool 呼叫系統"
-    - "VibeOps ToolExecutor"
-    - "VibeOps Agent（planner / builder / evaluator 等）"
+    - "AgentAdapter implementations (e.g., ClaudeAdapter / OpenCodeAdapter / CliAdapter at the adoption layer)"
+    - "Tool 呼叫系統（採用層 runtime）"
+    - "ToolExecutor 實作（採用層）"
+    - "Agent（採用層；planner / builder / evaluator 等角色）"
     - "所有 MCP 工具插件"
 
   error_codes:

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

@@ -1,6 +1,6 @@
 # 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
+# Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+# Adoption layer must implement an equivalent runtime; UDS retains only the human-readable concept under core/.
 # Migration: XSPEC-086 Phase 2 (2026-04-27)
 #
 # Human-readable standard: core/change-batching-standards.md (remains in UDS)
@@ -14,31 +14,29 @@ standard:
     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"
+    canonical_owner: adoption-layer
+    canonical_path: "" # adoption-layer responsibility
     source: core/change-batching-standards.md
     description: >
-      DEPRECATED: This standard has moved to DevAP (flow orchestration layer).
-      Install DevAP and load standards/flow/change-batching-standards.ai.yaml instead.
+      DEPRECATED: Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+      Adoption layer must implement an equivalent runtime.
 
   rules:
     - id: deprecation-notice
       trigger: any batch change operation
       instruction: >
-        This standard (change-batching-standards.ai.yaml) has been migrated to DevAP.
+        Runtime details for this standard are now adoption-layer responsibility (runtime moved to adoption layer 2026-04-28).
         For the canonical executable definition, load:
-          dev-autopilot/standards/flow/change-batching-standards.ai.yaml
 
         The human-readable standard remains at:
           universal-dev-standards/core/change-batching-standards.md
 
-        To install DevAP: npm install -g @devap/cli
       priority: required
 
     - id: atomic-commits
       trigger: merging a batch
       instruction: >
-        DEPRECATED — load dev-autopilot/standards/flow/change-batching-standards.ai.yaml
+        DEPRECATED — see universal-dev-standards/core/ for human-readable concept; runtime is adoption-layer responsibility
         for the current executable batch orchestration rules.
 
         Minimal fallback: Enforce all-or-nothing batch merging — either all changes

package/bundled/ai/standards/circuit-breaker.ai.yaml

@@ -20,7 +20,7 @@ standard:
     - "任何重試機制必須使用斷路器包裝，不得直接無限重試"
     - "斷路器狀態必須透過遙測可觀測（circuit_breaker_state_change 事件）"
     - "OPEN 狀態下的請求必須立即失敗（fail fast），不等待 timeout"
-    - "failureThreshold 預設值為 3，與 claude-code-book 及 DevAP Fix Loop 一致"
+    - "failureThreshold 預設值為 3，與 claude-code-book 及常見 Fix Loop 實作慣例一致"
     - "斷路器必須按照「功能單元」建立，不得全域共享單一斷路器"
 
   states:
@@ -80,12 +80,12 @@ standard:
       when: "每次狀態轉換時上傳"
 
   applicable_scenarios:
-    - "DevAP Fix Loop Agent 呼叫重試"
-    - "DevAP Judge / Quality Gate 重試"
-    - "DevAP API 呼叫（LLM API 不穩定保護）"
-    - "VibeOps Feedback Loop 重試"
-    - "VibeOps FLARE 主動檢索重試"
-    - "VibeOps AutoCompact（原始靈感來源）"
+    - "Fix Loop Agent 呼叫重試（採用層）"
+    - "Judge / Quality Gate 重試（採用層）"
+    - "LLM API 呼叫（不穩定保護）"
+    - "Feedback Loop 重試（採用層）"
+    - "FLARE 主動檢索重試（採用層）"
+    - "AutoCompact 風格的對話壓縮重試（claude-code-book 為原始靈感來源）"
 
   error_codes:
     CB-001: "CIRCUIT_OPEN — 斷路器開路，請求被拒絕"

package/bundled/ai/standards/contract-testing-standards.ai.yaml

@@ -0,0 +1,62 @@
+# Contract Testing Standards - AI Optimized
+# Source: core/contract-testing-standards.md
+
+id: contract-testing-standards
+meta:
+  version: "1.0.0"
+  updated: "2026-05-05"
+  source: core/contract-testing-standards.md
+  description: Consumer-driven contract testing standard with release gate integration; applies to projects with API consumers
+
+requirements:
+  REQ-1:
+    id: REQ-CT-001
+    title: Consumer-Driven Flow
+    rule: >
+      For projects with API consumers, contracts MUST be published by consumers
+      to a Pact Broker (or equivalent). Providers MUST verify all active consumer
+      contracts in CI. The `can-i-deploy` command MUST return exit 0 before
+      any provider deployment.
+    rationale: >
+      Provider-only contract tests miss the most common class of contract bug:
+      the provider ships a change it considers non-breaking, but consumers assumed
+      different response structure.
+
+  REQ-2:
+    id: REQ-CT-002
+    title: Schema Matchers Not Literals
+    rule: >
+      Consumer contracts MUST use schema matchers (like(), eachLike(), integer(),
+      string(), email()) rather than exact literal values. Only assert fields
+      the consumer actually uses.
+    rationale: >
+      Literal value matching causes brittle contracts that break on realistic data
+      variation without indicating any real compatibility issue.
+
+  REQ-3:
+    id: REQ-CT-003
+    title: Backward Compatibility Window
+    rule: >
+      Minor releases MUST maintain N-1 consumer contract compatibility.
+      Major releases require a deprecation period: notify consumers, keep old
+      contract active until all consumers migrate, then archive.
+    rationale: >
+      Consumers cannot always upgrade in lockstep; the N-1 window allows them
+      one release cycle to migrate without service disruption.
+
+  REQ-4:
+    id: REQ-CT-004
+    title: Release Gate
+    rule: >
+      All active consumer contracts MUST be green before deploying a provider
+      to production. This is Dimension 4 (Tier-3) in release-readiness-gate.md.
+      Mark N/A when the project has no API consumers.
+    rationale: >
+      A red consumer contract means a deployed provider will break that consumer
+      in production — this is a hard release blocker, not a warning.
+
+quick_reference:
+  applies_when: "project has API consumers (service-to-service, frontend-to-backend, public API)"
+  gate: "can-i-deploy exit 0 before provider deploy; N-1 compat required"
+  broker_tag_convention: "main, production, <feature-branch>"
+  release_readiness_dimension: "Dim 4, Tier-3"

package/bundled/ai/standards/cross-flow-regression.ai.yaml

@@ -0,0 +1,61 @@
+# Cross-Flow Regression Standards - AI Optimized
+# Source: core/cross-flow-regression.md
+
+id: cross-flow-regression
+meta:
+  version: "1.0.0"
+  updated: "2026-05-05"
+  source: core/cross-flow-regression.md
+  description: Cross-flow regression testing complementing per-flow Multi-Gate; verifies inter-flow state correctness and CUJ pass rates
+
+requirements:
+  REQ-1:
+    id: REQ-CFR-001
+    title: CUJ Suite Required per Release
+    rule: >
+      Every release candidate MUST run the full Critical User Journey (CUJ) regression
+      suite. CUJs are end-to-end sequences spanning ≥ 2 flows that share state or are
+      commonly executed sequentially. CUJ pass rate MUST be ≥ 95%.
+    rationale: >
+      Per-flow Multi-Gate testing proves intra-flow correctness; cross-flow tests catch
+      state contamination bugs that only manifest when flow outputs become the next
+      flow's inputs.
+
+  REQ-2:
+    id: REQ-CFR-002
+    title: Retrigger on Flow Spec Change
+    rule: >
+      When any flow's §2.4 Decision Points or Terminal States are modified, the full
+      CUJ regression suite MUST re-run as a pre-merge check — not just tests for the
+      changed flow. This prevents silent regressions in downstream flows.
+    rationale: >
+      A change to one flow's terminal states can produce different intermediate state
+      that breaks a previously passing downstream flow.
+
+  REQ-3:
+    id: REQ-CFR-003
+    title: Sequential State Threading
+    rule: >
+      CUJ tests MUST use sequential state threading: a shared `ctx` object accumulates
+      state across flows within a single test describe block. State MUST NOT be reset
+      between steps of the same CUJ. Each CUJ MUST have its own isolated ctx.
+    rationale: >
+      Resetting state between steps masks cross-flow contamination; independent ctx
+      per CUJ prevents CUJ-to-CUJ interference from masking bugs.
+
+  REQ-4:
+    id: REQ-CFR-004
+    title: Release Gate
+    rule: >
+      CUJ pass rate ≥ 95% = PASS. 90–95% = WARN (document specific failed CUJs).
+      < 90% or any business-critical flow combo failure = FAIL (release blocked).
+      This is Dimension 6 (Tier-2) in release-readiness-gate.md.
+    rationale: >
+      90% threshold accounts for environment-specific flakiness while ensuring
+      the vast majority of user journeys are verified end-to-end.
+
+quick_reference:
+  boundary_with_flow_based_testing: "flow-based-testing = intra-flow; cross-flow-regression = inter-flow"
+  cuj_trigger: "every release candidate + any flow §2.4 change"
+  pass_rate_target: "≥ 95% overall; 100% for business-critical combos"
+  release_readiness_dimension: "Dim 6, Tier-2"

package/bundled/ai/standards/disaster-recovery-drill.ai.yaml

@@ -20,7 +20,7 @@ requirements:
       (Recovery Point Objective) targets. These must be agreed with stakeholders
       before any DR drill can be considered meaningful.
     examples:
-      - "VibeOps commercial: RTO < 1 hour, RPO < 24 hours (daily backup)"
+      - "Commercial-grade SaaS example: RTO < 1 hour, RPO < 24 hours (daily backup)"
 
   - id: REQ-02
     title: Backup Restore Test

package/bundled/ai/standards/dual-phase-output.ai.yaml

@@ -97,9 +97,9 @@ standard:
     note: "Savings accumulate in repeated review scenarios (Fix Loop, Feedback Loop)"
 
   applicable_agents:
-    - DevAP Judge Agent
-    - VibeOps Evaluator Agent
-    - VibeOps Guardian Agent
+    - Judge Agent (adoption layer)
+    - Evaluator Agent (adoption layer)
+    - Guardian Agent (adoption layer)
     - Any LLM-driven AutoCompact / summarization component
 
   error_codes:

package/bundled/ai/standards/execution-history.ai.yaml

@@ -1,6 +1,6 @@
 # Execution History Repository Standards - DEPRECATED STUB
-# This file has been migrated to DevAP per DEC-049 (UDS/DevAP responsibility split).
-# Canonical location: dev-autopilot/standards/orchestration/execution-history.ai.yaml
+# Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+# Adoption layer must implement an equivalent runtime; UDS retains only the human-readable concept under core/.
 # Migration: XSPEC-086 Phase 2 (2026-04-27)
 #
 # Source spec: cross-project/specs/XSPEC-003-execution-history-standard-sdd.md
@@ -14,29 +14,27 @@ standard:
     deprecated: true
     deprecated_since: "5.4.0"
     removal_version: "6.0.0"
-    canonical_owner: devap
-    canonical_path: "dev-autopilot/standards/orchestration/execution-history.ai.yaml"
+    canonical_owner: adoption-layer
+    canonical_path: "" # adoption-layer responsibility
     source: cross-project/specs/XSPEC-003-execution-history-standard-sdd.md
     description: >
-      DEPRECATED: This standard has moved to DevAP (orchestration layer).
-      Install DevAP and load standards/orchestration/execution-history.ai.yaml instead.
+      DEPRECATED: Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+      Adoption layer must implement an equivalent runtime.
 
   rules:
     - id: deprecation-notice
       trigger: any execution history operation
       instruction: >
-        This standard (execution-history.ai.yaml) has been migrated to DevAP.
+        Runtime details for this standard are now adoption-layer responsibility (runtime moved to adoption layer 2026-04-28).
         For the canonical executable definition, load:
-          dev-autopilot/standards/orchestration/execution-history.ai.yaml
 
-        Note: DevAP's packages/core already implements execution history (ExecutionHistoryStorage).
         The YAML standard is now co-located with the implementation.
       priority: required
 
     - id: record-on-completion
       trigger: "Agent 任務執行完畢"
       instruction: >
-        DEPRECATED — load dev-autopilot/standards/orchestration/execution-history.ai.yaml
+        DEPRECATED — see universal-dev-standards/core/ for human-readable concept; runtime is adoption-layer responsibility
         for the current executable history protocol.
 
         Minimal fallback: Write required artifacts to .execution-history/{task-id}/{run-number}/

package/bundled/ai/standards/failure-source-taxonomy.ai.yaml

@@ -22,7 +22,7 @@ standard:
     - "failureSource 為 optional 欄位，不得破壞現有不含此欄位的程式碼"
     - "在同一失敗事件中，選擇最根本的來源作為 failureSource（例如 branch_divergence 比 compilation 更根本）"
     - "failureSource 應由偵測到失敗的元件設定（QualityGate / Adapter / SafetyHook / BranchDriftChecker）"
-    - "跨專案（DevAP / VibeOps）各自獨立定義 FailureSource type，語義保持一致"
+    - "各採用層各自獨立定義 FailureSource type，語義保持一致（避免跨層耦合）"
 
   failure_sources:
     prompt_delivery:
@@ -103,13 +103,11 @@ standard:
       - "resource_exhaustion > 其他（資源耗盡時無意義重試）"
       - "其他情況取最先偵測到的來源"
 
+  # Integration guidance (informative only; concrete file paths are
+  # adoption-layer concerns and intentionally omitted from the standard).
   integration_points:
-    devap:
-      files:
-        - "packages/core/src/types.ts — TaskResult.failureSource / FailureSource type"
-        - "packages/core/src/quality-gate.ts — QualityGateResult.failureSource 推斷"
-        - "packages/adapter-claude/src/claude-adapter.ts — resource_exhaustion 映射"
-    vibeops:
-      files:
-        - "src/types/index.ts — IterationRecord.failureSource（獨立定義，AGPL 隔離）"
-        - "src/runner/pipeline-runner.ts — agent:error 事件 payload"
+    expected_call_sites:
+      - "core types module — TaskResult.failureSource / FailureSource type"
+      - "quality-gate module — QualityGateResult.failureSource 推斷"
+      - "agent adapter — resource_exhaustion / network_error 映射"
+      - "pipeline runner — agent:error / agent:retry 事件 payload"