@scemoon/cdh 1.0.0

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

@@ -0,0 +1,192 @@
+# AI-DLC Phase 3: Verify (验证)
+
+Execute TDD red-green-refactor per BDD scenario at the right test layer, verify all scenarios, and run cross-component contract and cross-stack gates.
+
+## Goal
+
+Ensure every BDD scenario is correctly implemented at the right layer, every contract is backward-compatible, and the full stack e2e flow works — before delivery.
+
+## Flow
+
+```
+Plan + Tasks approved
+  │
+  ▼
+For each unit in DAG order (within each affected component):
+  For each BDD scenario in unit:
+    │
+    RED:   Write test at the right layer → confirm failure
+    GREEN: Write minimum implementation → confirm pass
+    REFACTOR: Clean up → confirm all tests still pass
+    │
+  ─────────────────────────────────
+  Next unit...
+  │
+  ▼
+After per-component units: regenerate shared types + contract tests
+  tools/generate_shared.py
+  pytest tests/contract/
+  tools/contract_diff.py
+  │
+  ▼
+After contracts: cross-stack e2e against unified preview
+  pytest tests/cross-stack/
+  │
+  ▼
+Gate: All layers green + contracts compatible + cross-stack pass
+```
+
+## Test Layers
+
+| Layer | When | Test Location | Run Against |
+|-------|------|---------------|-------------|
+| `unit` | Per function / module | `apps/{comp}/tests/unit/` | Local |
+| `integration` | Component + its DB / internal API | `apps/{comp}/tests/integration/` | Local container |
+| `e2e` | Whole component against preview | `apps/{comp}/tests/e2e/` | Component preview URL |
+| `cross-stack` | Full multi-client ↔ backend flow | `tests/cross-stack/` | Unified stack preview URL |
+| `contract` | Contract shape + backward compat | `tests/contract/` | Generated `packages/shared/` |
+
+## TDD — Red
+
+Write one pytest test per assertion in the BDD scenario, at the layer the test plan specified.
+
+```python
+# apps/backend/tests/unit/test_auth.py
+def test_login_valid_credentials():
+    result = authenticate("user@example.com", "correct123")
+    assert result.token is not None
+    assert result.expires_in == 3600
+```
+
+```bash
+pytest apps/backend/tests/unit/test_auth.py -v
+# FAILED — authenticate() not defined  (RED ✓)
+```
+
+**Rule VRF-001:** Test must fail on first run.
+
+## TDD — Green
+
+Write the minimum code to make the test pass. No premature abstraction.
+
+```python
+# apps/backend/src/auth/login.py
+def authenticate(email, password):
+    if email == "user@example.com" and password == "correct123":
+        return AuthResult(token="jwt_token", expires_in=3600)
+    raise AuthError("Invalid credentials")
+```
+
+**Rule VRF-002:** Minimum code to pass.
+
+## TDD — Refactor
+
+```bash
+pytest --cov --cov-fail-under=80
+# All tests passed, coverage ≥80%  (REFACTOR ✓)
+```
+
+**Rule VRF-003:** Behavior must not change. All existing tests must pass before and after.
+
+## Contract Verification (INT-001, INT-002, INT-003)
+
+After per-component units pass and before cross-stack e2e:
+
+```bash
+# 1. Regenerate shared types from contracts
+tools/generate_shared.py
+# → packages/shared/{api,events} updated
+
+# 2. Run contract tests
+pytest tests/contract/ --verbose
+# → All contract scenarios pass (uses packages/shared)
+
+# 3. Run contract compat check
+tools/contract_diff.py --base main --head HEAD
+# → exit 0 = backward-compatible
+# → exit 1 = breaking change detected, BLOCKED unless human-approved
+```
+
+**Rule INT-001:** Contract tests must be 100% pass.
+
+**Rule INT-002:** Any breaking contract change (field removed, type changed, status code changed, required field added) is BLOCKED until a human approves the major version bump and a migration note is added to `contracts/CHANGELOG.md`.
+
+**Rule INT-003:** Shared types must be generated, not hand-written. CI runs `generate_shared` and fails the build if `packages/shared/` is out of date.
+
+## Cross-Stack E2E (STK-001)
+
+```bash
+export STACK_URL=$(deploy_stack --preview --output url)
+pytest tests/cross-stack/ --stack-url $STACK_URL --verbose
+# All cross-stack scenarios pass
+```
+
+**Rule STK-001:** All `cross-stack` scenarios must pass. A single failure blocks delivery.
+
+## BDD Scenario Verification (per layer)
+
+```bash
+# Per component
+pytest-bdd apps/backend/features/ --verbose
+pytest-bdd apps/web/features/ --verbose       # e.g. via cucumber-js
+pytest-bdd apps/native/features/ --verbose    # or via detox/cavy
+pytest-bdd apps/desktop/features/ --verbose    # or via spectron
+pytest-bdd apps/wxa/features/ --verbose
+pytest-bdd apps/mya/features/ --verbose
+pytest-bdd apps/tta/features/ --verbose
+
+# Cross-stack
+pytest-bdd features/cross-stack/ --verbose
+```
+
+## Quality Gates (Backpressure)
+
+All gates enforced on every attempt to mark a unit / change complete:
+
+```bash
+# Per component
+pytest apps/{component}/ --cov --cov-fail-under=80 && \
+  pytest-bdd apps/{component}/features/ --verbose && \
+  bandit -r apps/{component}/src/ -q && \
+  ! grep -rn "TODO\|FIXME\|HACK\|XXX" apps/{component}/src/
+
+# Cross-component
+pytest tests/contract/ && \
+  tools/contract_diff.py --base main --head HEAD
+
+# Stack
+pytest tests/cross-stack/ --stack-url $STACK_URL
+```
+
+| Gate | Threshold | Rule | Scope |
+|------|-----------|------|-------|
+| Unit/integration coverage | ≥80% | VRF-005 | Per component |
+| BDD scenarios | 100% pass | VRF-004 | Per component |
+| Security | 0 vulns | VRF-005 | Per component |
+| No TODOs | 0 in src/ | VRF-005 | Per component |
+| Contract tests | 100% pass | INT-001 | Cross-component |
+| Contract compat | backward-compat | INT-002 | Cross-component |
+| Shared types | generated, in sync | INT-003 | Cross-component |
+| Cross-stack e2e | 100% pass | STK-001 | Stack |
+
+## Artifacts
+
+| Artifact | Location |
+|----------|----------|
+| TDD tests (unit/integration) | `apps/{comp}/tests/{unit,integration}/test_{feature}.py` |
+| TDD tests (e2e) | `apps/{comp}/tests/e2e/test_{feature}.py` |
+| BDD step defs (component) | `apps/{comp}/features/steps/test_{feature}_steps.py` |
+| BDD step defs (cross-stack) | `features/cross-stack/steps/test_{feature}_steps.py` |
+| Implementation | `apps/{comp}/src/{module}/{feature}.py` |
+| Contract tests | `tests/contract/test_{contract}.py` |
+| Cross-stack e2e | `tests/cross-stack/test_{flow}.py` |
+| Contract diff | `openspec/changes/{id}/contract-diff.md` (filled) |
+
+## Gate
+
+**Before advancing to Deliver phase:**
+- [ ] Per-component: All BDD scenarios pass (100%), coverage ≥80%, 0 vulns, no TODO
+- [ ] Contracts: `tools/contract_diff.py` exits 0; `tests/contract/` 100% pass; `packages/shared/` regenerated and in sync
+- [ ] Cross-stack: `tests/cross-stack/` 100% pass against stack preview
+- [ ] `openspec/changes/{id}/contract-diff.md` is filled and reviewed
+- [ ] All existing tests still pass

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

@@ -0,0 +1,43 @@
+# Verify Phase Agent Prompt
+
+你是一个 AI-DLC Verify Phase Agent。
+由 Master Agent 委派处理测试验证。
+
+## 输入
+- `openspec/changes/{id}/design.md` 和 `task-list.md`
+- BDD feature 文件
+
+## 任务
+
+1. **TDD Red-Green-Refactor**（按 DAG 顺序）
+   - 对每个 unit 的每个 BDD scenario：
+     - RED: 写 test → 确认失败
+     - GREEN: 写最小实现 → 确认通过
+     - REFACTOR: 重构清理 → 全部通过
+   - 测试按 layer 分类：unit / integration / e2e
+
+2. **Contract Verification**
+   - 重新生成 `packages/shared/` 类型
+   - 运行 `pytest tests/contract/`
+   - 运行 `tools/contract_diff.py`
+
+3. **Cross-Stack e2e**
+   - 对 unified preview 运行 `tests/cross-stack/`
+
+4. **Quality Gates**
+   - coverage ≥ 80%
+   - BDD scenarios 100% pass
+   - 0 vulns, no TODO
+
+## 输出产物
+- `apps/{component}/tests/{unit,integration,e2e}/test_{feature}.py`
+- `apps/{component}/features/steps/test_{feature}_steps.py`
+- `apps/{component}/src/{module}/{feature}.py`
+- `tests/contract/test_{contract}.py`
+- `tests/cross-stack/test_{flow}.py`
+- `openspec/changes/{id}/contract-diff.md`（填充）
+
+## 约束
+- 遵守 `rules.md` 中的 VRF-001 到 VRF-006
+- 遵守 INT-001 到 INT-006
+- 遵守 STK-001 到 STK-006

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

@@ -0,0 +1,73 @@
+# Verify Rules (VRF-*) + Integration Rules (INT-*)
+
+## VRF-001: TDD Red Phase
+**Severity:** MUST
+**Description:** Before writing implementation, write a test that asserts expected behavior. The test MUST fail on first run.
+**Valid:** `pytest apps/backend/tests/unit/test_auth.py -k test_login` → FAILED.
+**Invalid:** Test passes on first run.
+
+## VRF-002: TDD Green Phase
+**Severity:** MUST
+**Description:** Write the minimum code needed to make the test pass. No premature abstraction.
+**Valid:** Only the code path required by the test is implemented.
+**Invalid:** Adding database, caching, or logging before the test requires it.
+
+## VRF-003: TDD Refactor Phase
+**Severity:** MUST
+**Description:** After tests pass, refactor to improve code quality while keeping ALL tests green.
+**Valid:** `pytest --cov --cov-fail-under=80` → all pass.
+**Invalid:** Behavior change during refactoring.
+
+## VRF-004: BDD Scenario Pass Gate
+**Severity:** MUST
+**Description:** ALL BDD scenarios MUST pass at every required layer before marking complete.
+**Valid:** `pytest-bdd apps/{component}/features/ --verbose` → all pass.
+**Invalid:** Any failing BDD scenario.
+
+## VRF-005: Quality Gate Backpressure
+**Severity:** MUST
+**Description:** On every unit completion, ALL gates must pass: coverage ≥80%, BDD 100%, 0 vulns, no TODO.
+**Valid:** `pytest --cov --cov-fail-under=80 && bandit -r src/ -q && ! grep -rn "TODO" src/`
+**Invalid:** Any single gate fails.
+
+## VRF-006: Test Layer Correctness
+**Severity:** MUST
+**Description:** Each BDD scenario MUST be tested at the layer the plan specified. Cross-stack ≠ unit.
+**Valid:** Cross-stack scenarios in `tests/cross-stack/` against STACK_URL.
+**Invalid:** Cross-stack scenario implemented as mocked unit test.
+
+## INT-001: Contract as Source of Truth
+**Severity:** MUST
+**Description:** All cross-component APIs and events MUST be defined in `contracts/` (OpenAPI/AsyncAPI/GraphQL) and tagged with `INT-FR-*`.
+**Valid:** `contracts/api/auth.yaml` defines POST /auth/login; components use generated types.
+**Invalid:** Duplicate hand-written types across components with no contract file.
+
+## INT-002: Backward-Compatibility by Default
+**Severity:** MUST
+**Description:** Contract changes MUST be backward-compatible. Breaking = field removed, type changed, status code changed, required field added. BLOCKED until human approves MAJOR bump + CHANGELOG entry.
+**Valid:** Adding a new optional field (MINOR).
+**Invalid:** Removing a field without human approval.
+
+## INT-003: Generated Shared Types
+**Severity:** MUST
+**Description:** `packages/shared/` generated from `contracts/`. Component code MUST import from shared.
+**Valid:** `git diff --exit-code packages/shared/` → clean after generation.
+**Invalid:** Hand-edited files under `packages/shared/`.
+
+## INT-004: Contract Tests at INT FR Level
+**Severity:** MUST
+**Description:** Every `INT-FR-*` MUST have contract tests in `tests/contract/` verifying schema.
+**Valid:** Provider-agnostic contract tests using generated shared types.
+**Invalid:** Contract tests calling real production backend.
+
+## INT-005: Cross-Stack Feature Coverage
+**Severity:** MUST
+**Description:** Every `INT-FR-*` MUST have ≥3 scenarios in `features/cross-stack/` implemented in `tests/cross-stack/`.
+**Valid:** Cross-stack scenarios running against unified STACK_URL.
+**Invalid:** INT-FR without cross-stack feature file.
+
+## INT-006: Contract Diff Artifact
+**Severity:** MUST
+**Description:** Every contract change MUST produce `openspec/changes/{id}/contract-diff.md`.
+**Valid:** Generated by `tools/contract_diff.py` with added/removed/changed fields.
+**Invalid:** Contract change merged without contract-diff.md.

package/ai-dlc-skill/practices/bdd.md

@@ -0,0 +1,91 @@
+# Behavior-Driven Development (BDD)
+
+BDD is the behavior specification and verification methodology used in Understand and Verify phases.
+
+## Role in AI-DLC
+
+| Phase | BDD Usage |
+|-------|-----------|
+| Understand | Feature files with Given/When/Then scenarios |
+| Verify | pytest-bdd scenario verification against implementation |
+| Deliver | BDD e2e tests against preview URL |
+
+## Gherkin Syntax
+
+| Keyword | Purpose |
+|---------|---------|
+| `Feature` | High-level feature description |
+| `Scenario` | Single behavior example |
+| `Given` | Precondition / starting state |
+| `When` | Action performed |
+| `Then` | Expected outcome |
+| `And` / `But` | Additional clause |
+| `Background` | Steps before every scenario |
+| `Scenario Outline` | Template with Examples table |
+| `@tag` | Metadata (FR ID, type) |
+
+## Scenario Coverage Rules
+
+Each FR must have at least 3 scenarios:
+
+| Type | Purpose | Example Tag |
+|------|---------|-------------|
+| Positive | Happy path, should work | `@FR-001 @positive` |
+| Negative | Error handling, should fail | `@FR-001 @negative` |
+| Edge case | Boundary conditions | `@FR-001 @edge` |
+
+## Example
+
+```gherkin
+@FR-001
+Feature: User Login
+
+  @FR-001 @positive
+  Scenario: Successful login
+    Given the user is on the login page
+    When the user submits email "user@test.com" and password "correct123"
+    Then the user receives a JWT token
+    And the user is redirected to dashboard
+
+  @FR-001 @negative
+  Scenario: Login with wrong password
+    Given the user is on the login page
+    When the user submits email "user@test.com" and password "wrong"
+    Then the user sees error "Invalid credentials"
+
+  @FR-001 @edge
+  Scenario: Login with empty fields
+    Given the user is on the login page
+    When the user submits email "" and password ""
+    Then the user sees error "Email and password are required"
+```
+
+## pytest-bdd Integration
+
+```python
+# features/steps/test_login_steps.py
+from pytest_bdd import scenarios, given, when, then, parsers
+
+scenarios("../auth/login.feature")
+
+@given("the user is on the login page")
+def login_page():
+    return LoginPage()
+
+@when(parsers.parse("the user submits email {email} and password {password}"))
+def submit(email, password):
+    ...
+```
+
+## Verification
+
+```bash
+# Run all BDD scenarios
+pytest-bdd features/ --verbose
+
+# Run scenarios for a specific FR
+pytest-bdd features/ -k "FR-001"
+
+# BDD scenario coverage
+pytest-bdd features/ --coverage
+```

package/ai-dlc-skill/practices/sdd.md

@@ -0,0 +1,84 @@
+# Spec-Driven Development (SDD)
+
+SDD is the specification methodology used in Understand and Plan phases.
+
+## Role in AI-DLC
+
+| Phase | SDD Usage |
+|-------|-----------|
+| Understand | Intent capture, spec delta with EARS |
+| Plan | Design doc, task decomposition with DAG |
+| Deliver | Artifact archiving |
+
+## Core Artifacts
+
+### Proposal (Why/What/Impact)
+
+```markdown
+## Change: CHG-001 — User Authentication
+
+**Why:** Users need to securely access their accounts
+**What:** Email + password login with JWT session
+**Impact:** New auth module, changes to user model
+```
+
+### Spec Delta (EARS)
+
+```markdown
+## ADDED Requirements
+
+### FR-001: User Authentication
+
+**Priority:** P0
+
+**Description (Event-Driven):**
+When a user submits valid credentials, the system SHALL authenticate and return a JWT token.
+
+**Acceptance Criteria:**
+- AC1: Valid credentials return JWT with 1-hour expiry
+- AC2: Invalid credentials return 401
+- AC3: Empty fields return validation error
+```
+
+### Design Doc
+
+```markdown
+## Data Model: User
+
+| Field | Type | Constraints |
+|-------|------|-------------|
+| id | UUID | PK |
+| email | string | UNIQUE, NOT NULL |
+
+## API: POST /auth/login
+
+Request: `{email, password}`  Response: `{token, expires_in}`
+```
+
+### Task List with DAG
+
+```yaml
+units:
+  - id: unit-1
+    name: Database schema
+    depends_on: []
+  - id: unit-2
+    name: Login endpoint
+    depends_on: [unit-1]
+```
+
+## EARS Patterns
+
+| Pattern | Syntax | Example |
+|---------|--------|---------|
+| Ubiquitous | `The system SHALL ...` | Always-hash passwords with bcrypt |
+| Event-Driven | `When {event}, SHALL ...` | When user logs in, create session |
+| State-Driven | `While {state}, SHALL ...` | While session active, auto-refresh |
+| Unwanted | `If {condition}, SHALL ...` | If DB fails, return 503 |
+| Optional | `Where {feature}, SHALL ...` | Where SSO enabled, skip password |
+
+## Tools
+
+- Spec format: Markdown with EARS
+- Design: Markdown + Mermaid diagrams
+- Tasks: YAML with DAG structure

package/ai-dlc-skill/practices/tdd.md

@@ -0,0 +1,95 @@
+# Test-Driven Development (TDD)
+
+TDD is the implementation methodology used in the Verify phase.
+
+## Role in AI-DLC
+
+| Phase | TDD Usage |
+|-------|-----------|
+| Plan | Test plan written per scenario |
+| Verify | Red → Green → Refactor per BDD scenario |
+
+## Core Cycle
+
+```
+For each BDD scenario:
+  ┌──────────────────┐
+  │  1. RED          │  Write pytest test → confirm FAILURE
+  │  2. GREEN        │  Write minimum implementation → confirm PASS
+  │  3. REFACTOR     │  Clean up → all tests still PASS
+  └──────────────────┘
+```
+
+## RED Phase
+
+Write a test that asserts the expected behavior. It must fail on first run.
+
+```python
+# tests/unit/test_auth.py
+def test_login_valid_credentials():
+    result = authenticate("user@test.com", "correct123")
+    assert result.token is not None
+    assert result.expires_in == 3600
+```
+
+```bash
+pytest tests/unit/test_auth.py -v
+# FAILED — authenticate not defined  ✓ (RED confirmed)
+```
+
+**Rules:**
+- Test written before implementation code
+- Test must fail (confirms the assertion is valid)
+- Test covers only this scenario's behavior
+
+## GREEN Phase
+
+Write the minimum code to make the test pass.
+
+```python
+# src/auth/login.py
+def authenticate(email, password):
+    if email == "user@test.com" and password == "correct123":
+        return AuthResult(token="jwt_placeholder", expires_in=3600)
+    raise AuthError("Invalid credentials")
+```
+
+```bash
+pytest tests/unit/test_auth.py -v
+# PASSED  ✓ (GREEN)
+```
+
+**Rules:**
+- Minimum code to pass — no extras
+- No premature optimization
+- No new dependencies unless required
+
+## REFACTOR Phase
+
+Improve code quality without changing behavior.
+
+```bash
+pytest --cov --cov-fail-under=80
+# All tests passed, coverage ≥80%  ✓ (REFACTOR)
+```
+
+**Rules:**
+- Keep all tests green
+- No behavior changes
+- Repeat for next scenario
+
+## Naming Convention
+
+| Artifact | Location | Example |
+|----------|----------|---------|
+| Tests | `tests/unit/test_{feature}.py` | `tests/unit/test_auth.py` |
+| Step defs | `features/steps/test_{feature}_steps.py` | `features/steps/test_login_steps.py` |
+| Source | `src/{module}/{feature}.py` | `src/auth/login.py` |
+
+## Quality Gates
+
+```bash
+pytest --cov --cov-fail-under=80
+pytest-bdd features/ --verbose
+bandit -r src/ -q
+```

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

@@ -0,0 +1,114 @@
+# Cloud Providers
+
+## Default: TCB (Tencent CloudBase)
+
+TCB is the default cloud development platform. Aliyun is also supported.
+
+The provider layer supports a **monorepo multi-component stack** (native + desktop + web + backend + wxa + mya + tta). Use the `deploy_stack` orchestrator instead of per-component CLI commands for shared environments.
+
+## Provider Comparison
+
+| Capability | TCB | Aliyun |
+|-----------|-----|--------|
+| **Functions** | CloudBase Functions | Function Compute (FC) |
+| **Database** | DocDB + MySQL | TableStore + RDS |
+| **Storage** | COS (Cloud Object Storage) | OSS (Object Storage Service) |
+| **Hosting** | CloudBase Hosting + Preview | Static Website + CDN |
+| **Stack preview URL** | `https://{env-id}.tcb-preview.com` (gateway) | `https://{gateway}.{region}.fc.devs.com` |
+| **Default** | Yes | No |
+
+## Stack Deploy
+
+`deploy_stack` is the unified orchestrator. It deploys `backend` first, captures `BACKEND_URL`, then deploys all client components with `BACKEND_URL` injected. The output is `STACK_URL` (= `BACKEND_URL`) plus per-component URLs.
+
+```bash
+deploy_stack --preview --provider tcb
+# → STACK_URL=https://{env-id}.tcb-preview.com
+# → WEB_URL=https://{env-id}-{project}.tcb-preview.com
+# → NATIVE_DIST_URL=internal distribution URL
+# → DESKTOP_DIST_URL=internal distribution URL
+# → WXA_URL/MYA_URL/TTA_URL=mini-program preview QR
+```
+
+```bash
+deploy_stack --preview --provider aliyun
+# → STACK_URL=https://{gateway}.{region}.fc.devs.com
+# → WEB_URL=https://{bucket}.{region}.oss-website.aliyuncs.com
+# → NATIVE_DIST_URL=internal distribution URL
+# → DESKTOP_DIST_URL=internal distribution URL
+# → WXA_URL/MYA_URL/TTA_URL=mini-program preview QR
+```
+
+## Build Config Injection
+
+All client builds receive `BACKEND_URL` at build time. The orchestrator passes it; components must not hardcode URLs.
+
+```bash
+# web
+pnpm --filter web build --env BACKEND_URL=$BACKEND_URL
+
+# native
+cd apps/native && BACKEND_URL=$BACKEND_URL pnpm build
+
+# desktop
+cd apps/desktop && BACKEND_URL=$BACKEND_URL pnpm build
+
+# mini-programs (wxa, mya, tta)
+cd apps/wxa && BACKEND_URL=$BACKEND_URL pnpm build
+cd apps/mya && BACKEND_URL=$BACKEND_URL pnpm build
+cd apps/tta && BACKEND_URL=$BACKEND_URL pnpm build
+```
+
+## Component URL Resolution
+
+| Component | TCB | Aliyun |
+|-----------|-----|--------|
+| `backend` (gateway) | `https://{env-id}.tcb-preview.com` | `https://{gateway}.{region}.fc.devs.com` |
+| `web` (hosting) | `https://{env-id}-{project}.tcb-preview.com` | `https://{bucket}.{region}.oss-website.aliyuncs.com` |
+| `native` (distribution) | internal distribution URL | internal distribution URL |
+| `desktop` (distribution) | internal distribution URL | internal distribution URL |
+| `wxa` (mini-program) | mini-program preview QR | mini-program preview QR |
+| `mya` (mini-program) | mini-program preview QR | mini-program preview QR |
+| `tta` (mini-program) | mini-program preview QR | mini-program preview QR |
+
+## BDD E2E Targets
+
+| Test | Target |
+|------|--------|
+| `apps/backend/tests/e2e/` | `BACKEND_URL` |
+| `apps/web/tests/e2e/` | `WEB_URL` + `BACKEND_URL` (as API root) |
+| `apps/native/tests/e2e/` | `BACKEND_URL` (built into app) |
+| `apps/desktop/tests/e2e/` | `BACKEND_URL` (built into app) |
+| `apps/wxa/tests/e2e/` | `BACKEND_URL` (built into app) |
+| `apps/mya/tests/e2e/` | `BACKEND_URL` (built into app) |
+| `apps/tta/tests/e2e/` | `BACKEND_URL` (built into app) |
+| `tests/cross-stack/` | `STACK_URL` (full flow) |
+
+## Dynamic Preview URL
+
+Preview URLs are resolved at deploy time based on the active provider:
+
+- **TCB:** `deploy_stack --preview --provider tcb` → `STACK_URL=https://{env-id}.tcb-preview.com`
+- **Aliyun:** `deploy_stack --preview --provider aliyun` → `STACK_URL=https://{gateway}.{region}.fc.devs.com`
+
+Set as `STACK_URL` / `BACKEND_URL` / `WEB_URL` / per-component URLs as environment variables for BDD e2e tests:
+
+```bash
+export STACK_URL=$(deploy_stack --preview --output url)
+export BACKEND_URL=$STACK_URL
+export WEB_URL=$(deploy_stack --preview --output web_url)
+export NATIVE_URL=$(deploy_stack --preview --output native_url)
+export DESKTOP_URL=$(deploy_stack --preview --output desktop_url)
+pytest apps/web/tests/e2e/ --base-url $WEB_URL --api-url $BACKEND_URL
+pytest apps/native/tests/e2e/ --backend-url $BACKEND_URL
+pytest apps/desktop/tests/e2e/ --backend-url $BACKEND_URL
+pytest tests/cross-stack/ --stack-url $STACK_URL
+```
+
+## Stack Rollback
+
+Rollback is at the **stack** level: backend and all client components revert together to the last stable stack version.
+
+```bash
+deploy_stack --rollback ${LAST_STABLE_STACK_VERSION} --provider tcb
+```