@scemoon/cdh 1.0.6 → 1.0.8

package/ai-dlc-skill/components/tta.md

@@ -1,29 +0,0 @@
-# TTA 组件开发指南 (TTA-FR-*) — 抖音小程序
-
-## 技术栈
-- 框架: 抖音原生小程序 / uni-app
-- 语言: JavaScript / TypeScript
-- 构建: 抖音开发者工具
-- 测试: Jest
-- BDD: 手动 + miniprogram-automator
-
-## 关键命令
-- 构建: `pnpm --filter tta build`
-- 测试: `pnpm --filter tta test`
-- 预览: 上传到抖音小程序预览平台
-- Lint: `pnpm --filter tta lint`
-
-## 目录约定
-- `src/` → 组件源码
-- `tests/unit/` → 单元测试
-- `features/` → BDD feature 文件
-
-## FR 命名空间
-- Prefix: TTA-FR-NNN
-- 范围: 抖音小程序行为
-
-## 特定约束
-- 抖音小程序审核流程
-- 预览通过小程序预览 QR 码访问
-- `BACKEND_URL` 在构建时注入
-- 视频/直播相关功能使用抖音小程序 API

package/ai-dlc-skill/components/web.md

@@ -1,31 +0,0 @@
-# Web 组件开发指南 (WEB-FR-*)
-
-## 技术栈
-- 框架: React / Vue / Svelte
-- 语言: TypeScript
-- 构建: Vite / Webpack
-- 测试: Vitest / Jest + Testing Library
-- BDD: Cucumber.js / pytest-bdd
-
-## 关键命令
-- 构建: `pnpm --filter web build`
-- 测试全部: `pnpm --filter web test`
-- BDD: `cucumber-js features/`
-- Lint: `pnpm --filter web lint`
-
-## 目录约定
-- `src/` → 组件源码
-- `tests/unit/` → 单元测试
-- `tests/integration/` → 集成测试
-- `tests/e2e/` → E2E 测试
-- `features/` → BDD feature 文件
-- `features/steps/` → BDD step definitions
-
-## FR 命名空间
-- Prefix: WEB-FR-NNN
-- 范围: 浏览器端行为（SPA / SSR）
-
-## 特定约束
-- Web 组件在构建时接收 `BACKEND_URL` 环境变量
-- 使用 `aidlc/packages/shared/` 中的生成类型
-- API 调用走 `aidlc/packages/shared/api/`

package/ai-dlc-skill/components/wxa.md

@@ -1,29 +0,0 @@
-# WXA 组件开发指南 (WXA-FR-*) — 微信小程序
-
-## 技术栈
-- 框架: 微信原生小程序 / Taro / uni-app
-- 语言: JavaScript / TypeScript
-- 构建: 微信开发者工具 / Taro CLI
-- 测试: Jest / miniprogram-simtest
-- BDD: 手动 + 自动化（通过 miniprogram-automator）
-
-## 关键命令
-- 构建: `pnpm --filter wxa build`
-- 测试: `pnpm --filter wxa test`
-- 预览: 上传到微信小程序预览平台
-- Lint: `pnpm --filter wxa lint`
-
-## 目录约定
-- `src/` → 组件源码
-- `tests/unit/` → 单元测试
-- `features/` → BDD feature 文件
-
-## FR 命名空间
-- Prefix: WXA-FR-NNN
-- 范围: 微信小程序行为
-
-## 特定约束
-- 微信小程序审核流程（每次上架需要审核）
-- 预览通过小程序预览 QR 码访问
-- `BACKEND_URL` 在构建时注入到小程序配置
-- 不支持 npm 包中的所有 API（仅微信 API）

package/ai-dlc-skill/contracts/README.md

@@ -1,25 +0,0 @@
-# Contracts 目录说明
-
-## 三层合约体系
-
-```
-contracts/
-├── api/              ← OpenAPI 3.1 — HTTP API 合约 (已有)
-├── events/           ← AsyncAPI 3.0 — 事件合约 (已有)
-└── functions/        ← Runtime Contract — Serverless 函数接口 (新增)
-```
-
-## aidlc/contracts/api/
-HTTP API 描述，使用 OpenAPI 3.1 格式。
-每个文件对应一个 INT-FR-NNN，描述请求/响应 schema。
-
-## aidlc/contracts/events/
-事件驱动合约，使用 AsyncAPI 3.0 + CloudEvents 格式。
-描述事件的生产/消费关系。
-
-## aidlc/contracts/functions/
-Serverless 函数接口描述，Provider-agnostic。
-描述函数的触发器、资源需求、环境变量。
-部署时根据选择的 provider + compute_mode 自动映射到具体平台。
-
-模板位于 `templates/integration/runtime-contract.yaml`。

package/ai-dlc-skill/core/adaptive-flow.md

@@ -1,36 +0,0 @@
-# Adaptive Flow — 自适应流程决策
-
-AI-DLC Master Agent 根据需求复杂度自动裁剪执行阶段。
-
-## 复杂度分级
-
-| 级别 | 触发条件 | 执行阶段 |
-|------|---------|---------|
-| L1 | 单文件 bug fix，不改行为 | Verify (TDD Red→Green→Refactor) |
-| L2 | 单组件新功能，无需 INT 合约 | Understand → Verify |
-| L3 | 多组件功能，需要 INT 合约 | Understand → Plan → Verify |
-| L4 | 全栈新功能 + 部署 | Understand → Plan → Verify → Deliver |
-| L5 | 架构重构/平台迁移 | Plan → Verify |
-
-## 决策流程
-
-```
-Intent 输入
-  │
-  ├─ 是否单文件/修 bug？           → L1
-  ├─ 是否单组件且不改合约？        → L2
-  ├─ 是否多组件/涉及跨组件边界？   → L3
-  ├─ 是否全栈/需要部署到生产？     → L4
-  └─ 是否重构/不新增行为/迁移？    → L5
-```
-
-## 复杂度评估 Prompt
-
-分析用户输入时，先判断以下维度：
-
-1. **范围 (Scope)**：单文件 / 单组件 / 多组件 / 全栈
-2. **类型 (Type)**：修 bug / 新功能 / 重构 / 迁移
-3. **合约 (Contract)**：是否涉及 INT-FR、OpenAPI、AsyncAPI
-4. **部署 (Deploy)**：是否需要上线到 production
-
-输出格式：`[Lx] Phase 列表`，如 `[L3] understand → plan → verify`

package/ai-dlc-skill/core/security.md

@@ -1,29 +0,0 @@
-# Security Rules (SEC-*)
-
-## SEC-001: Secrets Management
-**Severity:** MUST
-Secrets MUST be retrieved from secure storage, never hardcoded or logged.
-
-## SEC-002: Input Validation
-**Severity:** MUST
-All user input MUST be validated before processing: type, length, format, range.
-
-## SEC-003: SQL Injection Prevention
-**Severity:** MUST
-All database queries MUST use parameterized statements.
-
-## SEC-004: CORS Configuration
-**Severity:** MUST
-CORS headers MUST be explicitly configured. Wildcard origins prohibited in production.
-
-## SEC-005: Rate Limiting
-**Severity:** MUST
-Public endpoints require rate limiting: 100 req/min unauthenticated, 1000 req/min authenticated.
-
-## SEC-006: HTTPS Only
-**Severity:** MUST
-All production traffic MUST use HTTPS. HTTP redirects to HTTPS.
-
-## SEC-007: Audit Logging
-**Severity:** MUST
-Security events MUST be logged with timestamps and actor identity.

package/ai-dlc-skill/cross-tool/cline/export.sh

@@ -1,31 +0,0 @@
-#!/usr/bin/env bash
-# cline/export.sh — Export AI-DLC rules to Cline format (.clinerules)
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-SKILL_DIR="$(cd "$SCRIPT_DIR/../.." && pwd)"
-PROJECT_ROOT="$(cd "$SKILL_DIR/.." && pwd)"
-
-cat > "$PROJECT_ROOT/.clinerules" << 'EOF'
-# AI-DLC Development Rules (Cline)
-
-## Core Methodology
-AI-DLC: Intent → Spec (EARS) → BDD → Design → TDD → Deploy
-
-## FR Namespaces
-NATIVE apps/native | DESKTOP apps/desktop | WEB apps/web
-BE apps/backend | WXA apps/wxa | MYA apps/mya | TTA apps/tta
-INT aidlc/contracts/ + aidlc/packages/shared/
-
-## Quality Gates
-- Coverage >= 80%
-- BDD scenarios 100% pass
-- 0 vulns, no TODO in src/
-- Contract backward-compat by default
-- Cross-stack e2e mandatory for multi-component changes
-
-## Reference
-Full skill: .opencode/skills/ai-dlc-skill/
-EOF
-
-echo "  ✓ $PROJECT_ROOT/.clinerules"

package/ai-dlc-skill/cross-tool/copilot/export.sh

@@ -1,47 +0,0 @@
-#!/usr/bin/env bash
-# copilot/export.sh — Export AI-DLC rules to GitHub Copilot format (.github/copilot-instructions.md)
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-SKILL_DIR="$(cd "$SCRIPT_DIR/../.." && pwd)"
-PROJECT_ROOT="$(cd "$SKILL_DIR/.." && pwd)"
-
-mkdir -p "$PROJECT_ROOT/.github"
-
-cat > "$PROJECT_ROOT/.github/copilot-instructions.md" << 'EOF'
-# AI-DLC Copilot Instructions
-
-## Development Workflow
-Follow the AI-Driven Development Lifecycle:
-1. Understand (SDD+BDD): Intent → EARS Spec → BDD Features
-2. Plan (SDD+TDD): Design Doc → Task DAG → Test Plan
-3. Verify (BDD+TDD): TDD Red→Green→Refactor per scenario
-4. Deliver (SDD+Cloud): Stack Preview → e2e → Production + BVT
-
-## Component FR Mapping
-- NATIVE-FR-* → apps/native/
-- DESKTOP-FR-* → apps/desktop/
-- WEB-FR-* → apps/web/
-- BE-FR-* → apps/backend/
-- WXA-FR-* → apps/wxa/
-- MYA-FR-* → apps/mya/
-- TTA-FR-* → apps/tta/
-- INT-FR-* → aidlc/contracts/ + aidlc/packages/shared/
-
-## Quality Gates
-- Coverage ≥80%
-- BDD 100% pass
-- 0 security violations
-- No TODO/FIXME in src/
-- Contract backward-compatible
-- Cross-stack e2e for multi-component changes
-
-## Security
-- Secrets: secure storage, no hardcoding
-- Input: validate type/length/format/range
-- SQL: parameterized queries only
-- CORS: explicit origins, no wildcard in prod
-- HTTPS only in production
-EOF
-
-echo "  ✓ $PROJECT_ROOT/.github/copilot-instructions.md"

package/ai-dlc-skill/cross-tool/cursor/export.sh

@@ -1,32 +0,0 @@
-#!/usr/bin/env bash
-# cursor/export.sh — Export AI-DLC rules to Cursor format (.cursor/rules/*.mdc)
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-SKILL_DIR="$(cd "$SCRIPT_DIR/../.." && pwd)"
-PROJECT_ROOT="$(cd "$SKILL_DIR/.." && pwd)"
-CURSOR_DIR="$PROJECT_ROOT/.cursor/rules"
-
-mkdir -p "$CURSOR_DIR"
-
-# Core rules
-cat > "$CURSOR_DIR/ai-dlc-core.mdc" << 'EOF'
----
-description: AI-DLC Core Lifecycle Rules
-globs: ["*"]
----
-# AI-DLC Core Rules
-
-See `.opencode/skills/ai-dlc-skill/SKILL.md` for full methodology.
-
-Key rules:
-1. Intent → Spec → BDD → Code pipeline
-2. Contract-first for cross-component changes
-3. 3-phase minimum (L1 bug fix: Verify only; L2 feature: Understand→Verify)
-4. All tests must fail before code (TDD Red phase)
-5. Coverage ≥80%, BDD 100%, 0 vulns, no TODO
-
-FR namespaces: NATIVE-*, DESKTOP-*, WEB-*, BE-*, WXA-*, MYA-*, TTA-*, INT-*
-EOF
-
-echo "  ✓ $CURSOR_DIR/ai-dlc-core.mdc"

package/ai-dlc-skill/cross-tool/export.sh

@@ -1,22 +0,0 @@
-#!/usr/bin/env bash
-# export.sh — One-click export AI-DLC rules to all supported tool formats
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-
-echo "AI-DLC Cross-Tool Export"
-echo "========================"
-echo ""
-
-for tool in onecode cursor cline copilot; do
-  export_script="$SCRIPT_DIR/$tool/export.sh"
-  if [ -f "$export_script" ]; then
-    echo "[$tool] Running $export_script..."
-    bash "$export_script"
-  else
-    echo "[$tool] No export script found at $export_script"
-  fi
-  echo ""
-done
-
-echo "Done. All supported tool configs generated."

package/ai-dlc-skill/cross-tool/onecode/config.yaml.tpl

@@ -1,17 +0,0 @@
-# .cdh/config.yaml — AI-DLC 项目配置
-name: {{project_name}}
-platform: {{cloud_provider}}  # tcb | aliyun
-phase: {{current_phase}}     # understand | plan | verify | deliver
-
-# compute_mode: fc | sae | cloudbase-functions | cloudbase-run
-compute_mode: {{compute_mode}}
-
-stack:
-  components:
-    - native
-    - desktop
-    - web
-    - backend
-    - wxa
-    - mya
-    - tta

package/ai-dlc-skill/cross-tool/onecode/export-skills.sh

@@ -1,35 +0,0 @@
-#!/usr/bin/env bash
-# export-skills.sh — Generate per-component .skill/SKILL.md from components/*.md
-set -euo pipefail
-
-PROJECT_ROOT="${1:-$PWD}"
-SKILL_DIR="${2:-${AI_DLC_SKILL_DIR:-$HOME/.cdh/skills/ai-dlc-skill}}"
-
-if [ ! -d "$SKILL_DIR" ]; then
-  echo "  ✗ ai-dlc-skill not found at $SKILL_DIR" >&2
-  exit 1
-fi
-
-echo "Generating component skills in $PROJECT_ROOT/apps/*/.skill/"
-
-for component in native desktop web backend wxa mya tta; do
-  component_dir="$PROJECT_ROOT/apps/$component"
-  skill_dir="$component_dir/.skill"
-  src="$SKILL_DIR/components/$component.md"
-
-  if [ ! -d "$component_dir" ]; then
-    echo "  ⚠ $component_dir not found, skipping"
-    continue
-  fi
-
-  if [ ! -f "$src" ]; then
-    echo "  ⚠ $src not found, skipping"
-    continue
-  fi
-
-  mkdir -p "$skill_dir"
-  cp "$src" "$skill_dir/SKILL.md"
-  echo "  ✓ $component → $skill_dir/SKILL.md"
-done
-
-echo "Done."

package/ai-dlc-skill/cross-tool/onecode/export.sh

@@ -1,54 +0,0 @@
-#!/usr/bin/env bash
-# onecode/export.sh — Export AI-DLC rules to onecode format
-set -euo pipefail
-
-# Project root: first arg or current working directory
-PROJECT_ROOT="${1:-$PWD}"
-# Skill dir: CDH platform skill pool or AI_DLC_SKILL_DIR env var
-SKILL_DIR="${AI_DLC_SKILL_DIR:-$HOME/.cdh/skills/ai-dlc-skill}"
-
-if [ ! -d "$SKILL_DIR" ]; then
-  echo "  ✗ ai-dlc-skill not found at $SKILL_DIR" >&2
-  echo "  Run: cdh skill install ai-dlc-skill" >&2
-  exit 1
-fi
-
-echo "  Exporting onecode configs for project: $(basename "$PROJECT_ROOT")"
-
-CDH_DIR="$PROJECT_ROOT/.cdh"
-CROSS_TOOL_DIR="$SKILL_DIR/cross-tool/onecode"
-
-# 1. Generate .cdh/config.yaml if not exists
-if [ ! -f "$CDH_DIR/config.yaml" ]; then
-  mkdir -p "$CDH_DIR"
-  sed "s/{{project_name}}/$(basename "$PROJECT_ROOT")/g; s/{{cloud_provider}}/tcb/g; s/{{current_phase}}/understand/g; s/{{compute_mode}}/cloudbase-functions/g" \
-    "$CROSS_TOOL_DIR/config.yaml.tpl" > "$CDH_DIR/config.yaml"
-  echo "  ✓ $CDH_DIR/config.yaml created"
-else
-  echo "  - $CDH_DIR/config.yaml exists, skipping"
-fi
-
-# 2. Generate .cdh/state.json if not exists
-if [ ! -f "$CDH_DIR/state.json" ]; then
-  mkdir -p "$CDH_DIR"
-  cat > "$CDH_DIR/state.json" <<-EOF
-{
-  "current_phase": "understand",
-  "completed_phases": [],
-  "gate_results": {}
-}
-EOF
-  echo "  ✓ $CDH_DIR/state.json created"
-else
-  echo "  - $CDH_DIR/state.json exists, skipping"
-fi
-
-# 3. Generate .cdh/SKILL.md from the master skill (always refresh)
-mkdir -p "$CDH_DIR"
-cp "$SKILL_DIR/SKILL.md" "$CDH_DIR/SKILL.md"
-echo "  ✓ $CDH_DIR/SKILL.md updated"
-
-# 4. Generate component skills into apps/*/.skill/
-bash "$CROSS_TOOL_DIR/export-skills.sh" "$PROJECT_ROOT" "$SKILL_DIR"
-
-echo "  onecode export complete."

package/ai-dlc-skill/phases/deliver/entry.md

@@ -1,26 +0,0 @@
----
-name: ai-dlc-deliver
-description: "Deliver Phase: Stack Preview → e2e → Production + BVT"
-triggers:
-  - deliver
-  - deploy
-  - release
----
-
-# Deliver Phase (交付)
-
-Deploy full stack, run cross-stack e2e, human approval, production BVT.
-
-## Entry
-
-See `lifecycle.md` for the full phase flow.
-See `rules.md` for enforceable rules (DLV-001 to DLV-004 + STK-001 to STK-006).
-See `prompt.md` for the sub-agent delegation prompt template.
-
-## 当被委派时
-
-1. `deploy_stack --preview` 统一部署
-2. 运行 per-component e2e + cross-stack e2e
-3. Staging 部署 + smoke test
-4. Human approval gate
-5. Production 部署 + BVT + 自动回滚

package/ai-dlc-skill/phases/deliver/lifecycle.md

@@ -1,185 +0,0 @@
-# AI-DLC Phase 4: Deliver (交付)
-
-Deploy the **full stack** together, verify per-component and cross-stack e2e against the unified preview, release with stack-level BVT.
-
-## Goal
-
-Deliver verified code to production as a coherent stack with full confidence — preview environment, per-component e2e, cross-stack e2e, stack-level BVT, and rollback at the stack level.
-
-## Flow
-
-```
-All Verify gates passed (per-component + contract + cross-stack)
-  │
-  ▼
-Unified Stack Preview Deploy (dynamic URL from cloud provider)
-  - backend (functions + DB migrate)
-  - web (hosting build with BACKEND_URL)
-  - native (build with BACKEND_URL; package + upload)
-  - desktop (build with BACKEND_URL; package + upload)
-  - wxa / mya / tta (build with BACKEND_URL; upload to mini-program platform)
-  │
-  ▼
-Per-component BDD e2e (against component preview URL or stack URL)
-  │
-  ▼
-Cross-stack e2e (full app ↔ web ↔ backend against unified stack URL)
-  │
-  ▼
-Staging Stack Deploy + Smoke
-  │
-  ▼
-Human Approval Gate
-  │
-  ▼
-Production Stack Deploy (whole stack as one unit)
-  │
-  ▼
-Stack BVT (Build Verification Test) — backend /health, app launch probe, web smoke, DB
-  │
-  ▼
-Archive: contract-diff.md + e2e reports + BVT report
-  │
-  ▼
-Gate: BVT pass → done | BVT fail → stack rollback
-```
-
-## Unified Stack Preview Deploy
-
-The whole stack is deployed as one unit. The preview URL is the **backend gateway**; all client components (`web`, `native`, `desktop`, `wxa`, `mya`, `tta`) receive it as a build-time or runtime config.
-
-```bash
-# TCB (default)
-deploy_stack --preview
-# → backend: tcb fn deploy --env preview
-# → backend: tcb db migrate --env preview
-# → web:     tcb hosting deploy --env preview --build-env BACKEND_URL=${STACK_URL}
-# → native:  build with BACKEND_URL=${STACK_URL}, upload to internal distribution
-# → desktop: build with BACKEND_URL=${STACK_URL}, upload to internal distribution
-# → wxa:     build with BACKEND_URL=${STACK_URL}, upload to mini-program platform
-# → mya:     build with BACKEND_URL=${STACK_URL}, upload to mini-program platform
-# → tta:     build with BACKEND_URL=${STACK_URL}, upload to mini-program platform
-# → STACK_URL = https://{env-id}.tcb-preview.com
-
-# Aliyun
-deploy_stack --preview
-# → backend: fun deploy --env preview
-# → web:     oss + cdn deploy with build env
-# → native:  build with BACKEND_URL, package
-# → desktop: build with BACKEND_URL, package
-# → wxa:     build with BACKEND_URL, upload to mini-program platform
-# → mya:     build with BACKEND_URL, upload to mini-program platform
-# → tta:     build with BACKEND_URL, upload to mini-program platform
-# → STACK_URL = https://{gateway}.{region}.fc.devs.com
-```
-
-The `deploy_stack` tool resolves the preview URL dynamically per platform and exports it as `STACK_URL` (or `BACKEND_URL` for components to consume).
-
-## Per-Component BDD E2E
-
-```bash
-export STACK_URL=$(deploy_stack --preview --output url)
-export BACKEND_URL=$STACK_URL
-
-# Backend
-pytest apps/backend/tests/e2e/ --base-url $BACKEND_URL
-
-# Web (against web hosting URL; uses BACKEND_URL as API root)
-export WEB_URL=$(deploy_stack --preview --output web_url)
-pytest apps/web/tests/e2e/ --base-url $WEB_URL --api-url $BACKEND_URL
-
-# Native (against installed package or emulator; uses BACKEND_URL)
-pytest apps/native/tests/e2e/ --backend-url $BACKEND_URL
-
-# Desktop (against installed package or emulator; uses BACKEND_URL)
-pytest apps/desktop/tests/e2e/ --backend-url $BACKEND_URL
-
-# Mini-programs (wxa, mya, tta) (against emulator or device; uses BACKEND_URL)
-pytest apps/wxa/tests/e2e/ --backend-url $BACKEND_URL
-pytest apps/mya/tests/e2e/ --backend-url $BACKEND_URL
-pytest apps/tta/tests/e2e/ --backend-url $BACKEND_URL
-```
-
-## Cross-Stack E2E
-
-```bash
-pytest aidlc/tests/cross-stack/ --stack-url $STACK_URL --verbose
-# Runs the full multi-client ↔ backend flow defined in aidlc/features/cross-stack/
-```
-
-**Rule STK-001:** All `cross-stack` scenarios must pass before staging or production.
-
-## Staging
-
-```bash
-deploy_stack --env staging
-export STAGING_URL=$(deploy_stack --env staging --output url)
-pytest aidlc/tests/cross-stack/ --stack-url $STAGING_URL
-smoke-test $STAGING_URL
-```
-
-## Human Approval
-
-Production deployment requires explicit human approval. Approval is a **stack** decision — the reviewer sees the per-component e2e results, the cross-stack e2e results, the staging smoke, and the `contract-diff.md`.
-
-## Production Stack Deploy
-
-```bash
-deploy_stack --env production
-# → Same as preview/staging but with prod env IDs and production secrets
-```
-
-## Stack BVT (Build Verification Test)
-
-Automated health and functionality checks against the **production stack**:
-
-```bash
-bvt ${PRODUCTION_URL}
-# Checks:
-#  1. backend /health returns 200
-#  2. web home page returns 200 (SSR) or shell loads (SPA)
-#  3. native/desktop/mini-program launch probe (deep link resolves against BACKEND_URL)
-#  4. Core end-to-end flow (login) succeeds
-#  5. Database connectivity (probe query)
-#  6. No error rate spikes (5xx < 0.1%, p99 < 500ms)
-```
-
-**Rule DLV-003:** BVT must pass. If BVT fails, automatic **stack** rollback to the previous stable stack version.
-
-## Stack Rollback
-
-Rollback is at the stack level — all components revert together so the stack stays internally consistent.
-
-```bash
-# Automatic on BVT failure
-deploy_stack --rollback ${LAST_STABLE_STACK_VERSION}
-
-# Manual on demand
-deploy_stack --rollback --stack-version v1.2.3
-```
-
-The previous stable stack version is identified by the `aidlc/contracts/CHANGELOG.md` version at the time of the last green BVT.
-
-## Artifacts
-
-| Artifact | Purpose |
-|----------|---------|
-| `STACK_URL` / `BACKEND_URL` | Dynamic, per-platform, per-env |
-| Per-component e2e report | Scenario pass/fail per component |
-| Cross-stack e2e report | Full flow pass/fail |
-| `aidlc/openspec/changes/{id}/contract-diff.md` | Final contract change record |
-| BVT report | Stack-level health check results |
-| Deploy log | Stack version, timestamp, component versions |
-
-## Gate
-
-**Before marking complete:**
-- [ ] Unified stack preview deploy succeeded; `STACK_URL` and `BACKEND_URL` resolved
-- [ ] All per-component BDD e2e tests pass against their preview URLs
-- [ ] All cross-stack e2e tests pass against the unified stack URL
-- [ ] Staging smoke tests pass
-- [ ] Human approval received (covers per-component + cross-stack + staging + contract diff)
-- [ ] Production stack deploy succeeded
-- [ ] Stack BVT passed
-- [ ] (If BVT failed) Stack rollback executed and confirmed
-- [ ] `aidlc/openspec/changes/{id}/contract-diff.md` archived

package/ai-dlc-skill/phases/deliver/prompt.md

@@ -1,40 +0,0 @@
-# Deliver Phase Agent Prompt
-
-你是一个 AI-DLC Deliver Phase Agent。
-由 Master Agent 委派处理部署交付。
-
-## 输入
-- `aidlc/openspec/changes/{id}/contract-diff.md`
-- 所有 e2e 测试报告
-
-## 任务
-
-1. **Unified Stack Preview**
-   - `deploy_stack --preview --provider {tcb|aliyun} [--compute-mode {fc|sae}]`
-   - 输出 STACK_URL + per-component URLs
-
-2. **Per-Component e2e**
-   - 对每个 affected component 运行 e2e 测试
-   - 使用动态解析的 URL
-
-3. **Cross-Stack e2e**
-   - `pytest aidlc/tests/cross-stack/ --stack-url ${STACK_URL}`
-
-4. **Staging Deploy + Smoke**
-   - `deploy_stack --env staging`
-   - 运行 smoke-test + health-check
-
-5. **Production Gate + Deploy**
-   - 等待 Human Approval
-   - `deploy_stack --env production`
-   - BVT 验证 + 自动回滚
-
-## 输出产物
-- 动态 URLs（STACK_URL / BACKEND_URL / WEB_URL）
-- e2e 测试报告（per-component + cross-stack）
-- BVT 报告
-- 部署日志
-
-## 约束
-- 遵守 DLV-001 到 DLV-004
-- 遵守 STK-004 到 STK-006（统一部署 + 构建配置注入 + stack 级回滚）