universal-dev-standards 5.3.1 → 5.4.0

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

@@ -1,302 +1,44 @@
-# Execution History Repository Standards - AI Optimized
-# Source: cross-project/specs/XSPEC-003-execution-history-standard-sdd.md
+# 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
+# Migration: XSPEC-086 Phase 2 (2026-04-27)
+#
+# Source spec: cross-project/specs/XSPEC-003-execution-history-standard-sdd.md
+# Deprecation schedule: UDS 5.4.0 deprecated → UDS 6.0.0 removed
 
 standard:
   id: execution-history
-  name: "Execution History Repository Standards"
-  description: "Structured system for persisting agent execution artifacts with L1/L2/L3 tiered access model"
-  guidelines:
-    - "每次 agent 任務執行完畢後，必須產出 required artifacts"
-    - "歷史以檔案系統目錄結構組織，支援直接路徑存取"
-    - "提供 L1/L2/L3 三層存取，平衡資訊量與 token 成本"
-    - "敏感資訊在寫入時自動 redact"
-    - "跨專案僅共享 L1 層級，遵守授權隔離"
-    - "歷史保留策略確保 L1/L2 索引永久保留，L3 artifacts 依 max_runs 設定自動清理以控制儲存空間"
-
   meta:
-    version: "1.0.0"
-    updated: "2026-04-02"
+    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/execution-history.ai.yaml"
     source: cross-project/specs/XSPEC-003-execution-history-standard-sdd.md
-    description: "基於 Meta-Harness 論文洞見，建立跨專案執行歷史標準"
-
-  schema:
-    storage:
-      description: "執行歷史為 append-only log，支援兩種儲存後端"
-      backends:
-        local:
-          description: "儲存在 repo 內的 .execution-history/ 目錄"
-          git_policy: |
-            L3 artifacts 不追蹤（納入 .gitignore），L1 index.json 可選追蹤。
-            歷史本質是寫入後不變動的 log，不適合 git 追蹤大量變動。
-          gitignore_rules: |
-            .execution-history/*/           # L3 artifacts 不追蹤
-            !.execution-history/index.json  # L1 索引可選追蹤
-            !.execution-history/index-archive.json  # L1 歸檔索引可選追蹤
-          when_to_use: "個人開發、小型專案、或不需跨環境共享歷史時"
-        file_server:
-          description: "儲存在外部 FileServer（如 S3、MinIO、NAS、共享磁碟）"
-          config_file: ".execution-history/storage.json"
-          config_schema:
-            backend: { type: string, enum: [local, file_server] }
-            file_server_url: { type: string, description: "FileServer 端點 URL" }
-            auth_method: { type: string, enum: [none, api_key, oauth], default: none }
-            sync_l1_to_local: { type: boolean, default: true, description: "是否將 L1 索引同步到本地" }
-          when_to_use: "團隊協作、跨環境共享、歷史量大、或需要長期保存時"
-          rules:
-            - "L1 索引始終同步到本地（sync_l1_to_local: true），確保離線可讀"
-            - "L2/L3 按需從 FileServer 拉取"
-            - "寫入走 FileServer API，本地不留 L3 副本"
-      default_backend: local
-
-    directory_structure:
-      root: ".execution-history/"
-      layout: |
-        .execution-history/
-        ├── storage.json                        # 儲存後端配置（可選，預設 local）
-        ├── index.json                          # L1: 最近 50 個活躍 tasks 索引
-        ├── index-archive.json                  # L1-ext: 歸檔 tasks 索引（> 90 天無新 run）
-        ├── {task-id}/
-        │   ├── manifest.json                   # L2: 任務層級摘要
-        │   ├── {run-number}/                   # 三位數字（001-999）
-        │   │   ├── manifest.json               # L2: 單次執行摘要
-        │   │   ├── task-description.md          # Required: 任務描述
-        │   │   ├── code-diff.patch              # Required: 程式碼變更
-        │   │   ├── test-results.json            # Required: 測試結果
-        │   │   ├── execution-log.jsonl          # Required: 執行日誌
-        │   │   ├── token-usage.json             # Required: Token 使用量
-        │   │   ├── final-status.json            # Required: 最終狀態
-        │   │   ├── error-analysis.md            # Optional: 錯誤分析
-        │   │   └── agent-reasoning.md           # Optional: Agent 推理過程
-        │   └── ...
-        └── ...
-      index_strategy:
-        description: "分層索引策略，平衡即時性與歷史完整性"
-        active_index: "index.json — 最近 50 個活躍 tasks（< 200 tokens 目標）"
-        archive_index: "index-archive.json — 超過 90 天無新 run 的 tasks 自動歸檔"
-        archive_trigger: "task 最後一次 run 距今 > 90 天"
-        reactivate_trigger: "歸檔 task 有新 run 時自動移回 active index"
-
-    artifacts:
-      required:
-        - id: task-description
-          file: "task-description.md"
-          format: markdown
-          description: "任務目標、輸入、預期產出"
-          max_size: "2KB"
-        - id: code-diff
-          file: "code-diff.patch"
-          format: "unified diff"
-          description: "本次執行產生的程式碼變更"
-          max_size: "50KB"
-        - id: test-results
-          file: "test-results.json"
-          format: json
-          description: "測試執行結果（通過/失敗/跳過數量、失敗詳情）"
-          schema_ref: "#/definitions/test-results"
-        - id: execution-log
-          file: "execution-log.jsonl"
-          format: jsonl
-          description: "結構化執行日誌（每行一個事件）"
-          schema_ref: "#/definitions/log-entry"
-        - id: token-usage
-          file: "token-usage.json"
-          format: json
-          description: "Token 使用量明細（input/output/total，按步驟分）"
-          schema_ref: "#/definitions/token-usage"
-        - id: final-status
-          file: "final-status.json"
-          format: json
-          description: "最終狀態（success/failure/partial，含摘要）"
-          schema_ref: "#/definitions/final-status"
-      optional:
-        - id: error-analysis
-          file: "error-analysis.md"
-          format: markdown
-          description: "失敗時的根因分析"
-          condition: "status != success"
-        - id: agent-reasoning
-          file: "agent-reasoning.md"
-          format: markdown
-          description: "Agent 的推理過程與決策紀錄"
-
-    access_layers:
-      L1:
-        name: "索引層"
-        files:
-          active: "index.json"
-          archive: "index-archive.json"
-        target_tokens: "< 200 (active), 按需 (archive)"
-        fields:
-          - task_id
-          - task_name
-          - tags
-          - latest_run
-          - latest_status
-          - latest_date
-          - total_runs
-        cross_project_access: true
-      L2:
-        name: "摘要層"
-        file: "manifest.json"
-        target_tokens: "< 1,000 per task"
-        fields:
-          - task_description_summary
-          - run_history
-          - key_metrics
-          - artifacts_available
-          - failure_summary
-        cross_project_access: false
-      L3:
-        name: "完整紀錄層"
-        file: "各 artifact 檔案"
-        target_tokens: "不限"
-        description: "直接讀取 run 目錄下的個別 artifact 檔案"
-        cross_project_access: false
-
-    retention_policy:
-      configurable: true
-      defaults:
-        max_runs_per_task: 50
-        max_total_size_mb: 500
-        cleanup_strategy: "oldest_l3_first"
-      rules:
-        - "超過 max_runs 時，最舊的 run 的 L3 artifacts 被刪除"
-        - "L1 和 L2 索引永久保留（除非手動刪除）"
-        - "cleanup 以 task 為單位，不跨 task 清理"
-
-    sensitive_data:
-      redact_on_write: true
-      sensitive_patterns:
-        - pattern: "sk-[a-zA-Z0-9_-]{20,}"
-          label: "API_KEY"
-        - pattern: "ghp_[a-zA-Z0-9]{36}"
-          label: "GITHUB_TOKEN"
-        - pattern: "password\\s*[:=]\\s*\\S+"
-          label: "PASSWORD"
-        - pattern: "-----BEGIN .* PRIVATE KEY-----"
-          label: "PRIVATE_KEY"
-      redact_format: "[REDACTED:{label}]"
-
-  definitions:
-    test-results:
-      type: object
-      required: [timestamp, summary, details]
-      properties:
-        timestamp:
-          type: string
-          format: "ISO 8601"
-        summary:
-          type: object
-          properties:
-            total: { type: integer }
-            passed: { type: integer }
-            failed: { type: integer }
-            skipped: { type: integer }
-        details:
-          type: array
-          items:
-            type: object
-            properties:
-              test_name: { type: string }
-              status: { type: string, enum: [passed, failed, skipped] }
-              duration_ms: { type: integer }
-              error_message: { type: string }
-
-    log-entry:
-      type: object
-      required: [timestamp, level, event]
-      properties:
-        timestamp: { type: string, format: "ISO 8601" }
-        level: { type: string, enum: [debug, info, warn, error] }
-        event: { type: string }
-        details: { type: object }
-        tool_call: { type: string }
-        tokens: { type: integer }
-
-    token-usage:
-      type: object
-      required: [total, breakdown]
-      properties:
-        total:
-          type: object
-          properties:
-            input_tokens: { type: integer }
-            output_tokens: { type: integer }
-        breakdown:
-          type: array
-          items:
-            type: object
-            properties:
-              step: { type: string }
-              input_tokens: { type: integer }
-              output_tokens: { type: integer }
-
-    final-status:
-      type: object
-      required: [status, summary, timestamp]
-      properties:
-        status: { type: string, enum: [success, failure, partial] }
-        summary: { type: string }
-        timestamp: { type: string, format: "ISO 8601" }
-        duration_seconds: { type: number }
-        error: { type: string }
+    description: >
+      DEPRECATED: This standard has moved to DevAP (orchestration layer).
+      Install DevAP and load standards/orchestration/execution-history.ai.yaml instead.
 
   rules:
-    - id: record-on-completion
-      trigger: "Agent 任務執行完畢（無論成功或失敗）"
+    - id: deprecation-notice
+      trigger: any execution history operation
       instruction: >
-        在任務完成後，依據 storage.json 配置的後端（預設 local），
-        將所有 required artifacts 寫入 .execution-history/{task-id}/{run-number}/ 目錄，
-        並更新 task manifest.json 和根 index.json。
-        若使用 file_server 後端，寫入走 FileServer API，
-        同時將 L1 索引同步到本地。
-      priority: required
-
-    - id: use-l1-first
-      trigger: "Agent 需要參考先前執行歷史"
-      instruction: >
-        先讀取 .execution-history/index.json（L1）篩選相關任務，
-        再讀取相關任務的 manifest.json（L2）了解脈絡，
-        僅在需要深入診斷時才讀取 L3 完整 artifacts。
-      priority: required
+        This standard (execution-history.ai.yaml) has been migrated to DevAP.
+        For the canonical executable definition, load:
+          dev-autopilot/standards/orchestration/execution-history.ai.yaml
 
-    - id: redact-sensitive
-      trigger: "寫入任何 artifact 到 .execution-history/"
-      instruction: >
-        在寫入前，掃描內容中的 sensitive_patterns，
-        將匹配內容替換為 [REDACTED:{label}] 格式。
+        Note: DevAP's packages/core already implements execution history (ExecutionHistoryStorage).
+        The YAML standard is now co-located with the implementation.
       priority: required
 
-    - id: respect-retention
-      trigger: "新 run 寫入後，檢查 retention_policy"
-      instruction: >
-        檢查該 task 的 run 數量是否超過 max_runs_per_task，
-        若超過則刪除最舊 run 的 L3 artifacts，保留 L1/L2 索引。
-      priority: recommended
-
-    - id: archive-stale-tasks
-      trigger: "index.json 更新時，檢查是否有 task 需要歸檔"
+    - id: record-on-completion
+      trigger: "Agent 任務執行完畢"
       instruction: >
-        若 index.json 中某 task 的 latest_date 距今超過 90 天，
-        將該 task 從 index.json 移至 index-archive.json。
-        若歸檔 task 有新 run 寫入，自動移回 index.json。
-        index.json 最多保留 50 個活躍 tasks。
-      priority: recommended
+        DEPRECATED — load dev-autopilot/standards/orchestration/execution-history.ai.yaml
+        for the current executable history protocol.
 
-    - id: cross-project-l1-only
-      trigger: "從其他專案讀取執行歷史"
-      instruction: >
-        跨專案存取僅限 L1 層級（index.json），
-        不得讀取 L2/L3 層級以遵守授權隔離。
+        Minimal fallback: Write required artifacts to .execution-history/{task-id}/{run-number}/
+        after each agent task completes.
       priority: required
-
-  storage:
-    directory: ".execution-history/"
-    format: "JSON + Markdown + JSONL + Patch"
-
-  architecture:
-    classification: always-on-protocol
-    note: >
-      Execution History 是 Always-On Protocol，
-      與 developer-memory、project-context-memory 同層級。
-      AI 自動遵循所有 rules，不需要 slash command。

package/bundled/ai/standards/pipeline-integration-standards.ai.yaml

@@ -1,184 +1,43 @@
-# Pipeline Integration Standards - AI Optimized
-# Source: core/pipeline-integration-standards.md
+# Pipeline Integration Standards - DEPRECATED STUB
+# This file has been migrated to DevAP per DEC-049 (UDS/DevAP responsibility split).
+# Canonical location: dev-autopilot/standards/flow/pipeline-integration-standards.ai.yaml
+# Migration: XSPEC-086 Phase 2 (2026-04-27)
+#
+# Human-readable standard: core/pipeline-integration-standards.md (remains in UDS)
+# Deprecation schedule: UDS 5.4.0 deprecated → UDS 6.0.0 removed
 
 standard:
   id: pipeline-integration
-  name: Pipeline Integration
-  description: Configuration contract, stage model, and context classification for automated development pipelines
-
   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/pipeline-integration-standards.ai.yaml"
     source: core/pipeline-integration-standards.md
-    references:
-      - "ISO/IEC 12207 (Software Lifecycle Processes)"
-      - "ISO/IEC 15504 SPICE (Process Assessment)"
-      - "Continuous Delivery (Jez Humble)"
-      - "DORA Metrics"
-
-  configuration_contract:
     description: >
-      Projects using automated pipelines declare pipeline preferences via standard toggles.
-      All toggles default to OFF (manual mode).
-
-    toggles:
-      - name: autoSpecGeneration
-        type: boolean
-        default: false
-        description: Automatically generate SDD specs from PRD/user stories
-        when_on: Pipeline generates spec draft, submits for review
-        when_off: Manual spec creation required
-
-      - name: autoDerive
-        type: boolean
-        default: false
-        description: Automatically derive BDD/TDD/ATDD from approved specs
-        when_on: Pipeline runs derivation after spec approval
-        when_off: Manual derivation via commands
-
-      - name: autoTDD
-        type: boolean
-        default: false
-        description: Automatically enter TDD RED phase after derivation
-        when_on: Pipeline sets RED state and creates test skeleton
-        when_off: Developer manually enters TDD
-
-      - name: autoCheckin
-        type: boolean
-        default: false
-        description: Automatically commit when all quality gates pass
-        when_on: Pipeline commits after all gates pass
-        when_off: Developer manually commits
-
-      - name: autoBatch
-        type: boolean
-        default: false
-        description: Automatically batch pending changes before commit
-        when_on: Pipeline accumulates changes and merges at threshold
-        when_off: Each change committed individually
-
-    reading_rules:
-      - Fail-safe defaults — all toggles default to OFF
-      - Explicit declaration — never assume toggle state without reading config
-      - Runtime override — CLI flags may override file-based config
-      - Validation — validate configuration values before execution
-
-  pipeline_stages:
-    description: Standard 6-stage pipeline model
-    stages:
-      - stage: PLAN
-        input: PRD, user stories, requirements
-        output: Structured requirements document
-        gate: Requirements reviewed
-
-      - stage: SPEC
-        input: Requirements
-        output: SDD specification with AC
-        gate: Spec approved
-
-      - stage: DERIVE
-        input: Approved spec
-        output: BDD scenarios, TDD skeletons, ATDD tables
-        gate: 1:1 AC mapping verified
-
-      - stage: BUILD
-        input: Test skeletons + spec
-        output: Implementation code
-        gate: Tests pass (RED→GREEN)
-
-      - stage: REVIEW
-        input: Implementation + tests
-        output: Review feedback
-        gate: Review approved
-
-      - stage: CHECKIN
-        input: Approved changes
-        output: Committed code
-        gate: All quality gates pass
-
-  context_classification:
-    types:
-      - type: greenfield
-        description: New project or feature with no existing code
-        scenario: Starting a new module, service, or product
-        strategy:
-          plan: Full requirements
-          spec: Complete SDD
-          derive: Full derivation
-          build: TDD from scratch
-          review: Full review
-          checkin: Standard checkin
-
-      - type: brownfield
-        description: Existing codebase requiring modification
-        scenario: Adding features to legacy code, refactoring
-        strategy:
-          plan: Impact analysis first
-          spec: Delta SDD (changes only)
-          derive: Targeted derivation
-          build: Modify existing + new tests
-          review: Focused review on changes
-          checkin: Standard checkin
-
-      - type: adhoc
-        description: Small, isolated changes
-        scenario: Bug fixes, configuration changes, hotfixes
-        strategy:
-          plan: Quick assessment
-          spec: Optional (for significant changes)
-          derive: Skip (unless complex)
-          build: Direct fix
-          review: Quick review
-          checkin: Standard checkin
-
-    detection_signals:
-      - signal: file_count
-        greenfield: 0 or minimal files
-        brownfield: Established codebase
-        adhoc: N/A
-      - signal: change_scope
-        greenfield: New directory/module
-        brownfield: Modifications to existing files
-        adhoc: 1-3 files changed
-      - signal: test_coverage
-        greenfield: No existing tests
-        brownfield: Existing test suite
-        adhoc: Existing tests cover area
+      DEPRECATED: This standard has moved to DevAP (flow orchestration layer).
+      Install DevAP and load standards/flow/pipeline-integration-standards.ai.yaml instead.
 
   rules:
-    - id: read-config-first
+    - id: deprecation-notice
       trigger: starting pipeline execution
-      instruction: Read all toggles from configuration before executing any stage
+      instruction: >
+        This standard (pipeline-integration-standards.ai.yaml) has been migrated to DevAP.
+        For the canonical executable definition, load:
+          dev-autopilot/standards/flow/pipeline-integration-standards.ai.yaml
+
+        The human-readable standard remains at:
+          universal-dev-standards/core/pipeline-integration-standards.md
       priority: required
 
     - id: fail-safe-defaults
       trigger: toggle not found in configuration
-      instruction: Default all unset toggles to OFF (manual mode)
-      priority: required
+      instruction: >
+        DEPRECATED — load dev-autopilot/standards/flow/pipeline-integration-standards.ai.yaml
+        for the current executable pipeline integration rules.
 
-    - id: enforce-stage-gates
-      trigger: completing a pipeline stage
-      instruction: Verify quality gate passes before progressing to next stage
+        Minimal fallback: Default all unset pipeline toggles to OFF (manual mode).
       priority: required
-
-    - id: context-awareness
-      trigger: starting pipeline execution
-      instruction: Detect or read context type and adapt stage strategy accordingly
-      priority: required
-
-    - id: log-decisions
-      trigger: skipping or executing a stage
-      instruction: Log which stages were executed, skipped, and why
-      priority: recommended
-
-    - id: validate-config
-      trigger: reading configuration
-      instruction: Validate toggle types (boolean), context enum, and unknown keys
-      priority: required
-
-related_standards:
-  - spec-driven-development.md
-  - forward-derivation-standards.md
-  - checkin-standards.md
-  - change-batching-standards.md
-  - acceptance-criteria-traceability.md