@scemoon/cdh 1.0.5 → 1.0.7

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 级回滚）

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

@@ -1,61 +0,0 @@
-# Deliver Rules (DLV-*) + Stack Rules (STK-*)
-
-## DLV-001: Unified Stack Preview Before Production
-**Severity:** MUST
-**Description:** Every release MUST deploy as unified stack preview with per-component e2e + cross-stack e2e passing before production.
-**Valid:** `deploy_stack --preview` → `pytest aidlc/tests/cross-stack/ --stack-url $STACK_URL`.
-**Invalid:** Deploying only one component to preview.
-
-## DLV-002: Production Approval Gate
-**Severity:** MUST
-**Description:** Production deployment requires explicit human approval reviewing per-component e2e, cross-stack e2e, staging smoke, and contract-diff.md.
-**Valid:** Human reviews all reports and explicitly approves.
-**Invalid:** Automated production deployment triggered solely by test pass.
-
-## DLV-003: Stack BVT Validation
-**Severity:** MUST
-**Description:** After production deploy, BVT MUST run against the stack. Failure triggers automatic stack rollback.
-**Valid:** `bvt ${PRODUCTION_URL}` → fail → `deploy_stack --rollback`.
-**Invalid:** BVT skip or success with errors.
-
-## DLV-004: Per-Component Preview URL Isolation
-**Severity:** MUST
-**Description:** e2e tests run against dynamic preview URLs, never hardcoded production URLs.
-**Valid:** `pytest apps/web/tests/e2e/ --preview-url $WEB_URL`.
-**Invalid:** Hardcoded `https://prod.example.com` in tests.
-
-## STK-001: Component Scope Declaration
-**Severity:** MUST
-**Description:** Every spec delta, design doc, task list MUST declare `affects:`.
-**Valid:** `affects: [web, backend, contracts]`.
-**Invalid:** Missing `affects` declaration.
-
-## STK-002: Cross-Component Tasks Have Edges
-**Severity:** MUST
-**Description:** Tasks consuming a contract MUST have explicit `depends_on` edge to producing task.
-**Valid:** `depends_on: [int-contract-auth-login, be-login-endpoint]`.
-**Invalid:** Implicit dependency with no DAG edge.
-
-## STK-003: Cross-Stack E2E Mandatory for ≥2 Components
-**Severity:** MUST
-**Description:** Changes affecting ≥2 components MUST have cross-stack e2e testing real flow between components.
-**Valid:** Real web client against real backend preview.
-**Invalid:** Cross-stack test that mocks the other component.
-
-## STK-004: Unified Stack Deploy
-**Severity:** MUST
-**Description:** Shared environments MUST use `deploy_stack` orchestrator, not per-component ad-hoc deploys.
-**Valid:** `deploy_stack --preview` deploys all components.
-**Invalid:** Ad-hoc per-component deploy to shared preview.
-
-## STK-005: Cross-Component Build Config Injection
-**Severity:** MUST
-**Description:** All client builds receive `BACKEND_URL` as build-time env var, never hardcoded.
-**Valid:** `pnpm --filter web build --env BACKEND_URL=$BACKEND_URL`.
-**Invalid:** Hardcoded URLs in `.env.production`.
-
-## STK-006: Stack-Level Rollback
-**Severity:** MUST
-**Description:** Rollback is stack operation. Entire previous stable version reverts together.
-**Valid:** `deploy_stack --rollback v1.2.3` reverts all components.
-**Invalid:** Rolling back only backend while leaving clients on new version.

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

@@ -1,25 +0,0 @@
----
-name: ai-dlc-plan
-description: "Plan Phase: Design Doc → Task DAG → Test Plan"
-triggers:
-  - plan
-  - design
-  - task-list
----
-
-# Plan Phase (规划)
-
-Convert approved spec into technical design and task decomposition.
-
-## Entry
-
-See `lifecycle.md` for the full phase flow.
-See `rules.md` for enforceable rules (PLN-001 to PLN-004).
-See `prompt.md` for the sub-agent delegation prompt template.
-
-## 当被委派时
-
-1. 读取 spec-delta 和 feature 文件
-2. 生成设计文档（per-component + integration）
-3. 分解为带 DAG 依赖的任务单元
-4. 编写测试计划（每层）

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

@@ -1,204 +0,0 @@
-# AI-DLC Phase 2: Plan (规划)
-
-Design the solution and decompose work into tracked, dependency-ordered units, including cross-component edges.
-
-## Goal
-
-Translate approved specifications into a concrete technical plan that can be executed unit by unit, with explicit cross-component dependencies and contract references.
-
-## Flow
-
-```
-Approved Spec + BDD Features (per-component + cross-stack)
-  │
-  ▼
-SDD: Design Doc
-  - architecture (per component)
-  - data model
-  - API contract (references INT-FR-*)
-  - state machine
-  - integration section (cross-component flow)
-  │
-  ▼
-SDD: Task Decomposition (units with DAG, including cross-component edges)
-  │
-  ▼
-TDD: Test Plan (per scenario, written before implementation)
-  - unit / integration / e2e / cross-stack layer
-  │
-  ▼
-INT: Contract plan (which contracts change, version impact)
-  │
-  ▼
-Gate: Human review → approved or revise
-```
-
-## SDD — Design Document (multi-component aware)
-
-A multi-component design doc is organized by **component sections** plus an **integration section**.
-
-```markdown
-## Design — CHG-{{id}}
-
-**Affects:** [{{components}}]
-**Contracts touched:** {{list or "none"}}
-
-### Component: backend (BE-FR-*)
-- Architecture: {{serverless / container / ...}}
-- Data model: {{tables / collections}}
-- API surface: {{references INT-FR-* contract}}
-- State machine: {{...}}
-
-### Component: web (WEB-FR-*)
-- Architecture: {{SPA / SSR}}
-- Routes: {{...}}
-- Data flow: {{uses aidlc/packages/shared generated from INT-FR-001}}
-
-### Component: native (NATIVE-FR-*)
-- Architecture: {{native architecture}}
-- Data flow: {{uses aidlc/packages/shared generated from INT-FR-*}}
-
-### Component: desktop (DESKTOP-FR-*)
-- Architecture: {{desktop architecture}}
-- Data flow: {{uses aidlc/packages/shared generated from INT-FR-*}}
-
-### Component: wxa (WXA-FR-*)
-- Architecture: {{WeChat Mini Program}}
-- Data flow: {{uses aidlc/packages/shared generated from INT-FR-*}}
-
-### Component: mya (MYA-FR-*)
-- Architecture: {{Mini Program}}
-- Data flow: {{uses aidlc/packages/shared generated from INT-FR-*}}
-
-### Component: tta (TTA-FR-*)
-- Architecture: {{TikTok Mini Program}}
-- Data flow: {{uses aidlc/packages/shared generated from INT-FR-*}}
-
-### Integration
-- Flow: {{web → backend → DB; or app → backend → event → ...}}
-- Contract refs: INT-FR-001, INT-FR-002
-- Failure modes: {{timeout, retry, fallback}}
-- Backward compat: {{additive / breaking → migration}}
-```
-
-### Data Model
-
-| Field | Type | Constraints |
-|-------|------|-------------|
-| id | UUID | PK |
-| email | string | UNIQUE, NOT NULL |
-| password_hash | string | NOT NULL |
-
-### API Contract
-
-| Method | Path | INT FR | Provider | Consumer |
-|--------|------|--------|----------|----------|
-| POST | /auth/login | INT-FR-001 | BE-FR-001 | WEB-FR-001, NATIVE-FR-001, DESKTOP-FR-001, WXA-FR-001, MYA-FR-001, TTA-FR-001 |
-
-### State Machine
-
-```
-ANONYMOUS → LOGGED_IN → SESSION_EXPIRED
-              ↓
-          LOGGED_OUT
-```
-
-## SDD — Task Decomposition with DAG (multi-component)
-
-Tasks MUST include cross-component edges. A task that produces or consumes a contract depends on the corresponding `INT-FR-*` task.
-
-```mermaid
-graph TD
-  INT1[INT-FR-001: define /auth/login contract]
-  BE1[BE-FR-001 unit-1: DB schema + models]
-  BE2[BE-FR-001 unit-2: login endpoint]
-  WEB1[WEB-FR-001 unit-1: login form + API client]
-  WEB2[WEB-FR-001 unit-2: token storage + redirect]
-  CS1[INT-FR-001 cross-stack: e2e login flow]
-
-  INT1 --> BE2
-  INT1 --> WEB1
-  BE1 --> BE2
-  BE2 --> CS1
-  WEB1 --> CS1
-  WEB2 --> CS1
-```
-
-```yaml
-units:
-  - id: int-contract-1
-    fr: INT-FR-001
-    affects: [contracts]
-    depends_on: []
-    deliverables: [aidlc/contracts/api/auth.yaml]
-  - id: be-unit-1
-    fr: BE-FR-001
-    affects: [backend]
-    depends_on: []
-    scenarios: []
-  - id: be-unit-2
-    fr: BE-FR-001
-    affects: [backend]
-    depends_on: [int-contract-1, be-unit-1]
-    scenarios: ["BE-FR-001 @positive", "BE-FR-001 @negative"]
-  - id: web-unit-1
-    fr: WEB-FR-001
-    affects: [web]
-    depends_on: [int-contract-1]
-    scenarios: ["WEB-FR-001 @positive", "WEB-FR-001 @negative"]
-  - id: cross-stack-1
-    fr: INT-FR-001
-    affects: [web, backend]
-    depends_on: [be-unit-2, web-unit-1]
-    layer: cross-stack
-    scenarios: ["INT-FR-001 @positive", "INT-FR-001 @negative", "INT-FR-001 @edge"]
-```
-
-## TDD — Test Plan (per scenario, per layer)
-
-Each scenario gets a test plan that names the **layer** it runs at.
-
-```markdown
-## BE-FR-001 @positive: Login API success
-Layer: integration
-Test cases:
-  1. test_login_valid_credentials_returns_jwt
-  2. test_login_sets_expiry_3600
-
-## WEB-FR-001 @positive: Login form happy path
-Layer: e2e
-Test cases:
-  1. test_login_form_submits_and_redirects
-
-## INT-FR-001 @positive: Full web→backend login flow
-Layer: cross-stack
-Test cases:
-  1. test_web_login_e2e_against_preview_url
-```
-
-## INT — Contract Plan
-
-For each contract change, list:
-- Old version, new version
-- Breaking? (yes / no) → if yes, plan migration in `aidlc/contracts/CHANGELOG.md`
-- Consumers affected (which components will pull the new shared types)
-- Backward-compat strategy (additive vs. deprecate-then-remove)
-
-## Artifacts
-
-| Artifact | Location | Purpose |
-|----------|----------|---------|
-| Design doc | `aidlc/openspec/changes/{id}/design.md` | Per-component + integration |
-| Task list | `aidlc/openspec/changes/{id}/task-list.md` | DAG with cross-component edges |
-| Test plan | Embedded in task-list or separate | Per-scenario, per-layer |
-| Contract plan | `aidlc/openspec/changes/{id}/contract-diff.md` placeholder | Filled in Verify |
-
-## Gate
-
-**Before advancing to Verify phase:**
-- [ ] Design doc has per-component sections + integration section
-- [ ] Tasks decomposed with explicit dependency DAG (including cross-component edges)
-- [ ] `INT-FR-*` tasks precede the consuming per-component tasks
-- [ ] Test plans name the layer (`unit` / `integration` / `e2e` / `cross-stack`) per scenario
-- [ ] Contract plan identifies breaking vs. additive
-- [ ] Human reviewed and approved

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

@@ -1,38 +0,0 @@
-# Plan Phase Agent Prompt
-
-你是一个 AI-DLC Plan Phase Agent。
-由 Master Agent 委派处理方案设计。
-
-## 输入
-- `aidlc/openspec/changes/{id}/spec-delta.md`
-- BDD feature 文件
-
-## 任务
-
-1. **SDD: Design Doc**
-   - 在 `aidlc/openspec/changes/{id}/design.md` 输出
-   - 包含：架构图（Mermaid）、数据模型、API 表、状态机
-   - 每组件独立 section + 集成 section
-
-2. **SDD: Task Decomposition**
-   - 在 `aidlc/openspec/changes/{id}/task-list.md` 输出
-   - YAML 格式，unit 带 `depends_on` DAG
-   - 跨组件 task 显示声明 `depends_on` 关系
-
-3. **TDD: Test Plan**
-   - 每个 BDD scenario 对应最少一个测试 case
-   - 标注 layer: unit / integration / e2e / cross-stack / contract
-
-4. **Contract Plan**
-   - 标注版本影响：additive / breaking
-   - 如需 breaking change 标记为 human-approval 阻塞
-
-## 输出产物
-- `aidlc/openspec/changes/{id}/design.md`
-- `aidlc/openspec/changes/{id}/task-list.md`
-- `aidlc/openspec/changes/{id}/contract-diff.md`（占位）
-
-## 约束
-- 遵守 `rules.md` 中的 PLN-001 到 PLN-004
-- 遵守 STK-001, STK-002（affects 声明 + cross-component 依赖）
-- 完成前必须通过 Human Gate 审查

package/ai-dlc-skill/phases/plan/rules.md

@@ -1,25 +0,0 @@
-# Plan Rules (PLN-*)
-
-## PLN-001: Design Documentation
-**Severity:** MUST
-**Description:** Each feature MUST have a design document covering architecture, data model, API contracts, and state machine. For multi-component features, MUST have per-component sections and an integration section.
-**Valid:** `aidlc/openspec/changes/{id}/design.md` with `## Component: backend`, `## Component: web`, `## Integration`.
-**Invalid:** A single flat architecture section with no per-component concerns.
-
-## PLN-002: Dependency DAG
-**Severity:** MUST
-**Description:** Units MUST be decomposed with explicit dependency DAG including cross-component edges. A task producing/consuming a contract MUST depend on the corresponding `INT-FR-*` task.
-**Valid:** `depends_on: [int-contract-1, be-unit-1]` for a web task consuming the contract.
-**Invalid:** Per-component task lists with no cross-component edges.
-
-## PLN-003: Test Plan Before Implementation
-**Severity:** MUST
-**Description:** Test plans for each scenario MUST be written before implementation and MUST name the test layer (`unit`, `integration`, `e2e`, `cross-stack`, `contract`).
-**Valid:** `BE-FR-001 @positive → layer: integration → test_login_valid_credentials`
-**Invalid:** A test plan with no layer designation.
-
-## PLN-004: Contract Plan
-**Severity:** MUST
-**Description:** For each contract change, the design doc MUST identify version impact (additive vs. breaking), consumers affected, and backward-compat strategy.
-**Valid:** `INT-FR-001 change: additive, MINOR bump; no consumer migration needed`
-**Invalid:** Contract change with no version impact noted.

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

@@ -1,26 +0,0 @@
----
-name: ai-dlc-understand
-description: "Understand Phase: Intent → Spec Delta → BDD Feature Files"
-triggers:
-  - understand
-  - spec-delta
-  - EARS
-  - feature file
----
-
-# Understand Phase (理解)
-
-Transform business intent into formal specification and behavior scenarios.
-
-## Entry
-
-See `lifecycle.md` for the full phase flow.
-See `rules.md` for enforceable rules (UND-001 to UND-006).
-See `prompt.md` for the sub-agent delegation prompt template.
-
-## 当被委派时
-
-1. 读取 intent 输入
-2. 按 SDD 方法生成 spec-delta（EARS 格式）
-3. 为每个 FR 写 BDD feature 文件（≥3 scenarios: positive, negative, edge）
-4. 输出到 `aidlc/openspec/changes/{id}/`